May 27, 2026 · 11 min readDocumentation Index
Fetch the complete documentation index at: https://docs.unpod.dev/llms.txt
Use this file to discover all available pages before exploring further.
Every Unpod call produces rich structured data: full transcripts, AI-generated summaries, sentiment analysis, call recordings, and extracted lead intelligence. This guide shows you how to pull that data into your own system — whether that’s a CRM, database, Slack, or a custom pipeline.
What Data Is Available After a Call
When an Unpod call completes, the task output contains:Integration Architecture
Unpod uses a poll + process model. You poll the API to detect completed calls, then process and forward the data.Step 1: Set Up Your Webhook Receiver
Build an HTTP endpoint that receives processed call data. Here’s a minimal receiver in Node.js and Python:Step 2: Build the Polling Service
This service runs continuously, detects newly completed calls, and forwards data to your webhook receiver.Step 3: Integrate with Your Business Systems
Push to HubSpot CRM
After a call, update the contact record with the outcome and schedule follow-up:Send Slack Notification
Alert your sales team when a high-interest call completes:Write to PostgreSQL
Persist call data for analytics and reporting:Step 4: Handle Transcripts
The transcript array gives you the full conversation:Production Checklist
Before going live with your integration:- Idempotency — Use
task_idas a deduplication key. Store processed IDs in Redis or DB to prevent double-processing - Error handling — Retry failed webhook deliveries with exponential backoff
- Persist cursor — Store the last processed timestamp or task ID so restarts don’t reprocess all history
- Secrets — Store
UNPOD_API_TOKENin environment variables, not in code - Rate limits — Unpod API has rate limits; add delays between polling requests if processing large backlogs
- Logging — Log every task ID processed for audit trail
- Alerting — Alert if the polling service stops delivering (gap in processed timestamps)
Quick Reference: Key Data Fields
| Field | Path | Use Case |
|---|---|---|
| Contact name | input.name | CRM lookup |
| Phone number | input.contact_number | CRM lookup |
| Call outcome | output.post_call_data.profile_summary.outcome | Lead status |
| Interest level | output.post_call_data.profile_summary.interest_level | Prioritization |
| Next action | output.post_call_data.profile_summary.next_action | Task creation |
| Call summary | output.post_call_data.summary.summary | CRM note |
| Callback time | output.post_call_data.summary.callback_datetime | Schedule follow-up |
| Recording URL | output.recording_url | Audit / QA |
| Transcript | output.transcript[] | Analysis / training |
| Duration | output.duration | Billing / analytics |
What’s Next
Create Task API
Trigger outbound calls programmatically.
Get Tasks API
Fetch task results and call data.
Call Logs API
Query historical call logs.
Analytics API
Aggregate usage and performance metrics.