Yodel.io Make integrationAutomate Yodel.io with Make.
Can Make keep your Yodel.io contacts and texts in sync with the rest of your stack? The Yodel.io Make integration gives you 7 action modules, no trigger. This guide is for sales and support teams: connect the account, build a first scenario, pick the right module.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Yodel.io Make integration let you automate?
The Yodel.io Make integration links your Yodel.io account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick that acts in one app. Yodel.io brings 7 action modules and no trigger, so another app or a schedule starts the flow.
Every new lead lands in Yodel.io with a text. A signup form in another app starts the scenario, Create or Update Contact files the person in Yodel.io, then Send a Text Message greets them. Your reps open Yodel.io and the contact is already there.
Contact tags follow your CRM. When a deal changes stage elsewhere, Tag added or Tag removed can carry that status into Yodel.io, as far as their fields allow. Check what each module asks for before you build on it.
Call steps sit next to your other tools. Outbound call, Inbound call and Call ended are listed as actions, which means they run when an earlier module hands them data, not on their own.
What Make does not give you here: no trigger, no search module and no Make an API Call module, so anything outside these 7 modules needs another route. The Make help pages for this app are AI-generated from the vendor docs and may contain mistakes. Before you choose, read our Make review and the n8n vs Make comparison; a similar phone setup is covered in the 8x8 Make integration.
How do you connect Yodel.io to Make?
- 01
Get your API key in Yodel.io
In Yodel.io, open Apps in the main menu, click the application you created with your developer account, and copy the API key shown in its details. Keep the Secret close too.
- 02
Open the connection window
In your Make scenario, add any Yodel.io module and click Create a connection. A connection is your Yodel.io account linked to Make once, then reused by every Yodel.io module.
- 03
Paste the credentials and save
Give it a clear label in Connection name if you like, for instance the team it belongs to, then paste the credentials copied from Yodel.io or follow the instructions on screen.
Your first scenario: greet each new lead by text
GoalWhen a form in another app receives a new lead, Make files the contact in Yodel.io and sends them a text message.
- 01
Start from the form app
On the Scenarios page, create a new scenario and click the +. Pick the trigger of the tool that collects your leads: Yodel.io has none, so the flow opens elsewhere.
- 02
Add Create or Update Contact
Click the + on the right, search Yodel.io and choose Create or Update Contact. Link your account with Create a connection, then map the lead's details from the first module.
- 03
Chain Send a Text Message
Add Send a Text Message after it and fill its fields with data from the earlier modules, so each text carries the right name and number.
- 04
Test with Run once
Submit a test entry in your form, then click Run once. Open each module's bubble and read the bundle it received, one bundle being one item, here one lead.
- 05
Schedule and switch on
Set the schedule on the first module (every 15 minutes by default) and turn the scenario on. From then on, each new lead gets filed and texted without you.
What can the Yodel.io modules do?
Yodel.io gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Call ended
ActionIn the docs onlyGoing by its name, this module deals with the end of a call in Yodel.io. Make files it as an action, not a trigger, and the docs carry no description: it only runs once an earlier module hands it data.
Create or Update Contact
ActionIn the docs onlyYour Yodel.io contact list stays current without copy and paste: as its name says, one module adds the person or updates the record already there. It is the natural first Yodel.io step in most scenarios.
Inbound call
ActionIn the docs onlyHere you get a Yodel.io action tied to incoming calls. Despite the name, Make lists it as an action, and the documentation gives no description, so open its fields in the editor to see what it really does.
Outbound call
ActionIn the docs onlyWith Outbound call, a scenario reaches the outgoing side of Yodel.io calling, as one step after the modules that gather your data. No official description exists, so read its fields before you promise anything to your team.
Send a Text Message
ActionIn the docs onlyA customer gets a text sent through Yodel.io the moment your scenario reaches this step. It turns data from any earlier module, a name, an order, a booking, into a message people actually read.
Tag added
ActionIn the docs onlyTag added lets a scenario work with a tag on a Yodel.io contact, which keeps segments aligned with what happens in your other tools. It is an action in Make, not a watcher, and the docs leave it undescribed.
Tag removed
ActionIn the docs onlyCleaning a label off a contact once it no longer applies is the job this module points to. Like its sibling Tag added, it sits in Make as an action with no official description, so the editor shows you what it really expects.
Need help automating Yodel.io with Make?
A person reads every message.
