Leads in by webhook or API
Each campaign has its own webhook URL, and API keys let your tools send leads with the consent they were given.
Send leads from Make into a Ringin campaign, where your team or an AI agent calls them within minutes. Bookings, callbacks, messages and every call’s outcome come back to Make as signed webhooks, to start the next step.
An HTTP module in Make posts each lead to a campaign’s webhook URL, or to the API with a key.
A new lead goes ahead of the list, so your team or the AI calls it within minutes, in its own calling hours.
In Settings → Integrations → Webhooks, add your scenario’s custom webhook URL as an endpoint and pick the events it wants.
Update your CRM, send a message or alert your team when a lead is interested or a booking is made.
Each campaign has its own webhook URL, and API keys let your tools send leads with the consent they were given.
Interested leads, bookings, moved and cancelled appointments, messages, callbacks, and each call’s outcome with the AI’s summary.
Every request is signed with your endpoint’s secret, and one your system misses is sent again for about a day.
Agents call from the browser, an AI agent calls on its own, or the AI calls first and hands over to a free agent.
Do-not-call list, calling hours in the lead’s time zone and, for AI calls, the lead’s consent.
Appointments land in Google Calendar or Outlook, and Make hears about each one.
Yes. Send leads into a campaign from Make with the campaign’s webhook URL, and add your scenario’s custom webhook URL as an endpoint in Settings → Integrations to act on bookings, callbacks, messages or call outcomes.
One flat monthly price for your whole team. Add AI agents whenever you are ready.