Recipes
Build against Callfora with a scoped credential, generated contract, and supported events. These recipes are for private apps your organization operates.
Integration Hub
Each recipe assumes a scoped credential, an acting user where ownership requires it, and live takeover in the desktop or mobile workspace.
Map the signed-in CRM user to an authorized workspace user
Send an idempotent click-to-dial request
Let the user continue in desktop or mobile
Operational boundary: The user needs a provisioned extension; sandbox execution never reaches a public calling provider.
Find an assigned conversation
Send an idempotent message
Attach the supported sent or failed event to the case
Operational boundary: Conversation assignment and messaging entitlements are enforced by the server.
Read a stable page of contacts
Store platform identifiers in the source system
Create changes with acting-user context
Operational boundary: Use cursors and retry reads; use idempotency keys for creates.
Read call records by cursor
Persist the request ID with the batch
Resume from the last confirmed cursor
Operational boundary: Call records are exported after they exist; this is not a promise of every call-state event.
Map an authorized user
Submit an idempotent presence update
Let the workspace reflect the new availability
Operational boundary: Presence updates do not provision a user or bypass role permissions.
Create an event with acting-user context
Store the returned event ID
Open the workspace for the human follow-up
Operational boundary: Calendar access follows the selected user's ownership and permissions.
Integration planning
Let’s find the right way to connect your business.
