n8n

Connect Blue to n8n's open-source workflow engine to automate across hundreds of apps.

n8n is an open-source workflow automation tool with hundreds of integrations. Connecting Blue to n8n lets you trigger workflows when something happens in Blue, push data from external systems back into Blue, and chain Blue together with any other tool n8n speaks to.

How it connects

Blue and n8n communicate through Blue’s public API and webhooks. n8n acts as the orchestrator — listening for events, making requests, and routing data between Blue and other services.

There are two directions:

  • Blue → n8n — a webhook from Blue triggers an n8n workflow when records change, automations fire, or forms submit.
  • n8n → Blue — an n8n workflow calls Blue’s GraphQL API to create or update records, attach files, post comments, and so on.

Setting it up

Triggering an n8n workflow from Blue

  1. In n8n, create a new workflow starting with a Webhook node. Copy the webhook URL it generates.
  2. In Blue, open the workspace’s Automations panel.
  3. Pick a trigger (record created, status changed, field updated, scheduled, etc.).
  4. Add a HTTP Request action with the URL set to the n8n webhook.
  5. Optionally include record data in the request body — use variables like {Name} or {Status} to pass field values through.
  6. Save the automation and the webhook will fire each time the trigger condition is met.

Calling Blue from n8n

  1. Create an API key in Organisation Settings → API.
  2. In n8n, add an HTTP Request node pointed at https://api.blue.app/graphql.
  3. Set the header Authorization: Bearer <your-api-key>.
  4. Build the GraphQL mutation or query in the node body. See the API docs for the available operations.

Example workflows

  • Slack → Blue — a Slack /task slash command lands in n8n, which creates a record in the right Blue workspace.
  • Blue → Sheets — every time a record’s status flips to Done, n8n appends a row to a Google Sheet for reporting.
  • Form → Blue → Email — an external form posts to n8n, which creates the Blue record, then sends a templated confirmation email to the submitter.
  • Stripe → Blue — a successful Stripe payment triggers n8n to mark the linked Blue record as paid.

Behavior

  • n8n is self-hosted or cloud — both work the same way against Blue’s API, as long as the n8n instance can reach api.blue.app.
  • API rate limits apply to the n8n side — see the API docs for the current ceilings.
  • For lower-code use cases, also see Zapier, Make, and Pabbly Connect.