Resources · Make integration

Nimble Make integrationAutomate Nimble with Make.

Can your CRM contacts and follow-up tasks run on their own? The Nimble Make integration gives you 7 modules: 1 trigger, 5 actions and 1 search. This guide is for sales and ops people new to Make, and it walks you from connection to a live first scenario.

Try the Nimble integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Nimble Make integration do for you?

The Nimble Make integration links your Nimble account to Make, a visual tool where you chain apps together without code. You build a scenario (the automation itself) out of modules (single bricks such as a trigger or an action), and Make then watches, creates, updates or deletes contacts and tasks in Nimble for you.

No new lead without a follow-up. On each run, Watch Contacts picks up the contacts added to Nimble, and Create a Task drops a reminder for the rep who owns the lead. Nobody has to remember to open the CRM after a busy afternoon of calls.

A CRM fed by your other tools. A demo request lands in a form app: List Contacts checks whether the person is already in Nimble, then Update a Contact or Create a Contact keeps a single clean record instead of two half-filled ones.

Erasure requests handled end to end. When someone asks to be forgotten, Delete a Contact removes them from Nimble in the same run that updates your other lists.

The listed modules only cover contacts and tasks. For anything else in Nimble, Make an API Call reaches the rest of the API with the same connection. The docs give no numeric limit for this app, so your Make plan sets the pace; the Make pricing guide explains how operations are counted. If you are still choosing a tool, read n8n vs Make first, and if you would rather learn the editor properly, the Make training starts from zero.

Connect

How do you connect Nimble to Make?

  1. 01

    Open a Nimble module

    In a scenario, click the +, type Nimble in the search box and pick any of its modules, for example Watch Contacts. Make then asks for a connection, meaning your Nimble account linked once and reused by every Nimble module.

  2. 02

    Create the connection

    Click Create a connection. You can give it a name, which helps later if you link a second Nimble account, such as a colleague's account.

  3. 03

    Authorize and save

    Follow what Make shows next: either approve access on the Nimble page that opens, or paste the key Nimble gives you. Then click Save. The module fields unlock as soon as the connection works.

First scenario

Your first scenario with Nimble

GoalWhen a new contact appears in Nimble, Make creates a follow-up task so the lead gets a call.

  1. 01

    Create the scenario

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

  2. 02

    Add Watch Contacts

    Search for Nimble, choose Watch Contacts and select your connection, or click Create a connection if this is your first Nimble module.

  3. 03

    Chain Create a Task

    Click the + on the right of Watch Contacts, pick Create a Task, then map the contact data from Watch Contacts into the task text so each reminder says who to call.

  4. 04

    Test with Run once

    Add a test contact in Nimble, then click Run once. Open the bubbles above each module to read the bundles (the items passed along) and check the task in Nimble.

  5. 05

    Schedule and switch on

    Open the clock on Watch Contacts: a new scenario runs every 15 minutes by default. Keep that or change it, then switch the scenario on so it keeps going without you.

Triggers

What starts a Nimble scenario

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

Nimble1Watch Contacts

Watch Contacts

Scheduled trigger

In Make“Triggers when new contact is created.”

Watch Contacts picks up the contacts created in Nimble and hands them to your scenario. Every fresh contact becomes a bundle, one item that the next modules can read, so its details can flow into a task or another app.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and the clock badge on the module reminds you of that.
When to use it
a rep logs a lead after a call, and the follow-up work should start without anyone copying the record by hand.
Watch out
a new contact reaches the scenario at the next check, not the second it is saved. On the Free plan 15 minutes is the shortest interval, on paid plans 1 minute.
Modules

What Make can do in Nimble

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

Nimble1

Create a Contact

Action

In Make“Creates a contact.”

Create a Contact writes a brand new record into Nimble from data another app hands over, so leads collected elsewhere stop waiting in a spreadsheet for someone to type them in.

When to use it
a webinar signup or a contact form produces a person who is not in your CRM yet.
Watch out
the docs do not say this module spots duplicates. Put List Contacts in front to check whether the person already exists.
Nimble2

