Resources · Make integration

Blue Make integrationAutomate Blue with Make.

Tired of copying the same details into Blue by hand? The Blue Make integration gives you 14 modules: 1 instant trigger, 8 actions and 5 searches. This guide is for people who know Blue and are new to Make: connect your account, then build a first scenario step by step.

Try the Blue integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Blue Make integration do for you?

The integration links your Blue account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that triggers, acts or searches. Once linked, Make can react to what happens in Blue, create and update records in your projects, file documents and read your project structure, all without writing code.

New requests land in the right project. A form or a CRM in another app fires the scenario, and Create a record drops the request into a Blue project. Add Upload file to a custom field when the request comes with attachments.

Your other tools hear about Blue changes. Watch events is an instant trigger: Blue calls Make the moment something happens. Pair it with Get a record to read the full record, then pass it to your chat or reporting app.

Status stays in sync from the outside. When a payment clears or a ticket closes elsewhere, Search records of a project finds the matching record and Update a record changes it. Onboarding a freelancer? Invite a user to a project handles the access.

What the integration does not do: there is no "Make an API Call" module for Blue. The fallback is Execute a GraphQL Query, which sends any query your Blue key is allowed to run. Blue also has an n8n node, covered in the Blue n8n integration guide, and the n8n vs Make comparison helps you pick. New to the editor? The Make training starts from zero.

Connect

How do you connect your Blue account to Make?

  1. 01

    Generate a token in Blue

    In Blue, open your profile, go to the API tab and click Generate a Token. Give it a name you will recognize later. Blue then shows two values: the Token ID and the Secret key. Copy both somewhere safe.

  2. 02

    Open the connection window in Make

    Add any Blue module to your scenario and click Create a connection. The connection is your Blue account linked to Make once, then reused by every Blue module. The Connection name field is optional, but a clear name helps when you have several accounts.

  3. 03

    Paste the credentials and save

    Paste the Token ID and the Secret key you copied from Blue, or follow the instructions Make shows on screen. Save, and the connection appears in the module. Blue requires an active account for this to work, so check your subscription first.

First scenario

Your first scenario: keep a Blue record in sync with another tool

GoalWhen a deal or ticket changes in another app, Make finds the matching record in Blue and updates it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. The first module is the trigger from your other app, for example your CRM or helpdesk, the place where the change really happens.

  2. 02

    Add Search records of a project

    Click the + on the right, search for Blue and pick Search records of a project. Click Create a connection with your Token ID and Secret key, then choose the project Make offers once the account is linked.

  3. 03

    Add Update a record

    Add Update a record after the search. Map the record the search returned, then map the values from the first module. Each item that flows between modules is a bundle: one record here, one deal there.

  4. 04

    Test with Run once

    Click Run once and trigger a change in the other app. Read the bundles each module received. A search can return zero, one or several records, so check that the right one was updated before going further.

  5. 05

    Schedule and switch on

    Set the schedule on the first module: a new scenario runs every 15 minutes by default. Then switch the scenario on. Each module that runs on one bundle counts as one operation on your Make plan.

Triggers

What starts a scenario from Blue

1 module starts a scenario when something happens in Blue. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Blue as soon as it happens.

Blue1Watch events

Watch events

Instant trigger

In Make“Watches for events.”

This is the only Blue trigger: it starts your scenario when an event happens in your Blue account, so Make does not have to go and look for changes. It gives you the event as a bundle, ready for the next module.

How it fires
instant, Blue calls Make through a webhook as soon as the event happens.
When to use it
when your team wants a message, a log line or a follow-up in another app the moment work moves in Blue.
Watch out
the setup starts with Create a webhook, then the connection. Make does not document the event types, so trigger a real change and read the bundle before mapping anything.
Modules

Everything the Blue app can do in Make

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

Blue1

Create a record

Action

In Make“Creates a record.”

Adds a brand new record to one of your Blue projects, filled with data from earlier modules, so work coming from outside lands in Blue without anyone retyping it.

When to use it
a quote request arrives through a web form and should become a record your team picks up.
Watch out
run it once with a test entry and check the record in Blue before switching the scenario on, or duplicates pile up fast.
Blue2

Execute a GraphQL Query

Action

In Make“Performs an arbitrary authorized GraphQL query.”

Sends a GraphQL query of your own to Blue, with the rights of your connected key. It is the escape hatch for anything the other thirteen modules do not cover.

When to use it
you need a piece of data or an operation that has no dedicated module.
Watch out
you write the query yourself, so this is the one technical module here. Test it with Run once on harmless data first.
Blue3

Get a record

Action

In Make“Retrieves a record.”

Reads one record you already know, and hands its full content to the next module. Think of it as opening the record in Blue, but from inside the scenario.

When to use it
right after Watch events, when the event alone does not carry every detail you want to forward.
Watch out
it needs the record's identifier. Map it from the trigger or a search; typing one by hand only works for tests.
Blue4

Invite a user to a project

Action

In Make“Invites a user to a project.”

Sends someone an invitation to join a Blue project, so access follows your process instead of someone remembering to click.

When to use it
a contract is signed in your e-signature tool and the new client or freelancer should see the project straight away.
Watch out
an invitation reaches a real person. Use your own address while you test with Run once.
Blue5

