Sync telli Call Data to Airtable CRM
When a telli call ends, it updates the Airtable CRM with interest and appointment status, then triggers follow-up emails or calendar tasks.
What it does
You instantly get your Airtable CRM updated with call outcomes and interest levels the moment a telli call ends, so you can immediately trigger follow-up emails or schedule appointments without manual entry. This automation ensures no lead slips through the cracks by automatically creating calendar tasks based on specific results from your n8n workflow.
Step by step
- Configure the telli webhook endpoint in n8n to trigger on call completion events.
- Map specific JSON fields from the telli payload to corresponding Airtable record columns.
- Set up conditional logic nodes in n8n to route different call outcomes to distinct actions.
Where the LLM does the work
- Generate natural language summaries of complex call notes for storage in Airtable text fields.
- Draft personalized follow-up email content based on the extracted interest level and outcome.
- Create concise calendar task descriptions that capture the essence of the sales conversation.
Watch out for
Tools that fit
The agent brief
You are helping me build the following AI agent workflow. ## Goal Sync telli Call Data to Airtable CRM: When a telli call ends, it updates the Airtable CRM with interest and appointment status, then triggers follow-up emails or calendar tasks. ## Specification - What it does: You instantly get your Airtable CRM updated with call outcomes and interest levels the moment a telli call ends, so you can immediately trigger follow-up emails or schedule appointments without manual entry. This automation ensures no lead slips through the cracks by automatically creating calendar tasks based on specific results from your n8n workflow. - Trigger: Triggered by an event (Event · on call ended) - Autonomy: Fully hands-off - Expected setup effort: about an afternoon - Tools/services involved: - telli: Voice agent platform providing call event webhooks - n8n: Workflow automation engine processing webhooks and logic - Airtable: CRM database storing contact records and appointment status ## Known pitfalls, handle each one explicitly in your implementation 1. Sensitive call data might be exposed if webhook URLs are not secured with secret tokens or IP whitelisting. 2. Schema mismatches between telli and Airtable can break the flow, validate field types during initial setup. ## Reference implementation https://n8n.io/workflows/3802 (workflow template) Fetch and inspect this before building. If it matches my stack, adapt it; if not, rebuild the pattern with my tools. ## Process requirements 1. Before building: ask me which of the listed tools I actually use and what my platform is (n8n / Make / code / other). Do not assume. 2. Adapt the pattern to my answers; do not force the reference stack. 3. Address every pitfall above; tell me how you handled each. 4. Provide a test plan I can run before letting this touch real data. 5. Ask before any step that sends messages, modifies data, or spends money. Source: https://usecasesforagents.com/use-case/sync-telli-call-data-to-airtable-crm/ via usecasesforagents.com
Frequently asked questions
Can I use a different Voice & Telephony than telli?
Yes. telli is only the example voice & telephony in this recipe. The same flow works with Aloware, ElevenLabs, GoToWebinar and Plivo. Swap the voice & telephony connection and keep the rest of the setup as written.
Want this running in your business?
Who it's for
Built for founders and execs who need sales handled without hiring for it.
Ops-IT teams triaging their own internal requests get the same pattern, different queue.