Resources · Make integration

Linked API Make integrationAutomate Linked API with Make.

Can Make handle your Linked API outreach without a line of code? The Linked API Make integration gives you 27 modules, 23 actions and 4 searches, with no trigger. This guide is for sales and recruiting teams: connect the account, then build a first scenario step by step.

Try the Linked API integration on MakeSee the 27 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Linked API Make integration do for you?

The Linked API Make integration links your Linked API account to Make so you can fetch people and companies, run searches, and send messages or connection requests inside a scenario, the automation you build in Make as a chain of modules. Each module is one brick of that chain. Linked API has no trigger, so another app or a schedule starts the work.

Leads that arrive already researched. A form or your CRM adds a new lead, Fetch a Person pulls the profile, and the next module writes it to the record. The rep who picks up the lead starts with context instead of a bare name.

Conversations filed where deals live. A scheduled scenario runs Poll Conversations, then Sync a Conversation on the thread that matters, and the exchange ends up in the CRM next to the deal it belongs to.

An invitation queue that stays short. Retrieve Pending Requests brings up the invitations still waiting, and Withdraw a Connection Request clears the ones your team has given up on.

What Make won't do here is react the second something happens: with no trigger in the app, every flow starts from another app or from the clock. Make's documentation for Linked API also says it was generated by AI and may contain mistakes, so confirm important details with Linked API directly.

Weighing tools before you commit? The n8n vs Make comparison sets out the criteria, Make pricing explains how operations are counted, and Make training covers scenario building from the ground up.

Connect

How do you connect Linked API to Make?

  1. 01

    Add a Linked API module

    In your scenario, pick any Linked API module, Fetch a Person for instance, and click Create a connection. A connection is your Linked API account linked to Make once, then reused by every Linked API module you add later.

  2. 02

    Copy your two tokens

    Log in to Linked API and open the dashboard. Copy the API token and the Identification Token displayed there. These are the credentials Make needs to recognize your account.

  3. 03

    Name and save the connection

    Back in Make, the Connection name field is optional, but a clear label such as Sales team helps once several accounts exist. Paste the credentials or follow the on-screen instructions.

First scenario

Your first scenario: research a new lead and invite them

GoalWhen a new lead lands in another app, Make fetches the person in Linked API and sends them a connection request.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Linked API has no trigger, so start with the app where your leads arrive, such as your CRM or form tool.

  2. 02

    Add Fetch a Person

    Click the + on the right of that first module, search for Linked API and choose Fetch a Person. Click Create a connection and paste your two tokens.

  3. 03

    Map the lead

    Fill the module fields with data from the first module, so every new lead gets looked up. Each lead travels as a bundle, the single item handed from one module to the next.

  4. 04

    Add the invitation

    Click the + again, pick Send a Connection Request and map the person returned by Fetch a Person. Every module run on a bundle is one operation, the unit your Make plan counts.

  5. 05

    Test with Run once

    Click Run once with a test lead and read the bundles each module received. The invitation really goes out, so use a colleague who knows it is a test.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. From then on, each new lead is researched and invited without anyone opening a tab.

Modules

What each Linked API module does in Make

Linked API gives you 27 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Linked API1

Check a Connection Status

ActionIn the docs only

Before anyone gets an invitation, Check a Connection Status tells your scenario where you stand with that person, so you are not guessing whether you are already connected. It works on one person per bundle.

When to use it
just ahead of Send a Connection Request, when your lead list mixes existing contacts with strangers.
Watch out
Make's documentation does not list the statuses it can return, so run it once and read the output before relying on it.
Linked API2

Comment on a Post

ActionIn the docs only

Comment on a Post publishes a written comment under one post, so a reply goes out while you stay in your CRM. The text can mix fixed words with data mapped from earlier modules.

When to use it
right after Fetch a Post, when an announcement from a target account deserves a short public reaction.
Watch out
comments are public and Run once posts for real, so test it on a post of your own first.
Linked API3

Execute a Custom Workflow

ActionIn the docs only

Some sequences don't fit in a single module. Going by its name, Execute a Custom Workflow launches a workflow defined on the Linked API side, and your scenario carries on once that step has run.

When to use it
your team already chains several Linked API steps and wants Make to start them as one block.
Watch out
Make's documentation says nothing about how that workflow is described, so check Linked API's own documentation before you build on it.
Linked API4

Fetch a Company

ActionIn the docs only

Need the facts about one company halfway through a scenario? Fetch a Company pulls a single company record into Make, ready to be written into your CRM or a spreadsheet by the next module.

When to use it
a new account enters your pipeline and the team wants its profile attached to it.
Watch out
it returns one company, not a list; reach for Search Companies when all you have are criteria.
Linked API5

Fetch a Company in Sales Navigator

ActionIn the docs only

Fetch a Company in Sales Navigator does the job of Fetch a Company but reads the account from Sales Navigator, so your records match the view your sellers already prospect from.

When to use it
account executives qualify targets inside Sales Navigator and want Make to copy that picture into the CRM.
Watch out
choose one of the two company fetch modules per scenario and keep it, otherwise the same record ends up filled from two sources.
Linked API6

