Resources · Make integration

Collector Make integrationAutomate Collector with Make.

Can Make pick up your Collector leads and pass them along for you? The Collector Make integration gives you 11 modules: 1 trigger, 9 actions and 1 search. This guide shows what each one is for, how to link your account and how to build a first working scenario.

Try the Collector integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Collector Make integration do?

The Collector Make integration links your Collector account to Make, a visual tool where you chain apps together without writing code. You build a scenario, which is the automation itself, out of modules, each module being one brick: a trigger that starts things, an action or a search. Collector brings 11 of those bricks, all centered on leads.

Hand every new lead to the rest of your stack. Watch New Leads spots leads that appear in Collector, and the next module in your scenario can send each one wherever your sales team works. Each lead travels as a bundle, meaning one item passed from a module to the next.

Keep a lead record up to date from another tool. When a deal moves in another app, Update a Lead can write the change back to Collector, so nobody retypes it by hand.

Pull the full picture before acting. Retrieve a Lead, Retrieve a Note by Lead ID or Retrieve a Follow Up by Lead ID gather what is already known about a person before an email or a task goes out.

Be aware that Make's own documentation for Collector is limited: it says there is not enough public information about the app to describe it in detail. The module list is solid, but field-level detail is thin, so test each step before relying on it. If you are weighing tools, the n8n vs Make comparison lays out the differences, and the Make pricing page explains how usage is counted.

Connect

How do you connect Collector to Make?

  1. 01

    Add a Collector module

    In your scenario, add any Collector module, for example Watch New Leads, then click Create a connection. A connection is your Collector account linked to Make once and reused by every Collector module afterwards.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when a team shares several accounts. Then either approve access on the Collector page that opens, or paste the key Collector gives you, depending on what the window asks for.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now read your Collector account and offer its data in the fields, which is a quick sign that the link works before you go further.

First scenario

Your first scenario with Collector

GoalWhen a new lead lands in Collector, Make reads its record and writes an update back to that lead.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module. Search for Collector and choose Watch New Leads as the starting point.

  2. 02

    Link your account

    Click Create a connection and authorize Make. Once the connection exists, fill the trigger's fields; Make lists what it can read from your Collector account.

  3. 03

    Read the lead's record

    Click the + to the right of the trigger and add Retrieve a Lead. Map the lead identifier from the trigger's output so Make fetches the right person.

  4. 04

    Write the update

    Add Update a Lead after it and map the values you want changed, taken from the two earlier modules. Keep it to one or two fields on the first try.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time, and you can open each module to read the bundles it received. Check that the update hit the lead you expected.

  6. 06

    Schedule and switch on

    Open the clock on the first module; a new scenario runs every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Then switch the scenario on.

Triggers

What starts a Collector scenario

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

Collector1Watch New Leads

Watch New Leads

triggerIn the docs only

You get each fresh Collector lead delivered to your scenario as its own bundle. Make's documentation lists this trigger without describing it, and its scheduled type is inferred from its name, so treat its exact output as something to confirm with a first test.

How it fires
scheduled, Make checks the app on the scenario's schedule, the clock badge on the module, every 15 minutes by default.
When to use it
whenever a lead entering Collector should kick off follow-up work elsewhere, such as alerting a sales rep or logging the contact in a spreadsheet.
Watch out
on the Free plan the gap between two checks cannot go below 15 minutes, so a new lead is picked up at the next check, not the second it appears.
Modules

What the Collector modules can do

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

Collector1

Create a New Lead

ActionIn the docs only

This one adds a lead to Collector for you, so contacts gathered in another app arrive in your pipeline without copy and paste.

When to use it
a form, a chat or an event list in another tool collects a prospect and you want Collector to hold the record.
Watch out
each run creates a new lead, so check with List Leads first if the same person might already exist.
Collector2

Get a Current User

ActionIn the docs only

Here you learn which Collector user the connection is signed in as, which helps you confirm that Make is talking to the right account.

When to use it
right after setting up a connection, or in a shared scenario where several team members each linked their own Collector account.
Watch out
it tells you about the account, not about leads; pair it with another module for real work.
Collector3

List Leads

SearchIn the docs only

You get your Collector leads back as a set, one bundle per lead, which lets the rest of the scenario handle each of them in turn.

When to use it
to review or copy existing leads, or to check whether someone is already in Collector before creating them.
Watch out
as a search, it can return zero, one or many bundles, and every module after it runs once per bundle, which counts operations.
Collector4