Create a Task

Action

In Make“Creates a task.”

With Create a Task, your team gets a to-do in Nimble when something happens elsewhere, instead of relying on memory or a sticky note on the screen.

When to use it
right after Watch Contacts, so every new lead comes with a reminder to call.
Watch out
the task text can mix your own words with data mapped from earlier modules. Click Run once and read what arrived before you trust it.
Nimble3

Delete a Contact

Action

In Make“Deletes a contact.”

Removing a person from Nimble through Delete a Contact keeps your CRM in line with requests you log somewhere else, without anyone hunting the record down manually.

When to use it
a data erasure request or a cancelled account has to reach the CRM as well.
Watch out
Make cannot bring the contact back once the module runs. Test on a dummy record and use Run once to check which contact reaches it.
Nimble4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call is your way into the parts of Nimble that the other six modules skip: it can call any endpoint of the Nimble API while reusing the connection you already set up.

When to use it
you need something in Nimble beyond contacts and tasks, and no listed module offers it.
Watch out
you write the request yourself, so keep Nimble's API reference open and check the answer with Run once.
Nimble5

Update a Contact

Action

In Make“Updates a contact.”

Update a Contact rewrites the details of a person who already exists in Nimble, which keeps one reliable record per person rather than a trail of near copies.

When to use it
a customer changes jobs or a phone number in your billing tool, and sales should see the same thing.
Watch out
the module has to know which contact to change. Place Watch Contacts or List Contacts before it and map the contact from there.
Nimble6

List Contacts

Search

In Make“Returns a list of contacts.”

List Contacts is the search of this app: it looks through Nimble and returns zero, one or several contacts, each as its own bundle, ready for the next step.

When to use it
before Create a Contact, to check whether a person is already there, or to pull a batch you want to update.
Watch out
each module after it runs once per contact found, and every run is an operation counted on your Make plan.
Need help

Need help automating Nimble with Make?

A person reads every message.

FAQ

Nimble and Make: common questions

01Is the Nimble Make integration free?
Yes, you can start on the Free plan. Nimble is a standard app in Make, not an Enterprise one, so all 7 modules are available from day one. The Free plan still has limits: 2 active scenarios, at least 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 (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. Your Nimble subscription is a separate matter.
02What do you need to connect Nimble to Make?
A Nimble account and a Make account are enough. The Make documentation for Nimble lists no extra prerequisite and no dedicated connection steps, so you follow the generic flow: add a Nimble module, click Create a connection, name it if you like, authorize Make on Nimble's page or paste the key Nimble provides, then click Save. That connection is stored once and reused by every Nimble module in all your scenarios, so you will not repeat this for each new automation.
03Is the Nimble trigger in Make instant or scheduled?
Scheduled. Watch Contacts is a polling trigger: Make asks Nimble for new contacts on the scenario's schedule instead of being notified the moment one is saved. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest interval, while paid plans let you go down to 1 minute. In practice a contact created just after a check waits for the next one, which is fine for follow-up tasks but worth knowing if your team expects an immediate reaction.
04What if a Nimble module is missing in Make?
Use Make an API Call. The listed modules handle contacts and tasks only, but this module can reach any endpoint of the Nimble API with the connection you already have, so you are not stuck when you need something else. You will need Nimble's API reference to build the request, and testing with Run once shows exactly what comes back. The Make documentation gives no numeric limit for Nimble, so the constraints you meet will come from your Make plan, such as the run interval or the execution time.
05Should you use Make or n8n for Nimble?
It depends on what you need from the tool, not on Nimble. On Make, Nimble offers 7 modules covering new contacts, contact creation, updates, deletion, search and tasks, plus Make an API Call for the rest, and it works from the Free plan. The same app often has an n8n node too, so check which operations it covers before you choose. Compare both on the modules you actually need, on how you want to build and on how each tool counts usage, then test your first scenario on the one that fits.
Same platform

Other docs you might need on this stack.

Browse all integrations