Update a record

Action

In Make“Updates a record.”

Changes an existing record in Blue with fresh values from your scenario, which keeps a project honest when the truth lives in another tool.

When to use it
an invoice is paid in your accounting app and the matching record in Blue should reflect it.
Watch out
you must point it at one precise record. Place Search records of a project or Get a record just before it.
Blue6

Upload file to a custom field

Action

In Make“Uploads one or more files to a custom field.”

Attaches one or more files to a custom field of a record, so the document sits right next to the work it belongs to.

When to use it
a signed PDF or a brief arrives by email and belongs on the record it concerns.
Watch out
on the Make Free plan, files are capped at 5 MB. Check the size of the attachments you expect before you switch the scenario on.
Blue7

Upload file to files directory

Action

In Make“Uploads one or more files to specific directory.”

Drops one or more files into a directory of your Blue files instead of a single record. Pick it over the custom field version when the document concerns the whole project.

When to use it
collecting meeting notes, exports or deliverables in one shared place.
Watch out
the same 5 MB file limit applies on the Free plan, and each file counts toward your 512 MB of transfer.
Blue8

List all projects

Search

In Make“Lists all projects.”

Returns your Blue projects, one bundle per project. Useful whenever a scenario has to loop over your whole workspace.

When to use it
building a project overview in a spreadsheet or a report app.
Watch out
the modules placed after it run once per project, and each run is an operation. A big workspace uses operations quickly.
Blue9

List custom fields

Search

In Make“Lists custom fields of a project.”

Shows the custom fields defined in a project, so you can see how the project is structured before writing data into it.

When to use it
preparing a scenario that fills custom fields, or checking a project setup from another tool.
Watch out
run it with Run once while you build, and read the bundles. They tell you exactly which field to map later.
Blue10

List lists of a project

Search

In Make“Lists lists of a project.”

Gives back the lists that organize a Blue project, each list as its own bundle, ready to filter or route.

When to use it
your scenario needs to know where records can go before it creates one.
Watch out
a project with several lists returns several bundles. Read them with Run once and decide which list you really need before going further.
Blue11

List tags within projects

Search

In Make“Lists tags within projects.”

Collects the tags used across your projects, handy when your team labels work and you want the same labels elsewhere.

When to use it
syncing a tag list with a reporting sheet, or checking a tag exists before a later module relies on it.
Watch out
each tag comes out as a separate bundle, so the next module runs once per tag.
Blue12

Search records of a project

Search

In Make“Searches records of a project.”

Looks through the records of one project and returns the ones that match. It is how a scenario finds the right record when it only knows a name or a detail.

When to use it
just before Update a record, to target the record tied to a deal or a ticket from another app.
Watch out
a search can find nothing, one or several records. Check the result with Run once before updating anything.
Blue13

Add reference to custom field

ActionIn the docs only

Writes a reference into a custom field of a Blue record. Make publishes no description for it, so treat it as a module to explore carefully.

When to use it
your project uses custom fields that point to other items and a scenario should fill them.
Watch out
with no official description, test it with Run once on a throwaway record and check the result in Blue first.
Need help

Need help automating Blue with Make?

A person reads every message.

FAQ

Questions people ask about Blue and Make

01Is the Blue Make integration free?
Yes, on the Make side. Blue is a standard app, available on the Free plan. That plan allows 2 active scenarios, a 15 minute minimum between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of transfer. The last two matter if you upload files to Blue. Paid plans bring the interval down to 1 minute and lift the cap on active scenarios. Blue itself is a separate subscription: you need an active Blue account, and its price is on the Blue pricing page, not on Make.
02What do you need to connect Blue to Make?
An active Blue account and an API token. In Blue, open your profile, click the API tab, then Generate a Token and give it a name. Blue shows a Token ID and a Secret key: copy both. In Make, add a Blue module, click Create a connection, name it if you like and paste the two values. For Watch events, Make asks you to create the webhook before the connection. The connection is then reused by every Blue module in your scenarios.
03Does the Blue trigger react in real time?
Yes. Watch events is an instant trigger: Blue calls Make through a webhook as soon as the event happens, instead of Make checking on a schedule. That is the lightning badge on the module in the editor. The other Blue modules are actions and searches, so a scenario that starts elsewhere, for example in your CRM, follows the schedule of that first module, every 15 minutes by default on a new scenario. Each module run on one bundle counts as one operation.
04What if a Blue module is missing in Make?
Use Execute a GraphQL Query. Blue has no Make an API Call module, but this one sends any GraphQL query your key is authorized to run, so it covers what the thirteen other modules do not. It asks you to write the query yourself, which is more technical than the rest of the app. If that is too far from what your team wants to maintain, look at another app that already holds the data, or ask the team at Hack'celeration to build it with you.
05Make or n8n for Blue?
It depends on the tool your team already runs. Blue exists on both sides: in Make, 14 modules with an instant Watch events trigger, a GraphQL module for the rest, and connection by Token ID and Secret key. n8n also has a Blue node, described in its own guide on this site. Neither is ranked here. Pick the platform where your other scenarios already live, so one team maintains one set of automations, and compare the two editors on a small test before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations