Resources · Make integration

Blink Make integrationAutomate Blink with Make.

Can Make post to your Blink feed when something happens in another tool? Yes. The Blink Make integration gives you 9 modules: 6 actions and 3 searches, no trigger. This page shows how to link your account, then walks you through a first scenario that sends a feed event.

Try the Blink integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Blink Make integration do for you?

The Blink Make integration lets Make write to Blink for you. It sends, reads, updates and archives feed events, and it can list the users, linked accounts and event categories of your workspace. Since Blink has no trigger in Make, your scenario, the automation you build, starts from a schedule or from another app.

An update your staff sees without anyone typing it. A new row in a spreadsheet or a signed form in another app can start the scenario, and Send a Feed Event turns it into an entry in the Blink feed. Pick the right label first with List Feed Event Categories.

A post that stays correct. When the source record changes, Update a Feed Event edits the same entry, and Archive a Feed Event takes it out of view once it no longer applies. Both need the event ID you kept from the first send.

A clean picture of who is in Blink. List Users and List Linked Accounts return one bundle, one item passed to the next module, per person or account, so you can compare them with your HR tool or a sheet.

What Make does not do here: no Blink module watches the app, so nothing starts on its own when someone posts in Blink. Anything the 9 modules miss goes through Make an API Call. The same app often has an n8n node too; the n8n vs Make page lays out the criteria, and the Make training covers the editor from scratch. If a run fails, start with Make troubleshooting.

Connect

How do you connect your Blink account to Make?

  1. 01

    Generate a Blink API token

    In the Blink admin dashboard, open the integrations section, click the application you want to manage and generate a new API token. Copy the token shown on screen right away; Make will ask for it in a moment.

  2. 02

    Add a Blink module and open the connection

    In your scenario, add any Blink module and click Create a connection. A connection is your Blink account linked to Make once, then reused by every Blink module you add later.

  3. 03

    Name it and paste the token

    The Connection name field is optional, but a clear name helps when you manage several workspaces. Paste the API token you copied from Blink, or follow the on-screen instructions, then save.

First scenario

Your first scenario with Blink and Make

GoalWhen a new record appears in another app, Make sends it to Blink as a feed event.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. Since Blink has no trigger, this first module comes from the app where your news starts.

  2. 02

    Pick the starting module

    Search for that other app by name, choose its module and click Create a connection to link it. Make then lists the folders, sheets or objects it can read from that account.

  3. 03

    Add Send a Feed Event

    Click the + on the right of the first module, search Blink and pick Send a Feed Event. Link your Blink account, then map the data of the first module into the fields Make shows.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received, and check the new entry in your Blink feed.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on a bundle is one operation, the unit Make counts on your plan.

Modules

What each Blink module does

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

Blink1

Archive a Feed Event

ActionIn the docs only

Removes an outdated entry from the active Blink feed without you opening Blink, so staff stop acting on news that no longer holds.

When to use it
when the record behind a post is closed or cancelled in the source app, and the post should step aside rather than be rewritten.
Watch out
the module needs the ID of the event, so store it when you first send the post, for example in a sheet next to the source record.
Blink2

Get a Feed Event

ActionIn the docs only

Brings back one feed event you already know by its ID, so the next module can reuse what Blink holds for it instead of guessing.

When to use it
just before Update a Feed Event, to read the current version and decide whether a change is really needed.
Watch out
it returns a single entry; to explore several, start from a list or keep your own register of IDs, since no Blink module searches events.
Blink3

Get a Linked Account

ActionIn the docs only

Fetches the details Blink keeps for one linked account, which lets a scenario check a single account without pulling the whole list.

When to use it
when an earlier module already gives you the account ID and you only need that one record, for instance to confirm it before sending anything.
Watch out
the Blink documentation available to Make does not detail what a linked account covers, so run it once and read the bundle before you build on it.
Blink4

List Feed Event Categories

SearchIn the docs only

Shows every category your Blink feed offers, so the events you send land under the right label instead of a random one.

When to use it
while building a scenario, run it once to see the available categories, then map the one you need into Send a Feed Event.
Watch out
as a search, it returns one bundle per category, and every module placed after it runs once for each of them.
Blink5

List Linked Accounts

SearchIn the docs only

Returns all the linked accounts of your Blink workspace in one pass, handy when you want an overview rather than one record.

When to use it
to copy the accounts into a sheet for review, or to find the ID that Get a Linked Account expects.
Watch out
each account arrives as its own bundle, so a long list means many operations for every module placed after it.
Blink6

List Users

SearchIn the docs only

Gives you the people registered in Blink, one bundle each, so you can compare your Blink roster with another tool without exporting anything by hand.

When to use it
to spot staff present in your HR system but missing in Blink, or the reverse, after an arrival or a departure.
Watch out
the list can return zero, one or many users; test with Run once to see how many bundles reach the next module.
Blink7

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Blink API with the connection you already set up, which covers whatever the eight other modules leave out.

When to use it
when the job you have in mind has no ready-made Blink module, and the Blink API documentation shows an endpoint for it.
Watch out
here you write the request yourself, path and body included, so read the Blink API reference first and test with Run once.
Blink8

Send a Feed Event

ActionIn the docs only

Publishes a new entry in the Blink feed from data coming out of another module, so an update reaches your team where they already read.

When to use it
when an event in another app, a signed form or a new row, deserves to be seen by staff in Blink.
Watch out
the update and archive modules very likely point to an event by its ID, so check in Run once whether the output bundle holds one, and keep it.
Blink9

Update a Feed Event

ActionIn the docs only

Corrects an entry already in the feed, so a change in the source shows up in the same post instead of a second, confusing one.

When to use it
when the record that produced the post moves, for example a new date or a new owner, and the feed should follow.
Watch out
pair it with Get a Feed Event when you need the current version, and make sure the ID you map is the one of the original post.
Need help

Need help automating Blink with Make?

A person reads every message.

FAQ

Questions about the Blink Make integration

01Is the Blink Make integration free?
Yes, on the Make side. Blink is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops a run after 5 minutes and caps files at 5 MB with 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Make counts usage in operations, one per module run on one bundle. Your Blink subscription is a separate matter, handled on the Blink side.
02What do you need to connect Blink to Make?
An active Blink account and an API token generated from it. In the Blink admin dashboard, go to the integrations section, click the application to manage, generate a new API token and copy it. In Make, add any Blink module, click Create a connection, give the connection a name if you like, and paste the token. The connection is then shared by every Blink module in your scenarios, so this setup is done once per account.
03Does the Blink Make integration react in real time?
No, because Blink has no trigger in Make: no module watches the app, scheduled or instant. A scenario that uses Blink starts in one of two ways. Either it runs on the schedule of its first module, every 15 minutes by default, or it starts from the trigger of another app, which can be instant if that app offers one. In both cases the Blink modules come after the first step and act on what it delivers.
04What if a Blink module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Blink API with the connection you already created, so you are not stuck with the 9 listed modules. You write the request yourself, based on the Blink API documentation. Note that the Make documentation page for Blink is generated from the vendor's docs and flags that it may contain mistakes, so check important details with Blink directly when something does not behave as expected.
05Make or n8n for Blink?
It depends on the tool your team already uses and on what you need to do with Blink. In Make, Blink comes with 9 ready modules around feed events, users and linked accounts, plus Make an API Call for the rest, all behind one connection. The same app often has an n8n node as well. Compare which operations each side offers for your case, then pick the tool in which your team is comfortable maintaining scenarios over time.
Same platform

Other docs you might need on this stack.

Browse all integrations