Integration patterns
1. Push: Post-call webhook
TalkPilot sends call data to your CRM after every completed call. Setup:- Configure the webhook URL on the agent (Dashboard or API)
- Build a webhook receiver in your CRM or automation tool
- Create a webhook trigger
- Parse the incoming call data
- Create or update a CRM record with the call summary, transcript, and customer info
2. Pull: API polling
Periodically fetch new calls and employee data from TalkPilot. Use case: Your CRM needs to display call history or doesn’t support webhooks.3. Bidirectional: Full sync
Combine both patterns for a complete integration:| Direction | What syncs | How |
|---|---|---|
| TalkPilot → CRM | Call records after each call | Post-call webhook |
| TalkPilot → CRM | Call history (catch-up) | API polling |
| CRM → TalkPilot | Employee availability | API: PATCH employee status |
| CRM → TalkPilot | Forwarding rules | API: PUT forwarding slots |
| CRM → TalkPilot | Knowledge base updates | API: POST/PATCH KB documents |
Employee status sync
Keep employee availability in sync between your HR system and TalkPilot:Forwarding slot sync
Keep call routing rules in sync from your CRM or scheduling system:Recommended API key setup
For CRM integrations, create a dedicated API key with specific permissions:| Integration | Permissions needed |
|---|---|
| Read call records | calls:read |
| Sync employees | employees:read, employees:write |
| Sync forwarding slots | forwarding:read, forwarding:write |
| Update KB content | kb:read, kb:write |
| Full bidirectional | All of the above |
Related resources
- Webhooks Guide — Webhook setup and best practices
- Employees API — Employee CRUD operations
- Forwarding Slots API — Slot management with bulk replace
- Calls API — Read call records