Resources · Make integration

Contacts+ Make integrationAutomate Contacts+ with Make.

Want your address book to keep itself tidy? The Contacts+ Make integration gives you 17 modules, 7 of them triggers, to act on contacts and tags. This guide connects your account and walks you through a first working scenario.

Try the Contacts+ integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Contacts+ Make integration do for you?

The Contacts+ Make integration links your Contacts+ account to Make so that contacts and tags move on their own. In Make you build a scenario, the automation itself, out of modules: each module is one brick that watches, creates, updates or searches something in Contacts+ or in another app.

Follow up with every new contact. Watch Contacts Created notices each contact added to your account, and Add Tags to the Contact labels it right away, so your sales list builds itself instead of waiting for a cleanup session.

Turn a scanned business card into a lead. Watch Business Card Transcribed starts a scenario once a card you captured has been turned into text. From there, Update a Contact or Add Tags to the Contact put that person where your team will see them.

Keep your tag system consistent. Watch Tags Created, Watch Tags Updated and Watch Tags Deleted let you mirror any change to your labels in another tool, while Create a Tag and Update a Tag push changes the other way.

What this integration does not cover: the Make documentation lists the triggers without their type, and going by their names they are all scheduled: Make checks Contacts+ at intervals rather than hearing about changes the moment they happen. Anything the 17 modules leave out can still be reached with Make an API Call. If you are weighing tools, the n8n vs Make comparison lays out the criteria, and the Make pricing page explains how operations are counted. Stuck on a run that fails? Head to Make troubleshooting.

Connect

How do you connect Contacts+ to Make?

  1. 01

    Register an app in Contacts+

    Log in to Contacts+, open the Developers section and create a new application. Paste the callback URI given by the Make documentation, then copy the Client ID and the Client secret it shows you.

  2. 02

    Open a connection in Make

    In your scenario, add any Contacts+ module and click Create a connection. A connection is your Contacts+ account linked to Make once, then reused by every Contacts+ module. The Connection name field is optional.

  3. 03

    Enter your credentials

    Paste the Client ID and Client secret you copied from Contacts+, or follow the instructions Make shows on screen. Once the connection is saved, the module can read your contacts and tags.

First scenario

Your first scenario: tag every new Contacts+ contact

GoalWhen a contact is created in Contacts+, Make adds your follow-up tags to that contact.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add your first module.

  2. 02

    Pick the trigger

    Search for Contacts+, choose Watch Contacts Created and click Create a connection, or pick the connection you already made.

  3. 03

    Add the tagging step

    Click the + on the right of the trigger and add Add Tags to the Contact. Map the contact coming from the trigger, then fill in the tags you want on every new entry.

  4. 04

    Test with Run once

    Click Run once, then add a test contact in Contacts+. Open each module's bubble to read the bundles it received: a bundle is one item, here one contact, passed along.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Make will then check for new contacts at that pace.

Triggers

What can start a Contacts+ scenario?

7 modules start a scenario when something happens in Contacts+. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Contacts+ as soon as it happens.

Contacts+1Watch Business Card Transcribed

Watch Business Card Transcribed

triggerIn the docs only

You get a scenario that picks up each business card once Contacts+ has turned it into text, so the people you met at an event reach your pipeline without anyone retyping them.

How it fires
scheduled. Make checks the app on the scenario's schedule, so the card appears at the next check.
When to use it
after a trade show, when a stack of scanned cards needs to be routed to sales or to a follow-up list.
Watch out
the Make documentation gives no detail about what this trigger returns, so run it once on a real card and read the bundle before mapping anything.
Contacts+2Watch Contacts Created

Watch Contacts Created

triggerIn the docs only

Every contact that lands in your Contacts+ account becomes the starting point of an automation: a welcome tag, a copy in your CRM, a message to the account owner.

How it fires
scheduled. Make checks the app on the scenario's schedule and collects the contacts added since the last check.
When to use it
when new contacts should be processed the same way every time, whoever added them.
Watch out
each new contact is one bundle, and each module that handles it costs one operation, the unit Make counts on your plan.
Contacts+3Watch Contacts Deleted

