Resources · Make integration

Dropcontact Make integrationAutomate Dropcontact with Make.

Can Make send your new leads to Dropcontact without a copy and paste? Yes. The Dropcontact Make integration gives you 4 modules: 2 actions and 2 searches. This guide shows what each one is for, how to plug in your API key, and how to build a first scenario.

Try the Dropcontact integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Dropcontact Make integration let you automate?

The Dropcontact Make integration links your Dropcontact account to Make, a no-code tool where you build a scenario (the automation itself, a chain of steps) out of modules (one brick per step). Here, the modules send contacts to Dropcontact and read them back, so no one has to export a file and upload it by hand.

Leads from a form, processed on arrival. A sales team collects demo requests in another app. Each new request goes to Create a Contact (synchronous), which waits for Dropcontact's answer and passes it straight to the next module, for example your CRM.

A long list, sent without babysitting. A marketing ops lead has a sheet of event attendees. Create a Contact (asynchronous) hands every row over without waiting, and the names suggest Get a Contact reads the results back later, a lead to confirm with Run once.

The endpoint nobody packaged. When the three ready-made modules stop short, Make an API Call reaches the rest of the Dropcontact API with the same connection.

Two limits to know before you start. Dropcontact has no trigger in Make, so the scenario always starts from another app or from a schedule. And Make's own documentation page for Dropcontact warns that it is AI-generated and may contain mistakes, so check anything important with Dropcontact directly. New to the editor? The Make training covers the basics. Dropcontact also has an n8n node, described on the Dropcontact n8n integration page, and the n8n vs Make comparison helps you pick a tool.

Connect

How do you connect your Dropcontact account to Make?

  1. 01

    Copy your API key

    You need an active Dropcontact account with a developer API key. Log in to Dropcontact, open the API tab, and copy the key shown on that page. Keep it at hand for the next step.

  2. 02

    Add a Dropcontact module

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

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the on-screen instructions, then save. From now on, every Dropcontact module in any of your scenarios can pick this connection from a list.

First scenario

Your first scenario with Dropcontact

GoalWhen a new lead shows up in the app where you collect them, Make sends it to Dropcontact and hands the answer to your next step.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Dropcontact has no trigger, this first module comes from the app where your leads land.

  2. 02

    Pick the lead source

    Search that app by name and choose the module that watches new records. Connect it the same way: Create a connection, then fill in what Make asks for, such as the sheet or list to watch.

  3. 03

    Add Create a Contact (synchronous)

    Click the + on the right of the first module, search Dropcontact, and pick Create a Contact (synchronous). Select your connection, then map the lead data from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received (a bundle is one item passed along, here one contact). Read what Dropcontact sent back before going further.

  5. 05

    Schedule and switch it on

    Open the clock on the first module and set the schedule, every 15 minutes by default. Then switch the scenario on. Each module run counts as an operation, the unit Make bills on your plan.

Modules

What each Dropcontact module does

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

Dropcontact1

Create a Contact (asynchronous)

Action

In Make“Creates a new contact asynchronously.”

Hands a contact over to Dropcontact and lets the scenario move on without waiting for the processed version.

When to use it
you push a long list from a spreadsheet or a CRM export and the next module does not need Dropcontact's answer right away.
Watch out
nothing processed comes back here. The module names point to Get a Contact as the follow-up step; treat it as a lead and check its output with Run once.
Dropcontact2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Dropcontact API to your scenario and reuses the connection you already set up, so there is no second key to paste anywhere.

When to use it
the thing you need is not covered by the three ready-made modules on this page.
Watch out
you write the request yourself, so keep Dropcontact's API documentation open next to the editor. It is the only Dropcontact module here that expects you to read an API reference.
Dropcontact3

Create a Contact (synchronous)

Search

In Make“Creates a new contact synchronously.”

Submits one contact and waits for Dropcontact's response inside the same module. Make files it as a search, which means it passes one or more bundles on to the next module instead of only confirming a write.

When to use it
a fresh lead from a form that you want to forward, answer included, to your CRM in the very next step.
Watch out
a search can also return zero bundles, so add a filter before the next module to skip empty results.
Dropcontact4

Get a Contact

Search

In Make“Retrieves a Contact.”

Reads back a contact that Dropcontact already received. The names hint that it pairs with the asynchronous creation module; confirm that with Run once before relying on it.

When to use it
in a separate scenario, or further down the same one, when you want the processed version of contacts you submitted earlier.
Watch out
as a search, it can come back empty. Try it with Run once on a contact you know was sent, and read the bundle before mapping anything downstream.
Need help

Need help automating Dropcontact with Make?

A person reads every message.

FAQ

Questions people ask about Dropcontact and Make

01Is the Dropcontact Make integration free?
Yes, on the Make side. Dropcontact is a standard app, available from the Free plan, like the 3,000+ standard apps Make offers on every plan. The Free plan allows 2 active scenarios, no more than one scheduled run every 15 minutes, and 5 minutes per execution. Paid plans go down to a 1 minute interval with unlimited active scenarios. Make counts usage in operations, one per module run. Dropcontact itself needs an active account with an API key, and its subscription is set on Dropcontact's own pricing page.
02What does it take to connect Dropcontact to Make?
Two things: an active Dropcontact account and a developer API key. You find the key in the API tab of your Dropcontact account and copy it as is. In Make, add any Dropcontact module, click Create a connection, give it a name if you like, and paste the key. The connection is then shared by the 4 Dropcontact modules, so you set it up once and pick it from a list in every new scenario you build afterwards.
03Can Dropcontact start a scenario in real time?
No, not by itself. Dropcontact has no trigger module in Make, neither scheduled nor instant, so it cannot launch a scenario on its own. The start comes from somewhere else. Either another app's trigger fires when a new lead appears there, and it may be instant if that app offers a webhook, or the scenario runs on Make's schedule, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans allow 1 minute.
04Is there a way past the 4 Dropcontact modules in Make?
Yes, through Make an API Call. This module calls any endpoint of the Dropcontact API with the connection you already created, so it covers what the two creation modules and Get a Contact leave out. You will need Dropcontact's API documentation to write the request. One more point: Make's documentation page for this app says it was AI-generated and may contain mistakes, so when a detail matters, confirm it with Dropcontact before you build around it.
05Make or n8n: which fits Dropcontact better?
It depends on where your other automations already run. Dropcontact exists on both: 4 modules in Make, including Make an API Call, and an n8n node described on a separate page of this site. The honest criterion is your team's habits. If your lead sources and CRM are already wired in Make scenarios, adding Dropcontact there keeps everything in one place. If your team builds in n8n, stay there. Neither choice changes what Dropcontact does with the contacts you send.
Same platform

Other docs you might need on this stack.

Browse all integrations