telli Make integrationAutomate telli with Make.
What can Make do with telli, without writing code? The telli Make integration gives you 15 action modules for contacts, calls and the auto dialer. Sales and ops teams will find here how to link the account and build a first scenario, one click at a time.
Verified Trustpilot reviews · AI, automation & growth agency
What does the telli Make integration do?
The telli Make integration links your telli account to Make, a tool where you build a scenario: an automation made of modules, each module being one brick that acts on one app. telli brings 15 modules, all of them actions, and their names cover three areas: contacts, calls you schedule, and the auto dialer.
Every new lead gets a call planned. A form or a CRM in another app starts the scenario, Add a Contact creates the person in telli, and Schedule a Call books the call right after. When leads arrive as a list, Add multiple Contacts and Schedule multiple Calls do the same job in bulk.
Two tools, one version of each contact. A sales rep edits a record in your CRM; Get a Contact by External ID finds its twin in telli, then Update a Contact or Delete a Contact brings telli in line.
Closed deals stop ringing. Once a prospect signs, Remove from Auto Dialer takes that person off the auto dialer, going by the module's name, so nobody calls a customer to sell them what they just bought.
What you will not find here: a trigger. None of the 15 modules can start a scenario on its own, and Make marks the telli documentation as limited, with no field described for any module. Test each one with Run once before you rely on it. Many apps also have an n8n node; the n8n vs Make comparison lays out how the two tools differ, and Make training walks you through the editor from the start.
How do you connect telli to Make?
- 01
Add a telli module
Inside a scenario, click the + and type telli in the search box. Pick any module, Add a Contact for instance, then click Create a connection. The connection is your telli account linked to Make once; every telli module reuses it afterwards.
- 02
Give it a name
Make offers a name field for the connection. You can skip it, yet a clear label, such as the team that owns the telli account, saves confusion when several people build scenarios in the same Make account.
- 03
Authorize, then save
Make either opens a telli page where you approve access, or asks you to paste a key that telli gives you. The documentation does not say which of the two telli uses, so follow the window that appears, then click Save.
Your first telli scenario in Make
GoalWhen a new lead arrives in another app, Make adds it to telli and schedules a call.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to place the first module. telli has no trigger, so start with the app where your leads land, such as a form or a CRM.
- 02
Add Add a Contact
Click the + on the right of that first module, search for telli and choose Add a Contact. Create the connection if this is your first telli module, then map the lead data coming from the previous module.
- 03
Chain Schedule a Call
Use the + again and pick Schedule a Call. Map what Add a Contact returned, so the call is attached to the person you just created and not to an empty record.
- 04
Test with Run once
Click Run once and send one test lead through the first app. Open each module to read the bundle it received: a bundle is one item moving from module to module, here one lead.
- 05
Schedule and switch it on
Set the schedule on the first module; a new scenario runs every 15 minutes by default. Then switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.
What can each telli module do?
telli gives you 15 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Add a Contact
ActionIn the docs onlyGet a new person into telli straight from another app. The module creates one contact for each bundle it receives, so leads no longer have to be copied over by hand from a form or a spreadsheet.
Add multiple Contacts
ActionIn the docs onlyLoad a whole batch of people into telli in a single module run instead of one run per contact. Your scenario stays short when the source already delivers a list rather than single records.
Call Ended Webhook
ActionIn the docs onlySee what happens after a telli call finishes, at least as far as the name suggests. The module list gives it as an action, not a trigger, and the documentation says nothing about what it sends back.
Contact Status Changed Webhook
ActionIn the docs onlyKeep an eye on status changes of your telli contacts, going by the module's label. Like Call Ended Webhook, it is listed as an action, and the documentation says nothing about which statuses exist.
Delete a Contact
ActionIn the docs onlyErase one person from telli so they no longer appear anywhere in your call work. Handy when someone asks to be removed, or when a record was created by mistake during a test run.
Get a Contact
ActionIn the docs onlyRead one telli contact and pass its details to the modules that follow. A later step can then write an email, fill a sheet or update a CRM with what telli already knows.
Get a Contact by External ID
ActionIn the docs onlyFind the telli contact that matches a record living in another tool. The name suggests a lookup by that other tool's own reference, which is how two systems stay paired without names getting mixed up.
Get multiple Contacts
ActionIn the docs onlyPull several telli contacts in one go. The name suggests several bundles come out of it; if so, every module placed after it runs once per contact, and each of those runs is an operation.
Make an API Call
ActionIn the docs onlyReach any part of the telli API that the listed modules leave out, using the same connection and no second login. It is the escape hatch when a feature you need has no module of its own.
Remove from Auto Dialer
ActionIn the docs onlyTake one person off the telli auto dialer, judging by the module's name. Deleting the contact is a separate module, so this one is the gentler choice when you only want the calls to stop.
Remove multiple Contacts from Auto Dialer
ActionIn the docs onlyPull a whole group off the auto dialer in a single run: the batch version of Remove from Auto Dialer. One module does the work that would otherwise take one run per person.
Schedule a Call
ActionIn the docs onlyBook a telli call for one contact at the moment your scenario decides, instead of setting it up in telli by hand. The call planning moves out of someone's to do list.
Schedule multiple Calls
ActionIn the docs onlyPlan calls for a batch of contacts in one module run. It pairs well with Add multiple Contacts when a whole list arrives together and each person on it needs a call.
Update a Contact
ActionIn the docs onlyBring one telli contact up to date with what just changed in another tool. Your callers then work from the same details as the rest of the company, not an old copy.
Update multiple Contacts
ActionIn the docs onlyApply changes to many telli contacts in one run rather than one run per person. Useful when a bulk edit elsewhere has to reach telli without a long chain of single updates.
Need help automating telli with Make?
A person reads every message.