Watch Contacts Deleted

triggerIn the docs only

Removals stop being silent. This trigger tells your scenario which contacts disappeared from Contacts+, so the other tools that hold a copy can follow.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns the deletions it finds.
When to use it
when a mailing list or a spreadsheet must stop showing people your team has dropped from the address book.
Watch out
the contact is gone from Contacts+, so expect Get a Contact to find nothing; build on what the trigger's bundle carries, and check it with Run once.
Contacts+4Watch Contacts Updated

Watch Contacts Updated

triggerIn the docs only

Changes to an existing contact, like a new job title or a corrected email, reach the rest of your stack without anyone copying them by hand.

How it fires
scheduled. Make checks the app on the scenario's schedule and picks up the contacts edited since the previous run.
When to use it
to keep a CRM or a shared sheet aligned with Contacts+ when your address book is the reference.
Watch out
if the same scenario runs Update a Contact on those contacts, it edits them again and can wake itself up on the next check. Write to another app, or add a filter.
Contacts+5Watch Tags Created

Watch Tags Created

triggerIn the docs only

A new label in Contacts+ can open the matching list, segment or folder elsewhere, so your tag system is set up once and mirrored everywhere.

How it fires
scheduled. Make checks the app on the scenario's schedule and lists the tags created since the last pass.
When to use it
when each tag stands for a segment that also has to exist in your emailing tool or in your CRM.
Watch out
this trigger reacts to the tag itself, not to contacts receiving it; watch contacts if you care about who is tagged.
Contacts+6Watch Tags Deleted

Watch Tags Deleted

triggerIn the docs only

When someone removes a label from Contacts+, your scenario learns about it and can retire the segment, list or column that depended on it.

How it fires
scheduled. Make checks the app on the scenario's schedule and reports the tags that are gone.
When to use it
to avoid orphan lists in other tools after your team trims the tag set.
Watch out
the tag is gone from Contacts+, so do not count on Get a Tag to read it; map what the trigger's bundle carries, after checking it with Run once.
Contacts+7Watch Tags Updated

Watch Tags Updated

triggerIn the docs only

A renamed or edited tag stays in sync across your tools, because the scenario receives the new version each time the label changes.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns the tags modified since the last check.
When to use it
when your tags double as segment names in another app and a rename has to follow there too.
Watch out
avoid calling Update a Tag on the same tags inside this scenario, or each edit triggers another round.
Modules

What can Make do in Contacts+?

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

Contacts+1

Add Tags to the Contact

ActionIn the docs only

This module labels a contact for you, so you can sort people by source, status or owner without opening Contacts+ one card at a time.

When to use it
right after a trigger hands you a contact, to mark where it came from or what should happen next.
Watch out
it only adds; to take a label off, use Remove Tags from the Contact, and check the result with Run once on a test contact.
Contacts+2

Create a Contact

ActionIn the docs only

People who fill a form, book a call or buy from you end up in your Contacts+ address book, with no copy and paste in between.

When to use it
when another app is where contacts first appear and Contacts+ should hold the clean record.
Watch out
nothing in the documentation says this module checks for duplicates, so search with List Contacts first if the person may already exist.
Contacts+3

Create a Tag

ActionIn the docs only

Your labels get created from a scenario instead of by hand, which keeps their names identical to the segments or campaigns they match in other tools.

When to use it
when a new campaign, event or client segment appears elsewhere and deserves its own tag in Contacts+.
Watch out
run it before Add Tags to the Contact in the same flow, so the label is there when the contact needs it.
Contacts+4

Get a Contact

ActionIn the docs only

You retrieve the full record of one precise contact, useful when an earlier step only gave you a reference and the next one needs the details.

When to use it
after a trigger or a search, to fetch that person in full before you write the details anywhere else, such as a CRM record or a shared sheet.
Watch out
it targets a single contact you already identified; to find someone by criteria, List Contacts is the right module.
Contacts+5