Make an API Call

ActionIn the docs only

With this module you can reach any part of the Collector API that the listed modules leave out, using the same connection you already set up.

When to use it
you need a Collector feature that none of the other ten modules covers.
Watch out
you write the request yourself, and Make's documentation for Collector is limited, so this is for someone who already knows Collector's API.
Collector5

Retrieve a Extra Data by Lead ID

ActionIn the docs only

Going by its name, it brings back the extra data stored against one lead, the details that sit beside the main record, so your scenario can use them.

When to use it
a downstream step, like a personalized message, needs more than the basic lead fields.
Watch out
it needs the lead's ID, so place it after a module that outputs one, such as Watch New Leads or List Leads.
Collector6

Retrieve a Follow Up by Lead ID

ActionIn the docs only

You can check what follow-up is attached to a given lead, which keeps a reminder or an alert in step with what the team already planned in Collector.

When to use it
before sending a reminder from another tool, to see whether a follow-up is already set in Collector.
Watch out
feed it a lead ID from an earlier module; without one, Make has nothing to look up.
Collector7

Retrieve a Lead

ActionIn the docs only

Pulling a single lead's record into the scenario gives later modules fresh values to map, instead of whatever was known when the trigger ran.

When to use it
just before an update or a message, when the lead may have changed since it was first picked up.
Watch out
it targets one lead, so use List Leads instead when you want a whole set.
Collector8

Retrieve a Note by Lead ID

ActionIn the docs only

Notes written on a lead in Collector come back into Make, so the context your team typed is not lost when work moves to another app.

When to use it
to carry a salesperson's remarks into a ticket, a task or a handover message.
Watch out
map the lead ID from an earlier step, and test with Run once on a lead that actually has a note.
Collector9

Retrieve an Order Detail

ActionIn the docs only

Order information held in Collector becomes available to the scenario, which lets you link a lead to what was actually bought.

When to use it
when a sale is recorded and your accounting or delivery tool needs the order's details.
Watch out
Make's documentation does not say which order fields come back, so read the bundle after a first Run once before mapping anything.
Collector10

Update a Lead

ActionIn the docs only

Changes made elsewhere are written straight onto an existing Collector lead, so the record stays accurate without anyone editing it by hand.

When to use it
a deal changes stage in another tool, or a reply arrives, and Collector should reflect it.
Watch out
an update overwrites the values you map, so map only what should change and test on one lead first.
Need help

Need help automating Collector with Make?

A person reads every message.

FAQ

Questions about the Collector Make integration

01Is the Collector Make integration free?
Yes, Collector is a standard app, so it is available on Make's Free plan. That plan allows 2 active scenarios, a minimum gap of 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) lower the gap to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Make counts usage in operations, one module running on one bundle. Collector's own subscription is a separate matter this page does not cover.
02What do you need to connect Collector to Make?
You need a Collector account and a Make account. Make's documentation lists no specific prerequisite for Collector. You add a Collector module, click Create a connection, optionally name it, then either authorize Make on Collector's page or paste the key Collector provides, and click Save. Every Collector module in your scenarios then reuses that single connection. If something fails, check that you are signed into the right Collector account, then start the connection again from the module.
03Does the Collector trigger react in real time?
No. Going by how Make lists it, Watch New Leads is a scheduled trigger, marked with a clock badge in the editor. Make checks Collector on the scenario's schedule, which is every 15 minutes by default. On the Free plan you cannot go below 15 minutes, while paid plans allow checks as often as every minute. A new lead therefore appears in your scenario at the next check, not the instant it is created. Collector has no instant trigger in Make, the kind an app fires through a webhook.
04What if a Collector module is missing in Make?
Use Make an API Call. It lets a scenario reach any endpoint of the Collector API with the connection you already set up, which covers what the other ten modules leave out. Keep in mind that Make's documentation for Collector is limited, because not enough public information exists about the app, so you need to know Collector's API to build the request. Test each call with Run once and read the bundle it returns before mapping values into later modules.
05Should you use Make or n8n with Collector?
It depends on the tool your team already uses. On Make, Collector offers 11 modules: one scheduled trigger, nine actions and one search, plus Make an API Call for anything else. n8n often has a node for the same app, but check its catalog for Collector before choosing. Compare what each tool covers for your exact case rather than picking by reputation. Whichever you choose, the logic stays the same: a new lead starts the flow, and later steps read or update it.
Same platform

Other docs you might need on this stack.

Browse all integrations