Fetch a Person

ActionIn the docs only

With Fetch a Person, one profile becomes a bundle Make can pass along, so the next module can file it in a CRM, a sheet or a message draft.

When to use it
someone fills in your demo form and you want to know who is behind the name before the call.
Watch out
every fetch costs an operation, so avoid looking up the same person again each time the scenario runs.
Linked API7

Fetch a Person in Sales Navigator

ActionIn the docs only

Recruiters and sellers who work in Sales Navigator get the person as that tool shows them, thanks to Fetch a Person in Sales Navigator, rather than the standard profile.

When to use it
your outreach lists come from Sales Navigator searches and you want enrichment to stay on that side.
Watch out
follow it with Send a Message in Sales Navigator rather than Send a Message, so the whole flow stays in one channel.
Linked API8

Fetch a Post

ActionIn the docs only

Fetch a Post turns one post into data your scenario can use: store it, pass it to another app for a summary, or react to it further down the chain.

When to use it
a post worth tracking shows up in a shared sheet and you want its content archived with it.
Watch out
it reads a single post, and nothing in this app watches a feed for new ones, so another module has to supply the post to fetch.
Linked API9

Get Actions Statistics

ActionIn the docs only

Get Actions Statistics gives you, as its name suggests, a read on the activity of your Linked API account, which saves you from copying numbers out of the dashboard.

When to use it
at the end of an outreach campaign, to write the latest activity into the sheet your manager reads.
Watch out
the documentation doesn't list which statistics come back, so check the bundle after a Run once before mapping anything.
Linked API10

Make a REST API Call

ActionIn the docs only

When no other module in the list covers your case, Make a REST API Call is the way out: as its name says, it sends a request you write yourself to the Linked API REST API.

When to use it
a Linked API feature appears in their documentation but has no dedicated module in Make.
Watch out
you build the request by hand, so keep Linked API's API reference open; the generic Make an API Call module is not offered for this app.
Linked API11

Poll Conversations

ActionIn the docs only

Despite the word poll, Poll Conversations is an action in Make, not a trigger: it brings back your conversations at the moment the scenario reaches it.

When to use it
as the first Linked API step of a scheduled scenario, to check your inbox each time the schedule fires.
Watch out
since the app has no trigger, a reply only reaches Make on the next scheduled run, every 15 minutes by default.
Linked API12

React to a Post

ActionIn the docs only

React to a Post leaves a reaction on one post, a light touch that keeps you on a prospect's radar without writing a word.

When to use it
after Fetch a Post, when the post comes from an account the team is warming up before a first message.
Watch out
if the scenario reads the same post twice, it will try to react twice, so keep a list of the posts already handled.
Linked API13

Remove a Connection

ActionIn the docs only

Remove a Connection ends your link with one person in your network. It keeps the network clean; undoing it means sending a new Send a Connection Request and waiting for an answer.

When to use it
a contact is marked lost or unsubscribed in the CRM and the team wants the network to match.
Watch out
this is about people in your network, not the Make connection that links your Linked API account to Make.
Linked API14

Retrieve Connections

ActionIn the docs only

Retrieve Connections hands your scenario the people you are already connected with, so your network can be copied into a CRM or a spreadsheet.

When to use it
when you first set up your CRM and want it seeded with the contacts you already have.
Watch out
if many people come back, each travels as its own bundle, and every module after it spends an operation per bundle.
Linked API15

Retrieve Pending Requests

ActionIn the docs only

Pending invitations pile up quietly. Retrieve Pending Requests brings them into Make so you can decide, one by one, which to keep and which to drop.

When to use it
before Withdraw a Connection Request, to clear stale invitations out of the queue.
Watch out
the documentation doesn't say whether received invitations are included alongside the ones you sent; read the first bundles from a Run once to find out.
Linked API16

Retrieve Performance

ActionIn the docs only

Retrieve Performance pulls performance figures from Linked API into your scenario, which spares you rebuilding a report by hand after each campaign.

When to use it
a campaign ends and you want its results in the same sheet as your other channels.
Watch out
nothing in Make's documentation describes which metrics you get, so look at a real output before designing a report around it.
Linked API17

Retrieve SSI

ActionIn the docs only

Retrieve SSI brings the SSI indicator into Make, so it can sit next to the rest of your sales numbers instead of living in screenshots.

When to use it
a sales manager follows SSI across the team and wants it collected without asking each rep.
Watch out
Make's documentation for this module stops at its name; confirm with Linked API what the value covers before you compare people on it.
Linked API18

Search Companies

SearchIn the docs only

Search Companies finds companies that match what you ask for and returns zero, one or several of them, each as a separate bundle.

When to use it
building a target account list for a new market before anyone starts outreach.
Watch out
a broad search can return a lot of bundles, and each module after it runs once per bundle, which adds operations quickly.
Linked API19

Search Companies in Sales Navigator

SearchIn the docs only

Search Companies in Sales Navigator runs the account search in Sales Navigator instead of the standard search, handy when your prospecting already happens there.

