Leadialer + Podio Integration
Podio connects through Leadialer's signed webhooks and REST API — directly using Podio flows and its API, or through Zapier/Make if you'd rather not write any glue. Call results and bookings become Podio items; new Podio leads can be pushed into Leadialer for dialing.
What the Podio integration does
Podio-based investor setups are usually custom — a lead app, a follow-up app, maybe GlobiFlow automations holding it together. Leadialer plugs into that with plain, signed webhooks: every completed call, booking, warm lead, and opt-out POSTs a JSON payload you can catch with Zapier, Make, or your own endpoint, then map onto your Podio apps exactly the way your workspace is structured.
Sending leads the other way is one HTTP call: POST them to Leadialer's /api/v1/leads with an API key — from a Podio flow, GlobiFlow, or a Zap — and the AI dialer picks them up for the next session. Payloads are HMAC-signed and retried three times, so your glue can restart without dropping events.
What syncs
- Events out via signed webhooks
- Leads in via the REST API
Setup
- 1Set up a catch endpoint (Zapier/Make hook or your own) and add it under Outgoing Webhooks in Leadialer.
- 2Map the event payload to your Podio app's fields.
- 3Leads in: POST new Podio leads to Leadialer's /api/v1/leads endpoint with an API key.
Field mappings
- Events out — { event, timestamp, data } JSON with lead name and event specifics; you decide which Podio app fields each value fills
- Leads in — POST /api/v1/leads accepts phone (required), firstName, lastName, phone2, phone3, email, propertyAddress, propertyCity, propertyState, propertyZip, notes, and an optional campaignId. Duplicates and Do Not Call numbers are rejected automatically.
Events Leadialer sends
call.completedFires when a call finishes — includes the outcome, the lead's score, and the AI-written call summary.
appointment.bookedFires when Alex books or reschedules an appointment — includes the date and time in your timezone and how it was booked (call or text).
lead.warmFires when a lead's score crosses the warm threshold — includes the score and whether it came from a call or a text thread.
lead.opted_outFires when a lead texts STOP — so you can suppress them in your other tools too.
Frequently asked questions
Do I have to use Zapier or Make?
No. If you're comfortable with Podio's API or GlobiFlow's outbound HTTP actions, you can catch Leadialer's webhooks and post leads directly — the middleware is purely optional convenience.
How do I secure my endpoint?
Verify the X-Leadialer-Signature header: it's a hex HMAC-SHA256 of the raw request body using your endpoint's signing secret. Reject anything that doesn't match.
What happens if my endpoint is down?
Leadialer retries each delivery up to three times. Calling and texting continue regardless — webhook delivery never blocks the dialer.