# Webex Connect Flow Builder node reference

Canonical: https://warmtransfer.net/knowledge/webex-connect-node-reference

Last verified: 2026-09-24

The Webex Connect Nodes index groups flow nodes under Utilities, Channels, Embedded Voice Nodes, and Integrations, while listing a separate Voice Flow Nodes group marked Deprecated[^32]. Within flows, variables are referenced as $(variableName) for custom variables and $(nodeID.variablename) for node output variables, with variable names being case-sensitive[^55].

## Node categories

The platform categorizes nodes across several distinct functional groups:[^32]

* **Utilities:** Start, End, Evaluate, Branch, HTTP request, Delay, DataParser, Data Transform, Call Workflow, Page connector, Profile, Generate OTP, Validate OTP, SocialHour, Cryptographic Hash, Decryption, and Encryption[^36].
* **Channels:** Send SMS, Push, RCS Capability, RCS Message, In-app messaging, Email, Messenger, Send Voice, Apple Messages for Business, WhatsApp, and Receive[^33].
* **Embedded Voice Nodes:** Call User, Voice Node Group, Play, Record, Collect Input, IVR Menu, and Call Patch nodes[^34].
* **Integrations:** Create Chat, Validate Chat, Inbound Webhooks, Outbound Webhooks, Custom Events, Generic Bot, and Custom Node[^35].
* **Voice Flow Nodes (Deprecated):** The Voice Flow node set (Start, Disconnect, Play, Collect Input, Call URL, Evaluate, Call Transfer, Dial DTMF, Send, Record, Call Project) is marked as deprecated on the index[^18].

## Utility nodes

The Evaluate node runs JavaScript code during flow execution for computations or data transformations not handled by other nodes[^21]. The node provides 4 predefined function libraries: imi_general, imi_base64, imi_strings, and imi_array[^22]. It returns numeric script results as decimal values; prefixing an expression with '' + converts the result to a string without the decimal portion[^20]. In Bot Builder-enabled tenants, tenants may make at most 1000 requests per month to generate Evaluate node scripts using AI[^19].

Branch node conditions support Equals, Not equals, Less than, Greater than, Less than or equals, Greater than or equals, RegEx, Equals ignore case, Contains, Contains ignore case, In, Not in, Starts with, Ends with, and Between[^5]. Multiple conditions within a single branch can be combined with AND (true only if both relations are true) or OR (true if either relation is true)[^2]. Conditions in different branches are validated sequentially[^6]. WarmTransfer's reading of the sources is that because branches are validated sequentially, branch order determines which outcome is taken when conditions in more than 1 branch could match[^3]. If no condition evaluates true, the node exits via a default None of the above outcome[^4].

The HTTP Request node supports GET, POST, PUT, PATCH, and DELETE methods[^25]. The node provides 2 timeout settings: Connection Timeout (failure to establish a connection) and Request Timeout (no response received)[^31]. The maximum configurable HTTP Request timeout is 20000 milliseconds from release v5.6.3 onwards[^24]. Output variables exposed by the node include https.statusCode, https.statusText, https.responseBody, and https.responseHeaders[^28]. It can extract values from JSON or XML responses using a built-in data parser[^29]. It exits via onSuccess when executed successfully, onError for invalid input, and onTimeout when response time exceeds the configured threshold[^27]. Webex Connect documentation recommends building retries as a flow loop around the HTTP or integration node, retrying a failed request 3 times with delays between attempts, rather than using a built-in retry setting[^30].

The Data Parser node converts JSON or XML data into key-value pairs exposed as named output variables[^14].

The Delay node pauses execution for a set number of seconds or until a specified date and time[^16]. When configured for x seconds, processing is delayed by at least x seconds, and the actual delay can be longer depending on active flow sessions in the tenant[^15]. The Delay node exits onTimeout when the wait completes, exits onError for invalid input, and exposes delay.waitTime as an output variable[^17].

The Generate OTP node creates Alphabetic, Numeric, or Alphanumeric OTPs (Alphanumeric by default) with a length between 4 and 64 characters (default is 6)[^37]. An OTP is valid for 30 minutes by default, though this duration is configurable; a resend generates a new OTP or reuses the current one, resetting validity in both cases[^39]. The node requires a unique transaction reference, outputs generateOTP.OTP, and exits via onSuccess or onError[^38]. The Validate OTP node exits onSuccess when verified, onError on invalid input, and onFail when the OTP is incorrect[^53]. Regenerating the service key during an active session causes OTP nodes to fail for existing sessions[^54].

