Blue n8n integrationAutomate Blue with n8n.

This one clones a template into a new project inside a company, so the board arrives with its structure in place instead of as an empty shell.

• Company: the company that will hold the project, picked from the list the credential can reach.
• Project Name: the name of the new project, often {{ $json.account }} when it comes from a CRM item.
• Template Name or ID: the template to copy, picked from a list.

A record is a todo or a task on a Blue board. This operation writes a new one into a chosen todo list and sets its custom fields in the same call.

• Todo List: the list the record lands in, required, so an empty value stops the node.
• Title: the text that shows on the card.
• Due Date: optional, though a board without dates is hard to sort later.
• Assignee Names or IDs: the users to assign, chosen from the list or passed as IDs through an expression.

When an operation is missing, this sends the GraphQL query you write straight to Blue and returns what the API answers, with no node update to wait for.

• GraphQL Query: the query text itself, pasted into the field.
• Variables (JSON): a JSON object handed to that query, handy for an identifier that changes on every run.

The reading side of the board: it returns records for a company, narrowed down by project and by text, so a workflow acts on a slice and not on the whole backlog.

• Company: required here, while Project stays optional, which makes a company wide search possible.
• Search Term: the text a record has to contain to come back.
• Show Completed: decides whether finished records join the results.
• Limit: the ceiling on results, paired with Skip to walk a long board page by page.

Sends an invitation by email and hands the person a role on the project, which removes the manual round trip of adding a collaborator once the board already exists.

• Email: the address of the person to invite, in the user@example.com shape.
• Role: Owner, Admin, Member, Client, Comment Only, View Only or Custom Role, from full access down to read only.
• Custom Role Name or ID: the custom role defined in the project, which the node asks for alongside Role.

Returns every company the credential can reach. It is the call to make first when a workflow does not yet know which board it should be writing to.

• Timeout (Ms): the request timeout in milliseconds, worth raising on a slow instance.
• Return Full Response: returns the full GraphQL response, errors and extensions included, instead of the clean payload.

Custom fields carry whatever is specific to a team, and this operation lists them for a project with their details, identifiers included.

• Sort Order: by created date, by name or by position, ascending or descending.
• Take: how many fields come back, a number between 1 and 100.
• Skip: how many to jump over, the other half of the paging pair.

Lists the projects held by one company and nothing more. Short as it is, it mostly serves to turn a project name into the identifier the other operations expect.

• Company: required, and the only field the operation asks for.
• Return Full Response: leave it off unless a GraphQL error needs reading in the execution log.

Adds one or several tags to a record that already exists, so an automation can classify a card after the fact without touching its title or its description.

• Record ID: the record to tag, in the record-123 shape, usually {{ $json.id }} from the read before it.
• Tag Names or IDs: the tags to add, selected from the list or passed as IDs through an expression.

Edits an existing record: title, dates, position, color, people, tags and custom fields in one call, and it can move the card to another list.

• Record ID: which record to change, required next to Company.
• Todo List: set it to move the record to another list, leave it empty to keep the card where it is.
• Color: a color code such as #FF5733 for cards that need to stand out.
• Add Custom Field to Update: pairs a custom field with its value, a currency written as 100 USD, a checkbox as True or False.