Diabolocom Make integrationAutomate Diabolocom with Make.
Can your call campaigns fill themselves with fresh contacts? The Diabolocom Make integration gives you 15 modules, 11 actions and 4 searches, to manage campaign contacts and read your setup. This guide walks ops teams through the connection and a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Diabolocom Make integration do for you?
The Diabolocom Make integration links your Diabolocom account to Make so a scenario, the automation you build in Make, can add, update, read and delete campaign contacts without anyone typing them in. Each step of that scenario is a module: one brick that does one job, such as creating a contact.
Campaigns that load themselves. When a lead comes in through a form or a CRM, Create a Contact drops it straight into the right Diabolocom campaign, so agents call people while the interest is still warm.
Contact records that stay current. A customer changes details in your billing tool, and Update a Contact carries the change over. When a list goes stale, Delete a Batch of Contacts clears it in one move instead of record by record.
Reporting on your own setup. List Campaigns, List Users and List Wrap-Ups pull your configuration into a spreadsheet, which helps anyone building reports on call outcomes.
Know the limits before you start. Make itself flags the Diabolocom documentation as limited, and the app has no trigger: Diabolocom cannot start a scenario on its own. Your scenario begins with another app or with a schedule. If you are new to the editor, the Make training covers the basics, and Make troubleshooting helps when a run fails.
Weighing tools? The n8n vs Make comparison sets out the criteria side by side.
How do you connect Diabolocom to Make?
- 01
Add a Diabolocom module
In your scenario, add any Diabolocom module, for instance Create a Contact, then click Create a connection. A connection is your Diabolocom account linked to Make once, and every Diabolocom module reuses it afterwards.
- 02
Name it and authorize
Give the connection a name if you like, which helps when several accounts are in play. Then either authorize Make on the Diabolocom page that opens, or paste the key Diabolocom provides, depending on what the window asks for.
- 03
Save and check
Click Save. Back in the module, Make should now offer the campaigns it can read in your account; if the list appears, the connection works.
Your first scenario with Diabolocom
GoalWhen a new lead appears in another app, Make adds it as a contact in a Diabolocom campaign.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the +. Since Diabolocom has no trigger, the first module comes from the app where your leads arrive, like a form tool or a CRM.
- 02
Add Create a Contact
Click the + on the right of that first module, search for Diabolocom and pick Create a Contact. Click Create a connection if you have not linked your account yet.
- 03
Pick the campaign and map the lead
Choose the campaign that should receive the contact. Then map the lead details from the first module into the fields Make displays, so each new lead becomes one bundle, one contact, in Diabolocom.
- 04
Test with Run once
Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can open the campaign and check the new contact is there.
- 05
Schedule it and switch it on
Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on. Each module run on a bundle counts as one operation on your plan.
What each Diabolocom module does
Diabolocom gives you 15 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a Contact
ActionIn Make“Creates a new contact in a specified campaign.”
Adds a person to a campaign you choose, so your agents get a new number to call without anyone copying it from another tool. It is the module most scenarios with Diabolocom end on.
Create New Campaign Field(s)
ActionIn Make“Creates new fields in a campaign.”
With this module you extend a campaign by adding fields to it, which gives you room to store details your agents need on screen during a call. It changes the campaign itself, not a contact.
Delete a Batch of Contacts
ActionIn Make“Deletes multiple contacts in a specific campaign.”
Clearing many contacts from one campaign in a single step is what this module is for, and it saves you a loop of single deletions. Your campaign then holds only the people worth calling.
Delete a Contact
ActionIn Make“Deletes a campaign contact by ID.”
Removes one contact from a campaign using its ID, so nobody calls a person who asked not to be contacted again. Choose it over the batch module when the event concerns a single person.
Get a Campaign
ActionIn Make“Gets single campaign by ID.”
Fetches the details of one campaign from its ID, so the next modules can use its information instead of you checking it by hand in Diabolocom. It reads, and changes nothing.
Get a Contact
ActionIn Make“Gets single campaign contact by ID.”
You get the full record of one campaign contact back from its ID, ready to copy into another app or to test before acting. Use it when you already hold the ID and want what Diabolocom knows about that person now.
Get a Group
ActionIn Make“Gets single group by ID.”
Returns a single group of your Diabolocom account from its ID, handy when a scenario must say which team handles something. It is the one-record version of List Groups.
Get a User
ActionIn Make“Gets single user by ID.”
Looks up one Diabolocom user by ID and hands their details to the rest of the scenario, so you can turn an ID into a real person. Pair it with modules that only give you the user ID.
Get a Wrap-Up Code
ActionIn Make“Gets single wrap-up code by ID.”
Translates a wrap-up code ID into its full details, so a spreadsheet or a CRM receives something readable instead of a raw ID. It reads a single code at a time.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Covers whatever the listed modules leave out: it calls any endpoint of the Diabolocom API with the connection you already set up. You describe the request yourself, so it suits someone comfortable reading API documentation.
Update a Contact
ActionIn Make“Updates a contact using the ID.”
Keeps a campaign contact in step with your other tools by changing the record behind a given ID. Agents then call with the right details in front of them, not outdated ones.
List Campaigns
SearchIn Make“Returns all campaigns.”
Brings back every campaign of your account, one bundle per campaign, so you can feed a sheet or pick the right one by name. As a search, it can return zero, one or many results.
List Groups
SearchIn Make“Returns all groups.”
This search collects all groups defined in Diabolocom, each one as a separate bundle. That gives your scenario the full map of your teams without clicking through the admin screens.
List Users
SearchIn Make“Returns all users.”
Pulls the complete list of users in your account, so you can compare it with your HR tool or your licence count. Every user arrives as its own bundle.
List Wrap-Ups
SearchIn Make“Returns all wrap-up codes.”
Returns all the wrap-up codes set up in Diabolocom as separate bundles, a clean base for any report on call outcomes. Use it once to build a reference table your other scenarios can read.
Need help automating Diabolocom with Make?
A person reads every message.
