# Talkdesk Canonical: https://warmtransfer.net/knowledge/talkdesk-platform Last verified: 2026-09-25 Talkdesk provides customer experience software through its CX Cloud and Customer Experience Automation (CXA) platform, covering inbound interactions across voice and digital channels[^9][^49][^21]. Its architecture includes Studio interaction routing, developer APIs across regional hosts, integration hooks, and carrier connectivity options[^40][^47][^9]. ## Telephony and Carrier Connectivity Talkdesk markets Bring Your Own Carrier (BYOC) as letting a customer retain its existing carrier relationship, phone numbers, and rates while connecting that carrier to Talkdesk CX Cloud[^9]. For carrier interconnection, Talkdesk's BYOC documentation states that it uses points of presence across the US, EU, APAC, and LATAM[^10]. Talkdesk positions Bring Your Own PBX (BYO PBX) as a mechanism to connect an existing on-premises PBX to Talkdesk CX Cloud, serving as a staged migration path to the cloud[^8]. For call control at the agent interface, the Talkdesk Telephony SDK API operates under the Advanced Dialer path to provide CTI functions, including dial, answer, agent ready and break states, as well as blind, consultation, and conference transfers[^51]. ## Architecture and Regional APIs Talkdesk developer documentation lists 5 API regions: US, Europe, Canada, UK, and FedRAMP[^40]. | Region | API Base URL | | --- | --- | | US | https://api.talkdeskapp.com/[^39] | | Europe | https://api.talkdeskapp.eu/[^35] | | Canada | https://api.talkdeskappca.com/[^34] | | UK | https://api.talkdeskapp.co.uk/[^38] | | FedRAMP | https://api.talkdeskapp-pubsec.com[^36] | Talkdesk instructs developers of multi-region apps to subscribe to provisioning events and consume the region-specific API gateway URL delivered in the `_links.root` field rather than hard-coding a region host; hard-coding is acceptable only for internal API use[^41]. WarmTransfer's reading of the sources is that an integration hard-coded to the US API host will probably fail against a Talkdesk account in another region, because each region has a separate API host[^37]. API requests authenticate through OAuth 2.0, where the authorize path is `/oauth/authorize` and the token path is `/oauth/token`[^2]. The Client Credentials grant provisions API access on behalf of an entire Talkdesk account, whereas the Authorization Code grant issues access on behalf of a single user[^3]. API permissions follow a `resource:permission` format (such as `account:read` or `campaigns:write`) that restricts both the target endpoint and whether the client has read or write authorization[^44]. When a scope is added to an OAuth client through Partner Project, propagation can take a few minutes, during which token requests for that scope return a 401 error[^43]. The Events API delivers event payloads as HTTPS webhooks using at-least-once delivery semantics, which can result in duplicate event receipts[^24]. Talkdesk signs these payloads using a private key and includes the signature alongside a key identifier in the `X-Hub-Ecdsa-Signature` header; receiving systems verify this signature using SHA512 and the corresponding public key[^25]. The Events API is required for AppConnect marketplace integrations and carries app lifecycle events, such as `app.installed`, `app.uninstalled`, `app.trial_started`, and `app.credentials_rotated`[^23]. ## Talkdesk Studio Talkdesk Studio supports 4 interaction flow types: API Request, Incoming Call, Incoming Message, and Outgoing Call[^47]. An Incoming Call flow executes from the time an inbound call arrives until the call terminates or post-call actions, such as surveys, finish[^48]. An Outgoing Call flow handles manual, agent-initiated outbound calls from when the dialed contact answers until the call connects with the agent[^50]. Inbound digital interactions across SMS, chat, and email are managed within a single Incoming Message flow type[^49]. Studio groups flow components across 7 functional categories: Contact/Input, Conditional, Data, Agent, Automated, Flow, and End actions[^45]. Flows configured with the API request trigger type can be initiated programmatically using the Flows API via `POST /flows/{flow-id}/interactions`, requiring the `flows-interactions:start` OAuth scope[^42][^32]. The Flows API starts an interaction on the published version of the targeted flow[^31]. WarmTransfer's reading of the sources is that edits to an API-triggered Studio flow probably do not affect Flows API executions until the flow is published again[^30]. When working with Studio API flows: - Input arguments currently support only string types[^1]. - A call path may contain at most 1 Make outbound call component[^13]. - A Request Direct Callback component cannot be placed immediately after another Request Direct Callback component[^13]. - In a flow using Request Direct Callback, the agent is rung first, and the customer is dialed only after the agent accepts the interaction and hears the callback-request announcement[^11]. - The Request Direct Callback component accepts a priority setting from 1 to 10, a search timeframe between 1 and 48 hours, and targets ring groups, individual agents, or attributes[^22]. - When Auto-answer is used alongside callbacks in Studio, its timeout accepts a value up to 40 seconds[^4]. Independent of Studio API request flows, Talkdesk offers a dedicated Callback API to trigger callbacks programmatically; the capability to pass key-value context to the agent with a callback request via this API is in Closed Beta[^12]. For continuity, the Fallback Experience API provides Studio Continuity Settings that allow administrators to redirect inbound calls per phone number to external destinations, route all calls to a single external backup number, or play an audio announcement during severe capacity degradation[^28]. Once activated, fallback configurations apply only to newly arriving inbound calls[^29]. Step-level Studio execution telemetry can be extracted through the Explore API using the `studio_flow_execution` report type, which limits each request to at most 1 month of execution data[^46]. ## Integrations and Media Talkdesk Connections enables no-code integrations to external HTTP services, which Studio flows invoke through the Execute Action component[^17]. Connections enforces specific operating constraints: - Input and output payloads must use `application/json` or `application/x-www-form-urlencoded`[^16]. - Action timeouts can be configured between 5 and 30 seconds, measured from request dispatch until response arrival[^19]. - Supported authentication mechanisms include no authentication, Basic authentication, `X-API-Key`, and OAuth2 flows covering Client Credentials, Resource Owner, Authorization Code, and Private Key JWT variants[^15]. - Studio flows must use the Run Function component to process array-type fields returned by a Connections action[^14]. - Connections does not support Contact Sync or Agent Sync; those capabilities require a Custom Integration[^18]. Automations can also link to Microsoft Power Automate through the Webhook Trigger API, which has been generally available since March 2023[^53]. When an administrator deletes a Webhook Trigger, Talkdesk processes the removal through a periodic 5-minute synchronization cycle rather than immediately[^52]. For voice media storage, files retrieved through the Recordings API are mp3 files[^33]. Calls occurring after 18 April 2017 are captured in dual-channel format by default, though dual-channel recording can be disabled[^33]. ## Customer Experience Automation (CXA) and AI Talkdesk's CXA platform documentation outlines several core components: Autopilot, Copilot, Data Cloud, Interaction and Quality Analytics, Multi-agent Orchestration, CXA Operations Center, and Automation Flows[^21]. Autopilot serves as Talkdesk's AI virtual agent across voice and digital channels, and it automatically transfers interactions to human agents upon encountering complex customer requests[^5]. Autopilot marketing material states support for 59+ languages[^6]. Autopilot integrates with Talkdesk Navigator for interaction routing, Knowledge Management for contextual information retrieval, and the CXA Operations Center for administrative oversight and monitoring[^7]. ## Applicability Applies to: Talkdesk CX Cloud BYOC, Talkdesk CX Cloud BYO PBX, Talkdesk APIs, Talkdesk AppConnect Events API, Talkdesk Studio, Talkdesk Explore API, Talkdesk Studio Continuity Settings, Talkdesk Callback API, Talkdesk Connections, Talkdesk Webhook Trigger API, Talkdesk Recordings API, Talkdesk Advanced Dialer, Talkdesk CXA, and Talkdesk Autopilot. Deployments: hybrid and multi-tenant. Sources checked 2026-09-25. The FedRAMP edition applies specifically to the FedRAMP API region URL[^36]. Default dual-channel recording applies to calls recorded after 18 April 2017[^33]. General availability for the Webhook Trigger API applies from March 2023 onward[^53]. ## What remains uncertain BYOC supported transports and codecs (including SIP, TLS, IPSec, Direct Connect, and G711u or G711a) are not covered by the sources below. Talkdesk AI data handling, model training policies, and data residency rules for Autopilot and Copilot are not covered by the sources below. The general availability date of Copilot Agentic is not covered by the sources below. Native Talkdesk phone numbers, porting processes, STIR/SHAKEN attestation levels, and 10DLC registration requirements are not covered by the sources below. Differences between Talkdesk Express and Talkdesk CX Cloud editions, including BYOC and Studio availability across tiers, are not covered by the sources below. The Studio draft, publish, and version rollback lifecycle is not covered by the sources below. The text and specifications of the Talkdesk BYOC datasheet PDF are not covered by the sources below. Talkdesk API rate limits and response handling behaviors are not covered by the sources below. ## Sources [^1]: Studio API request flows currently support only string input arguments. Source: [Using Request Direct Callbacks and Auto-answer in Studio API Flows](https://studio.talkdesk.com/docs/using-callbacks-and-auto-answer-in-api-triggered-flows), Using Request Direct Callbacks and Auto-answer, limitations section. Checked 2026-09-25. [^2]: The Talkdesk OAuth 2.0 authorize path is /oauth/authorize and the token path is /oauth/token. Source: [Authentication](https://docs.talkdesk.com/docs/authentication.md), Authentication, OAuth 2.0 implementation details. Checked 2026-09-25. [^3]: Talkdesk APIs use OAuth 2.0: the Client Credentials grant gives API access on behalf of a whole Talkdesk account, and the Authorization Code grant gives access on behalf of a single user. Source: [Authentication](https://docs.talkdesk.com/docs/authentication.md), Authentication, grant type descriptions. Checked 2026-09-25. [^4]: The Studio Auto-answer component used with callbacks accepts a timeout of up to 40 seconds. Source: [Using Request Direct Callbacks and Auto-answer in Studio API Flows](https://studio.talkdesk.com/docs/using-callbacks-and-auto-answer-in-api-triggered-flows), Using Request Direct Callbacks and Auto-answer, configuration step for Auto-answer. Checked 2026-09-25. [^5]: Talkdesk Autopilot is Talkdesk's AI virtual agent for voice and digital channels, and it redirects customers to a human agent when it detects complex cases. Source: [AI Virtual Agent | Talkdesk Autopilot](https://www.talkdesk.com/cloud-contact-center/self-service-experience/autopilot/), Autopilot product page, hero and handoff sections. Checked 2026-09-25. [^6]: Talkdesk's Autopilot marketing page advertises support for 59+ languages. Source: [AI Virtual Agent | Talkdesk Autopilot](https://www.talkdesk.com/cloud-contact-center/self-service-experience/autopilot/), Autopilot product page, languages statement. Checked 2026-09-25. [^7]: Talkdesk's Autopilot page lists integrations with Talkdesk Navigator for routing, Knowledge Management for contextual answers, and CXA Operations Center for monitoring and oversight. Source: [AI Virtual Agent | Talkdesk Autopilot](https://www.talkdesk.com/cloud-contact-center/self-service-experience/autopilot/), Autopilot product page, related products / integrations section. Checked 2026-09-25. [^8]: Talkdesk positions BYO PBX as a way to connect an existing on-premises PBX to Talkdesk CX Cloud as a staged migration path to the cloud. Source: [Talkdesk BYOC - Bring your own carrier](https://www.talkdesk.com/contact-center-platform/flexible-deployment/byo-pbx-carrier/), BYOC page, key benefit statement on migration path. Checked 2026-09-25. [^9]: Talkdesk markets BYOC as letting a customer keep its existing carrier relationship, phone numbers and rates while connecting that carrier to Talkdesk CX Cloud. Source: [Talkdesk BYOC - Bring your own carrier](https://www.talkdesk.com/contact-center-platform/flexible-deployment/byo-pbx-carrier/), BYOC page, BYOC/BYO PBX feature section. Checked 2026-09-25. [^10]: Talkdesk's BYOC page states that its carrier interconnection uses points of presence across the US, EU, APAC and LATAM. Source: [Talkdesk BYOC - Bring your own carrier](https://www.talkdesk.com/contact-center-platform/flexible-deployment/byo-pbx-carrier/), BYOC page, connectivity section (multi-tenant interconnection with telco providers). Checked 2026-09-25. [^11]: In a Studio API flow that uses Request Direct Callback, Talkdesk rings the agent first; the customer is dialed only after the agent accepts and hears a callback-request announcement. Source: [Using Request Direct Callbacks and Auto-answer in Studio API Flows](https://studio.talkdesk.com/docs/using-callbacks-and-auto-answer-in-api-triggered-flows), Using Request Direct Callbacks and Auto-answer in Studio API Flows, how it works section. Checked 2026-09-25. [^12]: The Talkdesk Callback API triggers callbacks by API request, and its option to send key-value context to the agent with a callback request is in Closed Beta. Source: [Callback API](https://docs.talkdesk.com/docs/callback-api.md), Callback API, overview and context data section. Checked 2026-09-25. [^13]: A Studio call path can hold at most one Make outbound call component, and a Request Direct Callback component cannot directly follow another one. Source: [Using Request Direct Callbacks and Auto-answer in Studio API Flows](https://studio.talkdesk.com/docs/using-callbacks-and-auto-answer-in-api-triggered-flows), Using Request Direct Callbacks and Auto-answer, limitations section. Checked 2026-09-25. [^14]: To use array-type fields returned by a Connections action, a Studio flow needs the Run Function component. Source: [What Connections Supports](https://docs.talkdesk.com/docs/what-connections-supports.md), What Connections Supports, Studio variable types section. Checked 2026-09-25. [^15]: Talkdesk Connections supports no authentication, Basic authentication, X-API-Key and several OAuth2 flows, including Client Credentials, Resource Owner, Authorization Code and Private Key JWT variants. Source: [What Connections Supports](https://docs.talkdesk.com/docs/what-connections-supports.md), What Connections Supports, authentication types section. Checked 2026-09-25. [^16]: Talkdesk Connections action input and output must be application/json or application/x-www-form-urlencoded. Source: [What Connections Supports](https://docs.talkdesk.com/docs/what-connections-supports.md), What Connections Supports, content format section. Checked 2026-09-25. [^17]: Talkdesk Connections lets admins set up no-code connections to third-party APIs, and Studio flows run the resulting custom actions through the Execute Action component. Source: [Connections](https://docs.talkdesk.com/docs/building-a-custom-integration-with-connections.md), Connections, usage in Studio section. Checked 2026-09-25. [^18]: Talkdesk Connections does not support Contact or Agent Sync; those require a Custom Integration. Source: [Connections](https://docs.talkdesk.com/docs/building-a-custom-integration-with-connections.md), Connections, limitation note. Checked 2026-09-25. [^19]: A Talkdesk Connections action timeout can be set from 5 seconds up to 30 seconds, measured from when the action is triggered until a response arrives. Source: [What Connections Supports](https://docs.talkdesk.com/docs/what-connections-supports.md), What Connections Supports, timeout section. Checked 2026-09-25. [^20]: On 21 October 2025 Talkdesk announced an agentic AI upgrade to Talkdesk Copilot, built on its Customer Experience Automation (CXA) platform, that synthesizes information across CRM, knowledge bases and enterprise systems for agents. Source: [Talkdesk upgrades Copilot with agentic AI to help human agents tackle the toughest customer challenges](https://www.talkdesk.com/news-and-press/press-releases/agentic-copilot/), press release, opening paragraphs. Checked 2026-09-25. [^21]: Talkdesk's CXA platform page lists Autopilot, Copilot, Data Cloud, Interaction and Quality Analytics, Multi-agent Orchestration, CXA Operations Center and Automation Flows as its components. Source: [Customer Experience Automation (CXA) Platform & Software | Talkdesk](https://www.talkdesk.com/customer-experience-automation/), CXA platform page, product navigation and component sections. Checked 2026-09-25. [^22]: Request Direct Callback takes a priority from 1 to 10, a search timeframe from 1 to 48 hours, and assignment by ring groups, agents or attributes. Source: [Using Request Direct Callbacks and Auto-answer in Studio API Flows](https://studio.talkdesk.com/docs/using-callbacks-and-auto-answer-in-api-triggered-flows), Using Request Direct Callbacks and Auto-answer, Request Direct Callback configuration step. Checked 2026-09-25. [^23]: The Events API is required for AppConnect marketplace integration and carries app lifecycle events such as app.installed, app.uninstalled, app.trial_started and app.credentials_rotated. Source: [Events API](https://docs.talkdesk.com/docs/events-api.md), Events API, Events section. Checked 2026-09-25. [^24]: The Talkdesk Events API delivers events as HTTPS webhooks with at-least-once semantics, so receivers can get duplicate events. Source: [Events API](https://docs.talkdesk.com/docs/events-api.md), Events API, Event Delivery section. Checked 2026-09-25. [^25]: Talkdesk signs Events API payloads with a private key and sends the signature in the X-Hub-Ecdsa-Signature header with a key identifier; receivers verify it using the public key and SHA512. Source: [Events API](https://docs.talkdesk.com/docs/events-api.md), Events API, Event Signatures and Signature Method sections. Checked 2026-09-25. [^26]: A Talkdesk Express community article states that BYOC on Talkdesk Express requires a multi-tenant SIP trunk (field report). Source: [Understanding BYOC: How to Bring Your Own Carrier to Talkdesk Express](https://express.talkdesk.com/articles/post/understanding-byoc-how-to-bring-your-own-carrier-to-talkdesk-express-zE63n90rPTlonbP), article body, section distinguishing multi-tenant vs single-tenant. Checked 2026-09-25. [^27]: The same Talkdesk Express community article describes BYOC as a setup that the customer requests from Talkdesk, which then assesses whether the carrier meets its requirements, rather than self-service configuration (field report). Source: [Understanding BYOC: How to Bring Your Own Carrier to Talkdesk Express](https://express.talkdesk.com/articles/post/understanding-byoc-how-to-bring-your-own-carrier-to-talkdesk-express-zE63n90rPTlonbP), article body, setup process section. Checked 2026-09-25. [^28]: The Talkdesk Fallback Experience API is a Studio Continuity Settings solution; it lets admins forward inbound calls per phone number to external numbers, send all calls to one external backup number, or play an audio message when capacity is seriously compromised. Source: [Fallback Experience API](https://docs.talkdesk.com/docs/fallback-experience-api.md), Fallback Experience API, overview section. Checked 2026-09-25. [^29]: Once enabled, the Talkdesk fallback experience configuration applies only to new inbound calls. Source: [Fallback Experience API](https://docs.talkdesk.com/docs/fallback-experience-api.md), Fallback Experience API, limitation note. Checked 2026-09-25. [^30]: Edits to an API-triggered Studio flow probably do not affect Flows API executions until the flow is published again (inferred). Source: [Flows API](https://docs.talkdesk.com/docs/flows-api.md), Flows API, overview paragraph (published version). Checked 2026-09-25. [^31]: The Talkdesk Flows API starts an interaction that runs the published version of a given Studio flow. Source: [Flows API](https://docs.talkdesk.com/docs/flows-api.md), Flows API, overview paragraph. Checked 2026-09-25. [^32]: Only Studio flows with the API request trigger type can be started through the Flows API, using POST /flows/{flow-id}/interactions. Source: [Flows API](https://docs.talkdesk.com/docs/flows-api.md), Flows API, usage section. Checked 2026-09-25. [^33]: Recordings from the Talkdesk Recordings API are mp3 files, and calls after 18 April 2017 are recorded in dual-channel format by default, though that can be disabled. Source: [Recordings API](https://docs.talkdesk.com/docs/recordingsapi.md), Recordings API, format section. Checked 2026-09-25. [^34]: The Talkdesk API base URL for the Canada region is https://api.talkdeskappca.com/. Source: [App and Talkdesk Regions](https://docs.talkdesk.com/docs/how-to-guarantee-your-app-works-in-all-regions.md), App and Talkdesk Regions, region table, Canada row. Checked 2026-09-25. [^35]: The Talkdesk API base URL for the Europe region is https://api.talkdeskapp.eu/. Source: [App and Talkdesk Regions](https://docs.talkdesk.com/docs/how-to-guarantee-your-app-works-in-all-regions.md), App and Talkdesk Regions, region table, Europe row. Checked 2026-09-25. [^36]: The Talkdesk API base URL for the FedRAMP region is https://api.talkdeskapp-pubsec.com. Source: [App and Talkdesk Regions](https://docs.talkdesk.com/docs/how-to-guarantee-your-app-works-in-all-regions.md), App and Talkdesk Regions, region table, FedRAMP row. Checked 2026-09-25. [^37]: An integration hard-coded to the US API host will probably fail against a Talkdesk account in another region, because each region has a separate API host (inferred). Source: [App and Talkdesk Regions](https://docs.talkdesk.com/docs/how-to-guarantee-your-app-works-in-all-regions.md), App and Talkdesk Regions, region table and rules for apps. Checked 2026-09-25. [^38]: The Talkdesk API base URL for the UK region is https://api.talkdeskapp.co.uk/. Source: [App and Talkdesk Regions](https://docs.talkdesk.com/docs/how-to-guarantee-your-app-works-in-all-regions.md), App and Talkdesk Regions, region table, UK row. Checked 2026-09-25. [^39]: The Talkdesk API base URL for the US region is https://api.talkdeskapp.com/. Source: [App and Talkdesk Regions](https://docs.talkdesk.com/docs/how-to-guarantee-your-app-works-in-all-regions.md), App and Talkdesk Regions, region table, US row. Checked 2026-09-25. [^40]: Talkdesk developer documentation lists five API regions: US, Europe, Canada, UK and FedRAMP. Source: [App and Talkdesk Regions](https://docs.talkdesk.com/docs/how-to-guarantee-your-app-works-in-all-regions.md), App and Talkdesk Regions, region table. Checked 2026-09-25. [^41]: Talkdesk says multi-region apps should subscribe to provisioning events and use the region-specific API gateway URL in the _links.root field rather than hard-coding a region; hard-coding is acceptable only for internal API use. Source: [App and Talkdesk Regions](https://docs.talkdesk.com/docs/how-to-guarantee-your-app-works-in-all-regions.md), App and Talkdesk Regions, rules for apps section. Checked 2026-09-25. [^42]: Starting a Studio flow interaction through the Flows API requires the flows-interactions:start scope. Source: [Scopes](https://docs.talkdesk.com/docs/scopes.md), Scopes, scope list, Flows entry. Checked 2026-09-25. [^43]: A scope added to an OAuth client through Partner Project can take a few minutes to take effect, and until then a token request for it returns a 401 error. Source: [Scopes](https://docs.talkdesk.com/docs/scopes.md), Scopes, note on adding scopes via Partner Project. Checked 2026-09-25. [^44]: Talkdesk API scopes use a resource:permission format, such as account:read or campaigns:write, and limit both which endpoints a client can call and whether it has read or write access. Source: [Scopes](https://docs.talkdesk.com/docs/scopes.md), Scopes, introductory section. Checked 2026-09-25. [^45]: Talkdesk Studio groups its flow components into seven categories: Contact/Input, Conditional, Data, Agent, Automated, Flow and End actions. Source: [Studio Components Overview](https://studio.talkdesk.com/docs/overview), Studio Components Overview, component category list. Checked 2026-09-25. [^46]: Step-level Studio execution data is available through the Explore API as the studio_flow_execution report type, with at most one month of data per request. Source: [Studio Flow Execution Report](https://docs.talkdesk.com/docs/studio-flow-execution-report.md), Studio Flow Execution Report, overview and data availability notes. Checked 2026-09-25. [^47]: Talkdesk Studio has four flow types: API Request, Incoming Call, Incoming Message and Outgoing Call. Source: [Flow Types](https://studio.talkdesk.com/docs/flow-types), Flow Types, overview list. Checked 2026-09-25. [^48]: A Studio Incoming Call flow covers an interaction from the moment the inbound call arrives until the call ends or its post-call actions, such as surveys, finish. Source: [Flow Types](https://studio.talkdesk.com/docs/flow-types), Flow Types, Incoming Call section. Checked 2026-09-25. [^49]: One Studio Incoming Message flow type defines the customer experience for inbound digital messages across SMS, chat and email. Source: [Flow Types](https://studio.talkdesk.com/docs/flow-types), Flow Types, Incoming Message section. Checked 2026-09-25. [^50]: A Studio Outgoing Call flow manages manual agent-initiated outbound calls from the moment the contact answers until the call with the agent is established. Source: [Flow Types](https://studio.talkdesk.com/docs/flow-types), Flow Types, Outgoing Call section. Checked 2026-09-25. [^51]: The Talkdesk Telephony SDK API, served under the Advanced Dialer path, provides CTI control of calls, including dial, answer, agent ready and break states, and blind, consultation and conference transfers. Source: [Telephony SDK API](https://docs.talkdesk.com/docs/telephony-sdk-api.md), Telephony SDK API, capabilities and endpoints sections. Checked 2026-09-25. [^52]: When a Webhook Trigger is deleted, Talkdesk syncs the deletion on a periodic five-minute timer rather than in real time. Source: [Webhook Trigger API](https://docs.talkdesk.com/docs/webhook-trigger-api.md), Webhook Trigger API, delete webhook trigger section. Checked 2026-09-25. [^53]: The Talkdesk Webhook Trigger API connects Talkdesk to Microsoft Power Automate through Connections-powered automations, and it has been generally available since March 2023. Source: [Webhook Trigger API](https://docs.talkdesk.com/docs/webhook-trigger-api.md), Webhook Trigger API, overview and availability note. Checked 2026-09-25.