Integrations
Connect Talkturo to scheduling, CRM, messaging, telephony, billing, and AI providers to automate calls and move data between systems.
Connect Talkturo to the rest of your stack
Talkturo integrates with external systems in five distinct ways: workflow integrations in TurboFlow, callable tools inside assistants, outbound event webhooks, provider selection for AI and telephony, and billing providers. Which option to use depends on where the integration should run and what it needs to do.
TurboFlow integrations
Connect OAuth-based apps in the workflow builder for triggers and actions.
Assistant tools
Let assistants schedule, trigger automations, call APIs, and run workflows during conversations.
Event webhooks
Send call lifecycle events to your own systems from each assistant.
Configure workflow integrations in TurboFlow, assistant tools in the assistant Functions tab, and call event delivery in the assistant Webhooks tab. These are separate features and are managed in different parts of Talkturo.
TurboFlow integrations
TurboFlow handles OAuth-based app connections for workflow triggers and actions. Use these integrations when you want Talkturo to react to external events or push data into another system as part of an automated flow.
Supported TurboFlow apps
| Integration | Connection type | Triggers | Actions |
|---|---|---|---|
| Cal.com | OAuth | Booking created, cancelled, rescheduled | Scheduling actions |
| Calendly | OAuth | Invitee created, canceled | Scheduling actions |
| Gmail | OAuth | None | Send email |
| HubSpot | OAuth | None | Create contacts, create deals |
| Slack | OAuth | Messages, app mentions, reactions, file shares | Send messages |
| Meta for Facebook and Instagram | OAuth | New lead from lead ads | None |
When to use TurboFlow
Use TurboFlow when the integration belongs in an automation flow rather than inside a live conversation. That is the right fit for event-driven work such as routing new leads, creating CRM records after a trigger fires, or sending follow-up notifications to a team channel.
Integration details
Cal.com
Cal.com supports booking-based triggers and scheduling actions inside TurboFlow. Use it when workflows need to react to appointment lifecycle changes or create scheduling steps as part of a broader automation.
Calendly
Calendly supports invitee event triggers and scheduling actions. It covers the common scheduling flow where a booking in Calendly should start a workflow or a workflow should create or manage scheduling activity.
Gmail
Gmail is available for send-email actions through OAuth. Use it when a workflow needs to send confirmation emails, internal alerts, or follow-up messages.
HubSpot
HubSpot supports OAuth-based actions for creating contacts and deals. This is the right option when workflow data should become CRM records without custom API work.
Slack
Slack supports both triggers and actions. A workflow can start from Slack activity such as messages, app mentions, reactions, or file shares, and it can also send messages back into Slack.
Meta for Facebook and Instagram
Meta integrations support lead ad triggers for new leads from Facebook and Instagram. Use them to move ad leads directly into workflows for qualification, routing, or downstream CRM updates.
Assistant tool functions
Assistant tool functions run in the context of a conversation. Use them when the assistant needs to take an action, fetch data, or hand work to another system while talking to a caller.
Choose assistant tools for real-time conversation tasks. Choose TurboFlow integrations for background automation that starts from a trigger or continues after the call.
Available assistant tools
| Tool | What it does | Typical use |
|---|---|---|
| Cal.com | Schedule, retrieve bookings, cancel bookings, check availability | Book or manage appointments during a call |
| Zapier | Trigger Zapier automations | Hand off call outcomes to thousands of external apps |
| Custom Webhooks | Call external API endpoints during a conversation | Query internal systems or trigger proprietary workflows |
| TurboFlow Workflows | Attach a published workflow as an LLM-callable tool | Reuse a structured flow from inside an assistant |
Configure assistant tools
Open the assistant you want to update, then use the Functions tab to add and manage tools available to that assistant.
Open the assistant
Go to the assistant you want to configure and open its Functions tab.
Add the tool type
Choose the integration or tool you want the assistant to call during conversations.
Configure access and behavior
Connect the external service if the tool requires it, then define how the assistant should use the function.
Test the conversation path
Run a test call or assistant session and confirm the tool fires at the right moment with the expected result.
Cal.com assistant functions
Cal.com functions are available directly inside assistants. They support four core operations:
- Schedule bookings during a live conversation
- Get bookings to review existing appointments
- Cancel bookings when a caller needs to change plans
- Check availability before offering times to a caller
This integration is useful when the assistant acts like a scheduling coordinator and needs immediate booking context.
Zapier assistant function
Zapier lets an assistant trigger downstream automations from a call. Use it when the call outcome should kick off work in another system without building a direct custom integration for each destination.
Custom webhook functions
Custom webhooks let an assistant call external API endpoints during a conversation. Each assistant can have multiple custom webhook tools, which makes this option useful for internal systems, proprietary services, or APIs that are not covered by a built-in integration.
Custom webhook functions run during live conversations. Make sure the external endpoint responds reliably and quickly enough for the caller experience you want to deliver.
TurboFlow workflows as tools
A published TurboFlow workflow can be attached as a callable tool for an assistant. This is useful when you want the assistant to delegate a structured process to a reusable workflow instead of encoding all logic directly in the prompt or tool instructions.
Assistant event webhooks
Assistant event webhooks send call events from Talkturo to your external systems. Configure them per assistant in the Webhooks tab when you need downstream systems to react to call activity.
Supported webhook events
| Event | When it fires | Common destination |
|---|---|---|
call.started | A call begins | Logging, live dashboards, notifications |
call.ended | A call completes | CRM updates, analytics pipelines, post-call automations |
call.transcribed | A transcript becomes available | QA review, summarization, storage, search indexing |
Webhook security
Talkturo signs webhook requests with an HMAC signature so your server can verify that the event came from Talkturo.
HMAC signature included with assistant event webhooks. Verify the signature on receipt before processing the payload.
When to use webhooks instead of tools
Use a webhook when Talkturo should notify your system after an event happens. Use a tool function when the assistant needs to call your system during the conversation and use the result immediately.
AI provider integrations
Each assistant can be configured with separate providers for language, speech-to-text, and text-to-speech. This lets you tune quality, latency, voice characteristics, and model behavior for the use case you are building.
LLM providers
| Provider |
|---|
| OpenAI |
| Google Gemini |
| DeepSeek |
| Qwen |
| Kimi |
| Anthropic |
| Cerebras |
| Talkturo Fast |
Speech-to-text providers
| Provider |
|---|
| Deepgram |
| AssemblyAI |
| Cartesia |
| ElevenLabs |
| Inworld |
Text-to-speech providers
| Provider |
|---|
| Cartesia |
| ElevenLabs |
| Inworld |
| OpenAI |
| DashScope |
| Kugel |
AI providers are selected per assistant. The best combination depends on your latency target, language coverage, voice requirements, and model behavior.
Telephony integrations
Talkturo supports telephony providers for phone numbers and SIP connectivity.
Supported telephony providers
| Provider | Role |
|---|---|
| Telnyx | Primary provider for phone number purchasing and SIP trunking |
| Twilio | Secondary provider for phone number purchasing and SIP trunking |
Use telephony integrations when you need to provision numbers, connect SIP infrastructure, or route calls through your preferred provider setup.
Billing integrations
Talkturo uses external billing providers for subscription and payment handling.
Supported billing providers
| Provider | Role |
|---|---|
| Stripe | Primary payment provider |
| Lemon Squeezy | Legacy alternative |
If you are managing account payments or reviewing billing behavior, expect Stripe to be the default provider in current setups.
Choose the right integration path
The fastest way to pick the right feature is to start with where the action happens.
- Use TurboFlow integrations when an OAuth-connected app should trigger or receive workflow actions.
- Use assistant tools when the assistant needs to do something during a call.
- Use assistant webhooks when your system should receive call events after they happen.
- Use provider integrations when you are configuring model, voice, transcription, telephony, or billing infrastructure.