Resources · Zapier integration

Blue Zapier integrationAutomate Blue with Zapier.

The Blue Zapier integration gives you 3 triggers, 16 actions and 8 searches to create, update, tag, move and find records in your Blue projects from any other app. Here is what each one does, what it costs in tasks, which trigger is instant and where it trips people up.

See the 27 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Blue Zapier integration actually does

Blue is a project management tool where work lives as records, organized in lists inside projects, inside a company account. Zapier connects it to your other apps: a new record or new activity can start an automation, and other apps can create, update, tag, comment, move, complete or delete records, manage project members and look things up.

Three results come up again and again. An intake that files itself: a form or a support ticket becomes a record with Create Record, gets tags with Append Tags to Record and an owner with Assign User to a Record. A record that follows the outside world: a payment or a signature in another tool runs Find Record, then Complete a Record or Move Record to Another List. A project that staffs itself: a new hire in your HR tool triggers Invite User to a Project.

The most useful thing to know before you build: of the three triggers, only Watch Events is instant. It fires the moment something happens in Blue, even on the free plan, while New Record and New Record Activity wait for Zapier's next check, every 15 minutes on Free.

What it does not do: nothing here creates a project, a list or a company, so the structure is set up in Blue first. Most operations also want company, project and record identifiers, which is why the searches matter so much. The same app has a Blue n8n integration and a Blue Make integration page if you want to compare.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here they are once, in plain English.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts the Zap, like a new record in a Blue list. Once the Zap is switched on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or changes something for you, like Create Record.
Task
The unit Zapier bills: one action that completes successfully. The number on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer and Zapier keeps only what is new. An instant one is pushed by the app as it happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
Search step
A step that looks up something already stored in an app, like a record by name, so later steps can reuse its ID.
Connection
Your Blue account linked to Zapier once, then reused by every Blue step of every Zap you build.
Cost

What a Blue Zap really costs

Blue is not a premium app on Zapier, so it runs on the free plan. The bill is counted in tasks, and the rules are easy to misjudge.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • BilledEach successful action, never the trigger
  • Blue triggers3: 1 instant, 2 polling

The trigger never costs a task, and neither do the checks Zapier runs on New Record or New Record Activity. Each action that succeeds counts as one task; a failed one counts for nothing. A Zap that creates a record, tags it and assigns it uses three tasks per run, three times a one-action Zap. The free plan gives 100 tasks a month and unlimited Zaps, two steps each. Since many Blue actions need a record ID, you will often add a search like Find Record first, and a search makes the Zap multi-step, which needs a paid plan.

Connect

Connect your Blue account to Zapier

  1. 01

    Open your connections

    In Zapier, go to the Apps page and click + Add connection. You need a Blue account, plus read or write access on any project you do not own but want the Zap to touch.

  2. 02

    Pick Blue

    Type Blue in the search box of the dialog, select it, then click Add connection. A new browser tab then opens on the Blue side for the sign-in step itself.

  3. 03

    Sign in and allow access

    Log in to Blue in that tab and grant Zapier access to the account. The connection now sits in your list, ready for every Blue trigger, action and search you add later.

First Zap

Your first Blue Zap, step by step

GoalEvery new record in a Blue intake list gets a comment that kicks off the team discussion.

  1. 01

    Create the Zap

    Start a new Zap, pick Blue as the app that starts it and New Record as the event, then select your Blue connection to continue.

  2. 02

    Point it at the project

    Fill the company and project fields with the IDs of the workspace you want watched. Both are required for this trigger to know where to look.

  3. 03

    Test the trigger

    Run the test: Zapier brings back the three most recent records of that project, so you can map the next step on a real one.

  4. 04

    Add the comment

    Add Blue again with Add a Comment to a Record, set the company and project, map the record ID from the trigger, and write the comment text.

  5. 05

    Test, then publish

    Test the action, check the comment in Blue, then click Publish. New records are then picked up at your plan's check interval.

Triggers

The 3 Blue triggers

3 events start a Zap when something happens in Blue, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

New Record

Polling trigger

In Zapier“Triggers when a new record is created in a list of a project.”

