Integrate Callingly With Make

swap_horiz Two-way integration account_tree Scenario trigger sync Two-way owner sync

Make (formerly Integromat) is an automation tool that connects your apps through workflows called Scenarios. Using Make, you can connect Callingly to thousands of other tools we don't have a native integration for — starting or scheduling calls when something happens in another app, and sending call data back out to your other tools.

supervisor_account Owners and Admins can enable integrations. Approx. reading time 5 min.

tips_and_updates
We also recommend that you check with the tool you intend to connect via Make regarding the user access you need to connect it on their side.

Connect Callingly to Make

Unlike most integrations, you set up the Make connection from the Make side using Callingly's Make app.

1.
Navigate to the New Integration page and click Connect next to Make. This creates the Make integration in Callingly, which will show as waiting to be connected until you finish the setup on Make.
2.
Open Callingly's integrations page on Make and add a Callingly module to a Scenario.
3.

Connect your Callingly account when Make prompts you. Once connected, the integration in Callingly updates to show that your Make account has been successfully connected.

info_outline
Note: You can always reopen your Make integration settings in Callingly for a direct link to Callingly's app on Make.

Callingly Modules in Make

Callingly exposes several modules you can use inside a Make Scenario:

  • Create Call. Creates or updates a lead and starts the outbound call flow, calling your team and connecting the first person to accept with the lead. You can specify which team should take the call.
  • Update Lead. Updates an existing lead (matched by phone number). Use this to add tags, update the lead's status or result, set the lead owner, or stop any scheduled calls.
  • List Teams. Returns the teams in your Callingly account, so you can select one when configuring a module.
  • List Numbers. Returns your Callingly phone numbers.

Callingly can also send data out to Make: a Scenario can subscribe to Callingly events (such as a completed call) using a webhook, letting you trigger further steps in Make whenever something happens in Callingly.

Configure Call Settings

The call settings for each Scenario — routing, retries, and schedule — are managed on the Callingly team the call is routed to, not in Make. When you use the Create Call module, choose which team the call should go to, then configure that team's settings on the Callingly Teams page.

tips_and_updates
Tip: Set up a different team for each type of lead you send through Make. Each team can have its own routing rules, retry schedule, and availability.

Next Steps

  1. Test the integration by running your Scenario with a fake lead. The Create Call module should start the outbound call flow and route the call to the team you selected.
  2. Set the call schedule. Be sure to set the schedule for when your team can receive calls. This way, nobody will receive a call outside of work hours.

Common Questions

What's the difference between Make and Zapier for Callingly?

Both let you connect Callingly to other apps through automated workflows. Make calls them Scenarios and Zapier calls them Zaps. Use whichever platform you already work in — the Callingly actions (start a call, update a lead) are the same idea in both. See our Zapier guide if you'd prefer Zapier.

How do I route calls to different teams?

Choose the team in the Create Call module, and configure that team's routing on the Callingly Teams page. To route different leads to different teams, use separate Create Call modules (or Make's routing tools) and select the appropriate team for each.

I connected Make in Callingly but it still says "waiting to be connected."

The connection is completed on the Make side. Add a Callingly module to a Scenario in Make and connect your Callingly account there. Once that's done, the status in Callingly updates automatically.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us