Integrations

n8n

Push data to EasyBoard from any n8n workflow using the built-in HTTP Request node. Works identically on self-hosted n8n and n8n Cloud — no plugin, no credential type to register, just a standard HTTP call.

Before you start

You'll need two values from your EasyBoard dashboard:

Dashboard ID

The short string in your dashboard URL: easyboard.live/d/abc123xyz456

Write token

Shown once at dashboard creation — retrieve it from the hub if needed

Configure the HTTP Request node

Add an HTTP Request node to your workflow and fill in these fields:

Method

PATCH

URL

https://easyboard.live/api/d/YOUR_DASHBOARD_ID/tiles

Authentication

Header Auth

Header Name

Authorization

Header Value

Bearer YOUR_WRITE_TOKEN

Body Content Type

JSON

Specify Body

Using JSON

Set the JSON Body to:

json
{
  "updates": [
    {
      "target": { "alternateId": "revenue" },
      "patch": { "value": "{{ $json.amount }}" }
    }
  ]
}

Replace revenue with your tile's alternateId. {{ $json.amount }} is n8n's expression syntax — click the field and use the expression editor to map any upstream node's output.

Store the write token as an n8n credential

In n8n, go to Credentials → New → Header Auth. Set the name to Authorization and the value to Bearer YOUR_WRITE_TOKEN. Reference this credential in the HTTP Request node rather than pasting the raw token into the workflow — it keeps the token out of your workflow JSON and makes rotation easy.

Update multiple tiles at once

One HTTP Request node can update several tiles in a single API call — counts as one request against your rate limit:

json
{
  "updates": [
    {
      "target": { "alternateId": "order-count" },
      "patch": { "value": "{{ $json.order_number }}" }
    },
    {
      "target": { "alternateId": "customer" },
      "patch": { "value": "{{ $json.billing_name }}" }
    },
    {
      "target": { "alternateId": "status" },
      "patch": { "value": "Processing" }
    }
  ]
}

Incrementing a counter

Use delta instead of value to safely increment a counter tile — even if two workflow runs fire simultaneously, the server-side delta math prevents double-counting:

json
{
  "updates": [
    {
      "target": { "alternateId": "signups" },
      "patch": { "delta": 1 }
    }
  ]
}

Common n8n workflow ideas

Webhook → tile

Receive a webhook from any service and immediately relay a field to EasyBoard

New database row

Postgres / MySQL node triggers on insert; push row count or a field value

Scheduled fetch

Schedule node polls an external API every N minutes; relay the result

Stripe payment

On charge.succeeded webhook, update revenue tile and increment order counter

GitHub event

On push or PR merge, update a deploy status text tile

Error alerting

Catch node triggers on workflow failure; push "Error" to a toggle tile

Self-hosted n8n and outbound access

If your n8n instance runs inside a private network, make sure it has outbound HTTPS access to easyboard.live on port 443. No inbound ports or webhooks are needed — EasyBoard only receives data, it doesn't call back.