When to use it
account executives keep their target lists in Sales Navigator and want the results pushed into a shared sheet.
Watch out
send the results to Fetch a Company in Sales Navigator rather than the standard fetch, so every record comes from one source.
Linked API20

Search People

SearchIn the docs only

Search People returns the people who match a search, from none to many, one bundle each, ready for enrichment or a message.

When to use it
a new role opens and recruiting wants a first list of candidate profiles in a sheet.
Watch out
a search that finds nobody returns zero bundles, and the rest of the scenario simply doesn't run on that pass.
Linked API21

Search People in Sales Navigator

SearchIn the docs only

For sellers on Sales Navigator, Search People in Sales Navigator returns leads straight from that tool, so the list Make works on matches the one the team sees.

When to use it
an SDR prepares a sequence and wants each lead handed to Fetch a Person in Sales Navigator.
Watch out
a message to every result is easy to build and impossible to recall, so test on a very narrow search first.
Linked API22

Send a Connection Request

ActionIn the docs only

Send a Connection Request invites one person to join your network the moment the scenario reaches it, with no tab switching for the rep.

When to use it
a lead is marked qualified in your CRM and the account owner wants the invitation out right away.
Watch out
run Check a Connection Status first, or you may invite someone who is already in your network.
Linked API23

Send a Message

ActionIn the docs only

Send a Message delivers a direct message to one person, with text you can assemble from earlier modules, like a first name or a company.

When to use it
after an event such as a demo booked or a webinar attended, to follow up where the relationship started.
Watch out
Run once sends a real message, so test on a colleague and read the mapped text in the bundle before switching on.
Linked API24

Send a Message in Sales Navigator

ActionIn the docs only

Send a Message in Sales Navigator writes to a lead from Sales Navigator instead of the standard inbox, keeping the conversation where your sales history already sits.

When to use it
your reps prospect in Sales Navigator and the follow-up should appear in the same place.
Watch out
pick this module or Send a Message for a given lead, not both, or the same person hears from you in two inboxes.
Linked API25

Sync a Conversation

ActionIn the docs only

Sync a Conversation brings one conversation into Make so its messages can be stored in your CRM next to the contact.

When to use it
a prospect replies and the account owner wants the exchange kept on the record without copying and pasting.
Watch out
it handles one conversation at a time; Poll Conversations is the module that looks across the whole inbox.
Linked API26

Sync a Conversation in Sales Navigator

ActionIn the docs only

Keeping Sales Navigator threads in your CRM is the job of Sync a Conversation in Sales Navigator: one conversation per run, taken from the Sales Navigator inbox.

When to use it
a deal moves forward and the full exchange with the lead should be attached to it.
Watch out
by its name, the standard Sync a Conversation targets the regular inbox, so match the module to where the message was sent.
Linked API27

Withdraw a Connection Request

ActionIn the docs only

Withdraw a Connection Request takes back an invitation that is still waiting, which keeps your pending list short and your outreach tidy.

When to use it
right after Retrieve Pending Requests, for invitations the team no longer wants to leave open.
Watch out
once withdrawn, the invitation is gone; the only way back is a fresh Send a Connection Request.
Need help

Need help automating Linked API with Make?

A person reads every message.

FAQ

Linked API and Make: common questions

01Is the Linked API Make integration free?
Yes on the Make side: Linked API is a standard app, available from the Free plan. That plan gives you 2 active scenarios, at least 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and count usage in credits each month. Linked API is a separate subscription: you need an active account, and its own pricing page gives the details.
02What is needed to connect Linked API to Make?
An active Linked API account and two values from its dashboard, the API token and the Identification Token. In Make, add any Linked API module, click Create a connection, optionally fill in the Connection name field, then paste the credentials or follow the on-screen instructions. The connection is created once, and every Linked API module in your scenarios reuses it. If the account isn't active yet, sign up with Linked API and check its pricing page before building anything.
03Does Linked API trigger Make scenarios in real time?
No. Linked API has no trigger module in Make, neither scheduled nor instant, so nothing on the Linked API side can start a scenario by itself. You still have two ways in: open the scenario with another app's trigger, such as a new CRM record or a form entry, or let Make run it on a schedule, every 15 minutes by default, with 15 minutes as the floor on the Free plan and 1 minute on paid plans. Poll Conversations is an action, so it checks when the scenario runs, not when a message arrives.
04What if a Linked API module is missing in Make?
It depends on what is missing. The app has no generic Make an API Call module, but its list includes Make a REST API Call, which, as the name indicates, lets you send your own request to Linked API. Keep in mind that Make's documentation for this app is AI-generated and flagged as possibly containing mistakes, so check with Linked API what the service really supports. If the gap sits elsewhere in the flow, a module from another app or a hand from the team can fill it.
05Make or n8n for Linked API?
It depends on your criteria. On Make, the 27 modules are ready to use, 23 actions and 4 searches set up through one connection with no code, and the app is available from the Free plan. The same app often has an n8n node too, so check whether one exists for Linked API before you decide. Then compare what each tool offers for the exact steps you need and the plan you already pay for. Neither choice changes what Linked API itself allows you to do.
Same platform

Other docs you might need on this stack.

Browse all integrations