## Canvas structure and sub-flows

The Call Workflow node invokes another flow within the same service, passing flow context and session data[^10]. Only custom variables from the parent flow are accessible within the invoked child flow[^9]. If a calling flow lacks channel nodes but invokes a flow that contains them, a 'Channel Bean is null' error can occur; Cisco documents placing a placeholder Send node in the parent flow as the fix[^8]. Modularising a flow with Call Workflow is recommended when a flow exceeds 150 nodes[^7].

Flow canvas loading typically slows once a flow exceeds 200 nodes, and Page Connector is positioned as a method to split a flow across canvas pages[^40]. The Page Connector node must connect to a target node on the chosen page; because flow variables are not automatically shared across pages, custom variables must be used to pass values[^41].

## Channel nodes

The Receive node pauses flow execution until an incoming customer message or event arrives, exiting via onReceive when one arrives or ontimeout when none arrives within the configured Max Timeout in seconds[^51]. Channels supported by Receive include SMS, Voice, MMS, Messenger, Instagram (marked deprecated), WhatsApp, Email, Apple Messages for Business, RCS, Live Chat/In-App Messaging, and Custom Events[^50]. When handling SMS, the node matches keywords on the first word of the message; if the incoming message contains only the keyword, sms.message is empty[^52].

## Webex Contact Center task integration nodes

Webex Connect includes several Webex Contact Center (Webex CC) task integration nodes: Create Task, Set Variable, Queue Task, PIQ and EWT, Routed Notification, Modify Notification, Screen Pop, Close Task, and Resolve Conversation[^58]. Task nodes use a node authorization created under Assets > Integrations > Manage Integrations > Node Authorizations using OAuth2 sign-in to obtain access tokens for Webex CC APIs[^57]. If the authorizing credentials change in the integrating system, Webex Connect loses integration access[^56].

The Create Task node calls the Webex Contact Center Task API to create a new task and returns the Task ID and Conversation ID[^12].

The Queue Task node invokes the Webex CC Queue Task API to place the conversation's task into Webex Contact Center for agent allocation, selecting a queue statically or dynamically[^47]. When a flow requires more than 1 Queue Task node, Cisco recommends placing each node in a separate sub-flow reached from a branch and invoking those sub-flows using Call Workflow[^49].

The PIQ and EWT node can currently be used only after the Queue Task node and while the interaction is actively queued[^44]. It accepts a Queue ID and a Lookback Minutes value between 5 and 240 to calculate estimated wait time (EWT); EWT calculation requires valid data for at least 80 percent of the lookback period[^42]. The node exits via Success when both values are non-negative, Insufficient Information when PIQ is valid but EWT is -1, and Failure when the APIs fail or return invalid values[^43].

The Close Task node is a global node calling the Webex CC Close Task API using 1 of 3 methods: Close Task Accept, Close Task Reject (with reason and reason code), or Close Task on WxCC[^11].

## See also