Starts your Zap each time a record is created in a list of the Blue project you pick. Its contents travel to the next steps, so a fresh piece of work can be announced, copied or assigned without anyone opening Blue to look for it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
requests land in a Blue list and another tool or person has to hear about each one.
Watch out
it needs both the company and the project, entered as IDs, before the test can return anything.
2

New Record Activity

Polling trigger

In Zapier“Triggers when there is new activity (comments or actions) on a record.”

Watches one specific record and fires when something new happens on it, a comment or an action by a teammate. It suits a single high-stakes item rather than a whole project, since you choose the record in advance.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a client record or a key deliverable should push every new comment to a channel or an inbox.
Watch out
one Zap follows one record; if a later step comments on that same record, the Zap triggers itself again.
3

Watch Events

Instant trigger

In Zapier“Triggers when a new event occurs.”

Opens a channel through which Blue reports its events to Zapier as they occur, under a name you give it. Of the three triggers, it is the only one that does not depend on Zapier coming to check.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want Blue activity to reach another tool without the wait of a polling check.
Watch out
it asks for a Webhook Name, a required label; pick one you will recognize later among your Zaps.
Actions

The 16 Blue actions

Blue gives you 16 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Reference to a Custom Field

Action

In Zapier“Overwrites the Reference of the specific custom field.”

Links a record to another record through a reference custom field, and replaces whatever reference the field held before.

When to use it
tying a task to its client record or its parent deliverable automatically when it is created.
Watch out
it overwrites the existing reference rather than adding to it, so check you are not erasing a link someone set by hand.
2

Append Description to Record

Action

In Zapier“Appends description to a record without replacing existing description.”

Adds text to the end of a record's description and keeps what was already written. The text can carry formatting written as HTML.

When to use it
logging each new email or call summary on the same record, as a running history.
Watch out
each run adds more text, so a Zap that fires too often makes the description grow quickly.
3

Append Tags to Record

Action

In Zapier“Appends tags to a record without removing existing tags.”

Puts extra tags on a record without touching the tags it already has. If a tag is already there, the duplicate is dropped on its own.

When to use it
marking records by source, priority or client as they come in from other apps.
Watch out
you choose tags that exist in Blue, so create them in the project first.
4

Assign User to a Record

Action

In Zapier“Assigns user to a record.”

Gives a record one or more assignees, so the right people see it in their own work.

When to use it
routing new records to an owner based on the source, the client or the type of request.
Watch out
assignees are entered as user IDs, not names or emails, which is often the step that needs a lookup.
5

Add a Comment to a Record

Action

In Zapier“Adds a comment to a record.”

Posts a comment on a record, where the team already follows the work. The comment accepts HTML formatting.

When to use it
dropping a customer reply, a form answer or a status update where the team already discusses the work.
Watch out
if the Zap starts from New Record Activity on the same record, its own comment starts it again.
6

Complete a Record

Action

In Zapier“Mark complete a record.”

Marks a record as done, from its record ID, inside the company and project you name.

When to use it
the work is confirmed finished in another app, a payment received or a document signed.
Watch out
the record ID is required; when you only have a name, place Find Record before this step.
7

Create Record

Action

In Zapier“Creates a new record.”

Adds a new record to a list of a Blue project, filled with values from earlier steps. This is how form entries, tickets or leads become work items your team can pick up.

When to use it
requests arrive in another app and belong in a Blue list.
Watch out
company, project and list are all required, the list as its ID.
8

Custom GraphQL Query

Action

In Zapier“Freely customized GraphQL query.”

Lets you write your own query to Blue when none of the ready-made actions does what you need. It is the open door of the integration.

When to use it
a developer on the team needs a Blue operation that this list does not cover.
Watch out
this one is technical; without someone who knows Blue's query language, stick to the actions above.
9

Delete a Record

Action

In Zapier“Deletes a record in a project.”

Removes a record from a project. The Zap names the company, the project and the record, and Blue deletes it.

When to use it
a request is cancelled at its source and should not stay in the Blue list.
Watch out
the deletion is real; test it on a throwaway record before pointing it at live work.
10

Invite User to a Project

Action

In Zapier“Invites a user to a project.”

Sends a project invitation to an email address, with the role you choose for that person.

When to use it
a new client or freelancer signs, and they should get access to their project without anyone doing it by hand.
Watch out
the role is required, so decide in advance what each kind of invitee may see and do.
11

Move Record to Another List

Action

In Zapier“Moves a record to another list. Works within the same project or across different projects.”

Shifts a record from its current list to another one, within the same project or into a different project.

When to use it
a deal is won and its record should jump from the sales pipeline to the delivery project.
Watch out
you set both the current project and the destination project, so a wrong pick sends the record somewhere unexpected.
12

Remove Tags From Record

Action

In Zapier“Removes specific tags from a record without affecting other tags.”

Takes the tags you choose off a record and leaves all its other tags in place. Useful as the counterpart of Append Tags when a state ends.

When to use it
clearing an Urgent or Waiting tag once the matching event happens in another app.
Watch out
company, project and record are required, so the Zap must know exactly which record to clean.
13

Remove User to a Project

Action

In Zapier“Removes a user to a project.”

Takes a user out of a project, identified by their user ID. The name on Zapier reads exactly like this.

When to use it
a contract ends or a person leaves, and their project access should go with it.
Watch out
it needs the user's ID, not their email, so keep that ID somewhere a Zap can read it.
14

Update Record

Action

In Zapier“Updates the specific Record.”

Changes an existing record, identified by its record ID, with data coming from the trigger or a search.

When to use it
a status, an amount or a deadline changes in another tool and the matching record should follow.
Watch out
the record ID is required, so a search such as Find Record usually comes first.
15

Upload File to Files

Action

In Zapier“Uploads one or more files to files.”

Sends one or more files into the Files area of a Blue project, ready for the team to find there.

When to use it
signed contracts, invoices or exports produced elsewhere should be stored with the project they belong to.
Watch out
the company and the project are required, as an ID or a slug; the file goes to the project, not to a record.
16

Upload File to Custom Field

Action

In Zapier“Upload File to specific custom field.”

Attaches a file to a specific file custom field of one record, rather than to the project as a whole.

When to use it
each record needs its own deliverable, like a brief or a proof, stored in a dedicated field.
Watch out
it requires the record ID and the ID of the file attachment custom field, so set that field up in Blue first.
Searches

The 8 Blue searches

8 search steps look for data that already exists in Blue, so a later step can use it.

A search step looks up something that already exists in Blue and passes it to the next steps. In the editor, Blue's searches sit at the bottom of the Action event list, under SEARCH. Adding one makes the Zap multi-step. Blue offers no find-or-create variant. Three settings decide what happens next.

1

Find Company

Search

In Zapier“Finds a company in the account.”

Looks up a company in your Blue account and returns its details, starting with the identifier other steps ask for.

When to use it
at the top of a Zap, so later steps can use the company ID instead of a typed value.
Watch out
it only sees companies your connected account belongs to.
2

Find Lists

Search

In Zapier“Finds all lists in a project.”

Returns all the lists of a project in one go, so a following step can pick the right one.

When to use it
before Create Record or a move, when the target list depends on the incoming data.
Watch out
company and project are required, so this search usually follows another one.
3

Find Project

Search

In Zapier“Finds a project in the company by searching similar keywords in the name. Outputs maximum item of 20.”

Searches a company for projects whose name looks like the keywords you give it, and returns up to 20 of them.

When to use it
you know a project by its name, from a client or a form, but not by its ID.
Watch out
the match is on similar names, so a vague keyword can return the wrong project first.
4

Find Record

Search

In Zapier“Finds a record in the list by searching their Record Name.”

Finds a record in a list by its record name, then hands its ID and fields to the next steps.

When to use it
before Update Record, Complete a Record or a comment, when the trigger carries a name but no ID.
Watch out
two records with the same name both match; set the multiple-results option on purpose.
5

Find Record With Filters

Search

In Zapier“Finds records with advanced filters including tags, assignees, done status, date ranges, and custom field filters.”

Looks for records using several criteria at once: tags, assignees, done status, date ranges and custom field values.

When to use it
picking the open records of one assignee, or the ones tagged for a client, before acting on them.
Watch out
the more filters you combine, the more likely nothing matches; decide what the Zap does then.
6

Get a Project

Search

In Zapier“Retrieves a single project by its Project ID.”

Retrieves one project when you already have its project ID, and returns its details for later steps.

When to use it
another app stores the Blue project ID and you need the project's current data.
Watch out
it reads by ID only; to search by name, use Find Project instead.
7

Get a Record

Search

In Zapier“Retrieves a record using Record ID.”

Fetches one record from its record ID, with its current fields, without changing anything.

When to use it
checking a record's state just before deciding, with a filter, whether to act on it.
Watch out
company, project and record ID are all required.
8

Get Record Activity

Search

In Zapier“Retrieves activity (comments and actions) for a specific record.”

Reads the activity of a given record, its comments and actions, and passes that history to the next steps.

When to use it
building a summary or a report of what happened on a record before closing it.
Watch out
it reads one record at a time, identified by its ID.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that needed it are skipped. Switched on, the Zap goes on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Blue does not offer that variant for any of its searches, so it will not appear here.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a Blue Zap breaks

Zapier ties no help article to Blue, so the cases below are the ones every Zap meets, seen from a Blue project.

Most of them come from identifiers and from Zaps that feed their own trigger. If yours keeps failing, our Zapier troubleshooting page walks through the usual checks.

  • Old records are never picked up

    A Zap only reacts to what happens after you publish it. Records already in the project stay where they are; moving that backlog is a separate job.

  • The Zap comments on itself

    New Record Activity plus Add a Comment to a Record on the same record: each comment is new activity, the Zap starts again and burns tasks fast.

  • A bulk import goes quiet

    Import a large batch of records at once and New Record suddenly returns a huge pile. Zapier's flood protection can hold that batch back.

  • The same record never runs twice

    Zapier remembers what it has already seen on a polling trigger, so a record that started the Zap once will not start it again as new.
Need help

Need help automating Blue with Zapier?

A person reads every message.

FAQ

Blue Zapier integration: common questions

01Is the Blue Zapier integration free?
Yes, Blue is not a premium app, so it works on the free Zapier plan. That plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger and one action. Many Blue actions need a record ID, so a search such as Find Record often comes first, and a search, a filter or a second action makes the Zap multi-step, which needs a paid plan. Usage is then counted in tasks.
02How many tasks does a Blue Zap use?
One task per successful action, and nothing for the trigger. The checks Zapier runs on New Record or New Record Activity are free too, however often they happen. A Zap that creates a record, tags it and assigns it costs three tasks per run. An action that fails is not counted. Watch the loop case: a Zap that comments on the record whose activity it watches keeps restarting and eats tasks each time.
03Is Blue on Zapier real time?
Only one trigger is. Watch Events is instant: Blue tells Zapier the moment an event happens, on every plan, and the Zap shows a lightning bolt in the editor. New Record and New Record Activity are polling triggers, checked every 15 minutes on Free, every 2 minutes on Professional and every minute on Team and Enterprise. The type comes from Blue's own API and cannot be changed in the editor.
04What does it take to connect Blue to Zapier?
A Blue account, plus read or write access on any project you do not own but want the Zap to touch. You add the connection once from the Apps page with + Add connection, sign in to Blue in the tab that opens and allow access. After that, nearly every operation asks for a company and a project, and many for a record ID, so your account must be able to see them.
05Why does a Blue action ask for IDs instead of names?
Because Blue operations point at exact objects: Assign User to a Record wants user IDs, Update Record and Complete a Record want the record ID, Create Record wants the list ID. When your trigger only carries a name, place a search first, such as Find Record, Find Project or Find Lists, and map the ID it returns into the action. That search makes the Zap multi-step. Find Project can return up to 20 matches, so pick the first one on purpose.
06What if the Blue operation you need is not listed?
Then the ready-made list does not cover it, but Blue offers a way out: Custom GraphQL Query lets someone who knows Blue's query language write the request directly. It is a technical step, best left to a developer. Otherwise, check whether two existing operations chained together, a search then an action, reach the same result before looking at another tool. Keep in mind that this query step is billed in tasks when it succeeds, like any action.
07Zapier, Make or n8n for Blue?
It depends on your criteria rather than on a winner. On Zapier, Blue works on the free plan with 27 operations and one instant trigger, but useful Zaps often need a search and therefore a paid plan. Make and n8n list their own Blue operations, each on its page. Check first that the triggers, actions and searches you need exist on the tool, then weigh which tool your team already runs.
Same platform

Other docs you might need on this stack.

Browse all integrations