Get a Tag

ActionIn the docs only

This module reads one tag from Contacts+, so the rest of the scenario can check it or reuse its details in another tool.

When to use it
when a tag reference reaches you from a trigger and you need its current state before acting.
Watch out
a deleted tag is gone from Contacts+, so do not count on it after Watch Tags Deleted.
Contacts+6

List Contacts

SearchIn the docs only

You search your address book from a scenario and get back the matching contacts, which lets you check whether someone exists before creating or updating them.

When to use it
ahead of Create a Contact, to avoid a second copy of the same person.
Watch out
as a search, it can return zero, one or several contacts, each one a separate bundle, and every following module then runs once per contact.
Contacts+7

Make an API Call

ActionIn the docs only

When the listed modules stop short, this one lets you call any endpoint of the Contacts+ API from your scenario, with the same connection you already set up.

When to use it
for an operation none of the other listed modules covers, once you have found the right endpoint in the Contacts+ API documentation.
Watch out
you write the request yourself, so test it with Run once and read the response before switching the scenario on.
Contacts+8

Remove Tags from the Contact

ActionIn the docs only

Labels come off a contact automatically, so a status such as "to call" disappears the moment it is no longer true.

When to use it
when an event in another app, a signed deal or a closed ticket, means the old tag is out of date.
Watch out
test it with Run once on a test contact and look at which labels remain before switching the scenario on.
Contacts+9

Update a Contact

ActionIn the docs only

An existing contact gets corrected or completed from your scenario, keeping Contacts+ in line with what the rest of your tools know.

When to use it
when someone changes company or phone number in your CRM and the address book should follow.
Watch out
combined with Watch Contacts Updated in the same scenario, it can restart the flow on every edit, so filter or split the scenarios.
Contacts+10

Update a Tag

ActionIn the docs only

Renaming or editing a label happens from Make, which keeps Contacts+ tags matching the segment names used in your other apps.

When to use it
when a campaign or segment is renamed elsewhere and the tag should carry the new name.
Watch out
a scenario started by Watch Tags Updated that also runs this module will keep triggering itself.
Need help

Need help automating Contacts+ with Make?

A person reads every message.

FAQ

Contacts+ and Make: common questions

01Is the Contacts+ Make integration free?
Yes, on the Make side. Contacts+ is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need an active Contacts+ account, whose subscription is handled by Contacts+ itself, not by Make.
02What do you need to connect Contacts+ to Make?
An active Contacts+ account and an app registered in its Developers section. There you enter the callback URI given in the Make documentation, then copy the Client ID and the Client secret. In Make, add a Contacts+ module, click Create a connection, optionally name it, and paste those two values or follow the instructions on screen. That connection is then reused by every Contacts+ module in your scenarios, so you only set it up once.
03Does the Contacts+ Make trigger fire in real time?
No. The documentation does not state the trigger types, but going by their names all 7 Contacts+ triggers are scheduled: Make checks your account on the scenario's schedule instead of being notified by Contacts+ when something changes. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans allow checks as often as every minute. If a delay between a change and the reaction is a problem, pick the shortest interval your plan permits.
04What if a Contacts+ module is missing in Make?
Use Make an API Call. It calls any endpoint of the Contacts+ API from your scenario, with the connection you already created, so a feature the 17 listed modules leave out is still within reach. You write the request from the Contacts+ API documentation, then test it with Run once before activating. For a limit that comes from your Make plan rather than from the app, such as the interval between scheduled runs, the answer is a different plan.
05Should you use Make or n8n for Contacts+?
It depends on your criteria rather than on a winner. On Make, Contacts+ comes with 17 modules, including 7 scheduled triggers and Make an API Call, and it works from the Free plan. The same app often has an n8n node too, so check the n8n catalog before you decide. Compare the modules each tool offers for your exact use case, how you prefer to build, and which plan fits your volume of operations.
Same platform

Other docs you might need on this stack.

Browse all integrations