* [Webex Connect digital channel flow orchestration](https://warmtransfer.net/knowledge/webex-connect-digital-flows)
* [Webex Contact Center Flow Designer architecture](https://warmtransfer.net/knowledge/webex-cc-flow-designer)
* [Webex Contact Center APIs and webhooks](https://warmtransfer.net/knowledge/webex-cc-apis)

## Applicability

Applies to: Cisco Webex Connect and Cisco Webex Connect with Webex Contact Center. Deployments: multi-tenant. Sources checked 2026-09-24. The maximum HTTP Request node timeout configuration of 20000 milliseconds applies to release v5.6.3 and later[^24]. The monthly quota of 1000 AI script generation requests in the Evaluate node applies specifically to Bot Builder-enabled tenants[^19].

## What remains uncertain

Details regarding the remaining Webex CC task nodes (Set Variable, Routed Notification, Modify Notification, Screen Pop, and Resolve Conversation) are not covered by the sources below.

Detailed specifications for individual channel nodes (Send SMS, WhatsApp, Messenger, Email, Apple Messages for Business, RCS, and In-app messaging) are not covered by the sources below.

Default timeout values, payload size limits, and whether non-2xx status codes exit via onSuccess for the HTTP Request node are not covered by the sources below.

The default and maximum values for the Receive node Max Timeout parameter are not covered by the sources below.

A raw-HTML check of Create Task and Queue Task outcome names and casing is not covered by the sources below.

Specifications for utility and integration nodes not detailed above (Profile, SocialHour, Data Transform, cryptographic nodes, Custom Node, Generic Bot, Inbound Webhooks, Outbound Webhooks, and Custom Events) are not covered by the sources below.

Specifications for embedded voice nodes (Call User, Play, Collect Input, IVR Menu, Call Patch, Record, and Voice Node Group) are not covered by the sources below.

Node version history and the mapping of platform release v5.6.3 to a specific calendar date are not covered by the sources below.

## Sources

[^1]: In Webex CC digital flows the AI Agent node sends customer messages to a bot built in Webex Connect Bot Builder, and when the bot cannot resolve the query the flow hands the chat to a Webex CC agent through the Queue Task node. Source: [Configuring flows with AI Agent Node - WXCC](https://help.webexconnect.io/docs/configuring-flows-with-ai-agent-node), Configuring flows with AI Agent Node - WXCC, flow description. Checked 2026-09-24.
[^2]: Within a Branch node branch, multiple conditions can be combined with AND (true only if both relations are true) or OR (true if either relation is true). Source: [Branch Node](https://help.webexconnect.io/docs/branch), Branch Node, combining conditions. Checked 2026-09-24.
[^3]: Because branches are validated sequentially, when conditions in more than one branch could match, branch order determines which outcome is taken (inferred). Source: [Branch Node](https://help.webexconnect.io/docs/branch), Branch Node, evaluation order note. Checked 2026-09-24.
[^4]: When no Branch node condition evaluates true, the node exits through a default None of the above outcome. Source: [Branch Node](https://help.webexconnect.io/docs/branch), Branch Node, node outcomes. Checked 2026-09-24.
[^5]: Branch node conditions support Equals, Not equals, Less than, Greater than, Less than or equals, Greater than or equals, RegEx, Equals ignore case, Contains, Contains ignore case, In, Not in, Starts with, Ends with and Between. Source: [Branch Node](https://help.webexconnect.io/docs/branch), Branch Node, condition operators. Checked 2026-09-24.
[^6]: Branch node conditions in different branches are validated sequentially. Source: [Branch Node](https://help.webexconnect.io/docs/branch), Branch Node, evaluation order note. Checked 2026-09-24.
[^7]: The Call Workflow page recommends modularising a flow with Call Workflow when it exceeds 150 nodes. Source: [Call Workflow Node](https://help.webexconnect.io/docs/call-workflow), Call Workflow Node, best-practice note. Checked 2026-09-24.
[^8]: If a calling flow has no channel nodes but invokes a flow that does, a 'Channel Bean is null' error can occur; the documented fix is a placeholder Send node in the parent flow. Source: [Call Workflow Node](https://help.webexconnect.io/docs/call-workflow), Call Workflow Node, troubleshooting note. Checked 2026-09-24.
[^9]: Only custom variables from the parent flow are accessible in a child flow invoked by Call Workflow. Source: [Call Workflow Node](https://help.webexconnect.io/docs/call-workflow), Call Workflow Node, variables note. Checked 2026-09-24.
[^10]: The Call Workflow node invokes another flow in the same service and passes the current flow context and session data to it. Source: [Call Workflow Node](https://help.webexconnect.io/docs/call-workflow), Call Workflow Node, introduction. Checked 2026-09-24.
[^11]: The Close Task node is a global node that calls the Webex CC Close Task API with one of three methods: Close Task Accept, Close Task Reject (with reason and reason code) or Close Task on WxCC. Source: [Close Task - WXCC](https://help.webexconnect.io/docs/wxcc-close-task), Close Task - WXCC, method selection. Checked 2026-09-24.
[^12]: The Create Task node calls the Webex Contact Center Task API to create a new task and outputs the Task ID and Conversation ID. Source: [Create Task - WXCC](https://help.webexconnect.io/docs/wxcc-create-task), Create Task - WXCC, introduction and output variables. Checked 2026-09-24.
[^13]: In the Create Task node, the WhatsApp source number must be entered without the country code. Source: [Create Task - WXCC](https://help.webexconnect.io/docs/wxcc-create-task), Create Task - WXCC, channel-specific fields. Checked 2026-09-24.
[^14]: The Data Parser node converts JSON or XML data into key-value pairs that are exposed as named output variables. Source: [Data Parser Node](https://help.webexconnect.io/docs/data-parser), Data Parser Node, introduction and output variables. Checked 2026-09-24.
[^15]: A Delay node configured for x seconds delays processing by at least x seconds, and actual delay can be longer depending on active flow sessions in the tenant. Source: [Delay Node](https://help.webexconnect.io/docs/delay), Delay Node, note on delay accuracy. Checked 2026-09-24.
[^16]: The Delay node pauses a flow either for a number of seconds or until a specified date and time. Source: [Delay Node](https://help.webexconnect.io/docs/delay), Delay Node, configuration. Checked 2026-09-24.
[^17]: The Delay node exits onTimeout when the wait completes and onError for invalid input, and exposes delay.waitTime as an output variable. Source: [Delay Node](https://help.webexconnect.io/docs/delay), Delay Node, node outcomes and output variables. Checked 2026-09-24.
[^18]: The Nodes index marks the Voice Flow node set (Start, Disconnect, Play, Collect Input, Call URL, Evaluate, Call Transfer, Dial DTMF, Send, Record, Call Project) as deprecated. Source: [Nodes](https://help.webexconnect.io/docs/nodes), Nodes page, Voice Flow Nodes (Deprecated) heading. Checked 2026-09-24.
[^19]: Each Bot Builder-enabled tenant may make at most 1000 requests per month to generate Evaluate node scripts with AI. Source: [Evaluate Node](https://help.webexconnect.io/docs/evaluate-node), Evaluate Node, AI script generation note. Checked 2026-09-24.
[^20]: The Evaluate node returns a numeric script result as a decimal value; prefixing the expression with '' + converts the result to a string without the decimal portion. Source: [Evaluate Node](https://help.webexconnect.io/docs/evaluate-node), Evaluate Node, note on script output. Checked 2026-09-24.
[^21]: The Evaluate node runs JavaScript code as part of flow execution for computations or data transformations that other nodes cannot handle. Source: [Evaluate Node](https://help.webexconnect.io/docs/evaluate-node), Evaluate Node, introduction. Checked 2026-09-24.
[^22]: The Evaluate node provides four predefined function libraries: imi_general, imi_base64, imi_strings and imi_array. Source: [Evaluate Node](https://help.webexconnect.io/docs/evaluate-node), Evaluate Node, predefined functions section. Checked 2026-09-24.
[^23]: The Evaluate node page as read states no limit on script execution time or script size (inferred). Source: [Evaluate Node](https://help.webexconnect.io/docs/evaluate-node), Evaluate Node, whole page (absence). Checked 2026-09-24.
[^24]: From Webex Connect release v5.6.3 onwards the maximum HTTP Request node timeout configuration is 20000 milliseconds. Source: [HTTP Request Node](https://help.webexconnect.io/docs/http-request), HTTP Request Node, timeout settings note. Checked 2026-09-24.
[^25]: The HTTP Request node supports the GET, POST, PUT, PATCH and DELETE methods. Source: [HTTP Request Node](https://help.webexconnect.io/docs/http-request), HTTP Request Node, method field. Checked 2026-09-24.
[^26]: The HTTP Request node page directs OAuth 2.0 use to the custom integration node capability rather than the standard HTTP Request node. Source: [HTTP Request Node](https://help.webexconnect.io/docs/http-request), HTTP Request Node, authentication note. Checked 2026-09-24.
[^27]: The HTTP Request node exits through onSuccess when the request executes successfully, onError for invalid input, and onTimeout when the response exceeds the configured time. Source: [HTTP Request Node](https://help.webexconnect.io/docs/http-request), HTTP Request Node, node outcomes. Checked 2026-09-24.
[^28]: The HTTP Request node exposes output variables including https.statusCode, https.statusText, https.responseBody and https.responseHeaders. Source: [HTTP Request Node](https://help.webexconnect.io/docs/http-request), HTTP Request Node, output variables. Checked 2026-09-24.
[^29]: The HTTP Request node can extract values from JSON or XML responses using a built-in data parser. Source: [HTTP Request Node](https://help.webexconnect.io/docs/http-request), HTTP Request Node, response parsing section. Checked 2026-09-24.
[^30]: Webex Connect documentation recommends building retries as a flow loop around the HTTP or integration node, retrying a failed request three times with delays between attempts, rather than a built-in retry setting. Source: [HTTP Request Node](https://help.webexconnect.io/docs/http-request), HTTP Request Node, rate limiting / retry guidance. Checked 2026-09-24.
[^31]: The HTTP Request node has two timeout settings: a Connection Timeout for failure to establish the connection and a Request Timeout for no response. Source: [HTTP Request Node](https://help.webexconnect.io/docs/http-request), HTTP Request Node, timeout settings. Checked 2026-09-24.
[^32]: The Webex Connect Nodes index groups flow nodes under Utilities, Channels, Embedded Voice Nodes and Integrations, and lists a separate Voice Flow Nodes group marked Deprecated. Source: [Nodes](https://help.webexconnect.io/docs/nodes), Nodes page, category headings. Checked 2026-09-24.
[^33]: The Channels group on the Nodes index lists Send SMS, Push, RCS Capability, RCS Message, In-app messaging, Email, Messenger, Send Voice, Apple Messages for Business, WhatsApp and Receive. Source: [Nodes](https://help.webexconnect.io/docs/nodes), Nodes page, Flow Nodes > Channels list. Checked 2026-09-24.
[^34]: The Embedded Voice Nodes group on the Nodes index lists Call User, Voice Node Group, Play, Record, Collect Input, IVR Menu and Call Patch nodes. Source: [Nodes](https://help.webexconnect.io/docs/nodes), Nodes page, Embedded Voice Nodes list. Checked 2026-09-24.
[^35]: The Integrations group on the Nodes index lists Create Chat, Validate Chat, Inbound Webhooks, Outbound Webhooks, Custom Events, Generic Bot and Custom Node. Source: [Nodes](https://help.webexconnect.io/docs/nodes), Nodes page, Flow Nodes > Integrations list. Checked 2026-09-24.
[^36]: The Utilities group on the Nodes index lists Start, End, Evaluate, Branch, HTTP request, Delay, DataParser, Data Transform, Call Workflow, Page connector, Profile, Generate OTP, Validate OTP, SocialHour, Cryptographic Hash, Decryption and Encryption. Source: [Nodes](https://help.webexconnect.io/docs/nodes), Nodes page, Flow Nodes > Utilities list. Checked 2026-09-24.
[^37]: The Generate OTP node produces Alphabetic, Numeric or Alphanumeric OTPs (Alphanumeric by default) with a length from 4 to 64 characters (6 by default). Source: [Generate OTP Node](https://help.webexconnect.io/docs/generate-otp), Generate OTP Node, OTP format and length fields. Checked 2026-09-24.
[^38]: The Generate OTP node requires a unique transaction reference, exposes the OTP as generateOTP.OTP, and exits onSuccess or onError. Source: [Generate OTP Node](https://help.webexconnect.io/docs/generate-otp), Generate OTP Node, transaction reference, output variables and node outcomes. Checked 2026-09-24.
[^39]: A Generate OTP node OTP is valid for 30 minutes by default, the period is configurable, and a resend either generates a new OTP or reuses the current one with the validity reset in both cases. Source: [Generate OTP Node](https://help.webexconnect.io/docs/generate-otp), Generate OTP Node, validity and resend fields. Checked 2026-09-24.
[^40]: The Page Connector page states that flow canvas loading typically slows once a flow has more than 200 nodes, and positions Page Connector as a way to split a flow across canvas pages. Source: [Page Connector Node](https://help.webexconnect.io/docs/page-connector), Page Connector Node, introduction note. Checked 2026-09-24.
[^41]: The Page Connector node must be connected to a target node on the selected page, and flow variables are not automatically shared across pages, so custom variables are used to share values. Source: [Page Connector Node](https://help.webexconnect.io/docs/page-connector), Page Connector Node, configuration and notes. Checked 2026-09-24.
[^42]: The PIQ and EWT node takes a Queue ID and a Lookback Minutes value between 5 and 240 used to calculate EWT, and EWT needs valid data for at least 80 percent of the lookback period. Source: [PIQ and EWT - WXCC](https://help.webexconnect.io/docs/wxcc-piq-and-ewt), PIQ and EWT - WXCC, configuration fields. Checked 2026-09-24.
[^43]: The PIQ and EWT node exits Success when both values are non-negative, Insufficient Information when PIQ is valid but EWT is -1, and Failure when the APIs fail or return invalid values. Source: [PIQ and EWT - WXCC](https://help.webexconnect.io/docs/wxcc-piq-and-ewt), PIQ and EWT - WXCC, node outcomes. Checked 2026-09-24.
[^44]: The PIQ and EWT node can currently be used only after the Queue Task node and only while the interaction is actively queued. Source: [PIQ and EWT - WXCC](https://help.webexconnect.io/docs/wxcc-piq-and-ewt), PIQ and EWT - WXCC, usage note. Checked 2026-09-24.
[^45]: Dynamic queue selection in the Queue Task node requires node version 1.5 or later. Source: [Queue Task - WXCC](https://help.webexconnect.io/docs/wxcc-queue-task), Queue Task - WXCC, queue details (dynamic). Checked 2026-09-24.
[^46]: Queue Task node outcomes include a Queued success outcome and failure outcomes including taskFailed, onError, onInvalidData, onauthorizationfail and onTimeout, and outputs include taskId and agentId. Source: [Queue Task - WXCC](https://help.webexconnect.io/docs/wxcc-queue-task), Queue Task - WXCC, node outcomes and output variables. Checked 2026-09-24.
[^47]: The Queue Task node calls the Webex CC Queue Task API to queue the conversation's task in Webex Contact Center for agent allocation, using a queue selected statically or dynamically. Source: [Queue Task - WXCC](https://help.webexconnect.io/docs/wxcc-queue-task), Queue Task - WXCC, introduction and queue details. Checked 2026-09-24.
[^48]: For skill-based queues the Queue Task node takes one or more Skill, Skill Condition and Skill Value entries, supports skill relaxation with a default timeout of 60 seconds, and accepts a contact priority from 1 to 9. Source: [Queue Task - WXCC](https://help.webexconnect.io/docs/wxcc-queue-task), Queue Task - WXCC, skill-based routing section. Checked 2026-09-24.
[^49]: When a flow needs more than one Queue Task node, Cisco recommends putting each in a separate sub-flow reached from a branch and invoking the sub-flows with Call Workflow. Source: [Queue Task - WXCC](https://help.webexconnect.io/docs/wxcc-queue-task), Queue Task - WXCC, note on multiple Queue Task nodes. Checked 2026-09-24.
[^50]: The Receive node supports SMS, Voice, MMS, Messenger, Instagram (marked deprecated), WhatsApp, Email, Apple Messages for Business, RCS, Live Chat/In-App Messaging and Custom Events. Source: [Receive Node](https://help.webexconnect.io/docs/receive), Receive Node, channel selection. Checked 2026-09-24.
[^51]: The Receive node pauses flow execution until an incoming customer message or event arrives, and exits onReceive when one arrives or ontimeout when none arrives within the configured Max Timeout in seconds. Source: [Receive Node](https://help.webexconnect.io/docs/receive), Receive Node, configuration and node outcomes. Checked 2026-09-24.
[^52]: For SMS the Receive node matches keywords on the first word of the incoming message; if only the keyword is sent, sms.message is empty. Source: [Receive Node](https://help.webexconnect.io/docs/receive), Receive Node, SMS keyword note. Checked 2026-09-24.
[^53]: The Validate OTP node exits onSuccess when the OTP is verified, onError when validation fails due to invalid input, and onFail when the OTP is incorrect. Source: [Validate OTP Node](https://help.webexconnect.io/docs/validate-otp), Validate OTP Node, node outcomes. Checked 2026-09-24.
[^54]: If the service key is regenerated during a session, the OTP nodes fail for existing sessions. Source: [Validate OTP Node](https://help.webexconnect.io/docs/validate-otp), Validate OTP Node, note. Checked 2026-09-24.
[^55]: Webex Connect flows reference custom variables as $(variableName) and node output variables as $(nodeID.variablename), and variable names are case-sensitive. Source: [Evaluate Node](https://help.webexconnect.io/docs/evaluate-node), Evaluate Node, variables section. Checked 2026-09-24.
[^56]: If the authorizing credentials change in the integrating system, Webex Connect loses access to the integration. Source: [Webex CC Task Integration Nodes and Node Authorizations](https://help.webexconnect.io/docs/wxcc-task-integration-nodes-and-node-authorizations), Node Authorizations section, note. Checked 2026-09-24.
[^57]: Webex CC task nodes use a node authorization, created under Assets > Integrations > Manage Integrations > Node Authorizations via OAuth2 sign-in, to obtain the access token for Webex CC APIs. Source: [Webex CC Task Integration Nodes and Node Authorizations](https://help.webexconnect.io/docs/wxcc-task-integration-nodes-and-node-authorizations), Node Authorizations section. Checked 2026-09-24.
[^58]: The Webex CC task integration nodes in Webex Connect are Create Task, Set Variable, Queue Task, PIQ and EWT, Routed Notification, Modify Notification, Screen Pop, Close Task and Resolve Conversation. Source: [Webex CC Task Integration Nodes and Node Authorizations](https://help.webexconnect.io/docs/wxcc-task-integration-nodes-and-node-authorizations), Webex CC Task Integration Nodes and Node Authorizations, node list. Checked 2026-09-24.