Calling an external API from a Webex Contact Center flow

See also

Sources

1. 1
   The Flow Designer HTTP Request activity fetches information from an external data source such as a CRM using standard HTTP protocols.

   Build and manage flows with Flow Designer · HTTP Request activity section (seen via search-engine index excerpt only) · Checked 2026-09-30
2. 2
   When an HTTP Request activity is placed immediately after the Queue Contact activity, the HTTP Request may not retrieve the required data.

   Build and manage flows with Flow Designer · note sentence returned verbatim by WebFetch · Checked 2026-09-30
3. 3
   The HTTP Request activity supports Basic Auth and OAuth 2.0 attributes for authenticated endpoints.

   Build and manage flows with Flow Designer · HTTP Request activity section (search-engine index excerpt) · Checked 2026-09-30
4. 4
   Cisco recommends not logging sensitive response data from API calls made in flows.

   Using the New HTTP Connector for Webex Contact Center APIs · best practices section · Checked 2026-09-30
5. 5
   Cisco's verification step is a Case activity placed right after the HTTP Request activity that checks the status code for 200 OK.

   Configure HTTP Request on Call Flows with Authorization Type as Basic on WebEx Contact Center · Verify · Checked 2026-09-30
6. 6
   The ID of a Webex Contact Center HTTP connector cannot be modified after creation.

   Create Webex Contact Center HTTP connector · Create the connector procedure, note · Checked 2026-09-30
7. 7
   Connectors are created in Control Hub under Contact Center, Integrations, Connectors.

   Using the New HTTP Connector for Webex Contact Center APIs · creating the connector steps · Checked 2026-09-30
8. 8
   Creating a Webex Contact Center HTTP connector requires the Full Administrator, External Full Administrator, or Contact Center Service Administrator role.

   Create Webex Contact Center HTTP connector · Before you begin · Checked 2026-09-30
9. 9
   A custom connector supports Basic Authentication (the default) and OAuth 2.0 with the grant types Client credentials - certificate, Client credentials - client secret, and Password Grant.

   Configure custom connector for Webex Contact Center · Configure custom connector procedure, Authentication Type · Checked 2026-09-30
10. 10
    For Basic Authentication, a custom connector takes a Username, a Password and a Validation URL used to validate the username and password.

    Configure custom connector for Webex Contact Center · Configure custom connector procedure, Basic Authentication fields · Checked 2026-09-30
11. 11
    An organization can have at most 10 custom connectors.

    System limits in Webex Contact Center · Table 1, Number of Connectors row · Checked 2026-09-30
12. 12
    For OAuth 2.0, a custom connector takes a Token URL for the authorization server and a Scope, plus Client ID and Client Secret (client secret and password grants), Username and Password (password grant), or a public and private key certificate (certificate grant).

    Configure custom connector for Webex Contact Center · Configure custom connector procedure, OAuth 2.0 fields · Checked 2026-09-30
13. 13
    A custom connector's Resource Domain URL must be entered with an https:// prefix.

    Configure custom connector for Webex Contact Center · Configure custom connector procedure, Resource Domain URL · Checked 2026-09-30
14. 14
    Deactivating a Webex Contact Center HTTP connector halts call routing for any flows that use it.

    Create Webex Contact Center HTTP connector · Manage the connector, deactivate note · Checked 2026-09-30
15. 15
    Flow debugging can decrypt logs selectively, based on administrator privileges set in user profiles, with flow-level and activity-level decryption settings and extra search filters.

    What's new for administrators in Webex Contact Center · entry on enhanced Flow Debugging (search-engine index excerpt; entry date not seen) · Checked 2026-09-30
16. 16
    Deleting a Webex Contact Center HTTP connector removes its functions from the workflows that use it.

    Create Webex Contact Center HTTP connector · Manage the connector, delete note · Checked 2026-09-30
17. 17
    Because a JSONPath that matches nothing returns an empty result, and Cisco does not document what Flow Designer writes to the output variable in that case, a lookup flow should test the parsed variable for empty before routing on it.inferred

    RFC 9535: JSONPath: Query Expressions for JSON · Section 2.1.2, applied to Flow Designer Parse Settings · Checked 2026-09-30
18. 18
    Flow Designer functions let you write custom code inline in a code editor, in JavaScript or Python, and reuse it across flows.

    Build and manage flows with Flow Designer · Create and manage functions (search-engine index excerpt; heading confirmed by WebFetch) · Checked 2026-09-30
19. 19
    An organization supports at most 200 functions, and each function gets at most 128 MB of memory.

    Build and manage flows with Flow Designer · Create and manage functions, limitations (search-engine index excerpt) · Checked 2026-09-30
20. 20
    Values returned by a Function activity can be parsed and set into flow variables, and flow logic can branch on the activity's output variables and status or error codes.

    What's new for administrators in Webex Contact Center · entry introducing the Function activity (search-engine index excerpt; entry date not seen) · Checked 2026-09-30
21. 21
    Function code can be tested with sample values, showing outputs and errors, before the flow is published.

    Build and manage flows with Flow Designer · Create a function (search-engine index excerpt) · Checked 2026-09-30
22. 22
    The HTTP Request activity supports a GraphQL content type for APIs that accept GraphQL.

    What's new for administrators in Webex Contact Center · entry on HTTP activity GraphQL content type (search-engine index excerpt; entry date not seen) · Checked 2026-09-30
23. 23
    Cisco recommends that flows calling Contact Center APIs allow for rate limiting, handle HTTP 429 responses gracefully, and handle documented API error codes with Case activities.

    Using the New HTTP Connector for Webex Contact Center APIs · best practices section · Checked 2026-09-30
24. 24
    Flow developers can create custom flow variables of type JSON and use them in the HTTP Request, Parse and Set Variable activities, including storing data extracted with a JSON path filter expression.

    Build and manage flows with Flow Designer · Flow variables, JSON variable type (search-engine index excerpt) · Checked 2026-09-30
25. 25
    The result of a JSONPath query under RFC 9535 is a nodelist, which can be empty when nothing matches.

    RFC 9535: JSONPath: Query Expressions for JSON · Section 2.1.2 · Checked 2026-09-30
26. 26
    In JSONPath (RFC 9535), a query starts with the root identifier $, which stands for the root node of the JSON value being queried.

    RFC 9535: JSONPath: Query Expressions for JSON · Section 2.2.2 · Checked 2026-09-30
27. 27
    RFC 9535 defines name (dot-notation), wildcard, index and filter (?) selectors for picking members and array elements out of a JSON value.

    RFC 9535: JSONPath: Query Expressions for JSON · Sections 2.3.1, 2.3.2, 2.3.3, 2.3.5 · Checked 2026-09-30
28. 28
    Cisco recommends Read-Only access for a Webex Contact Center connector used only for GET calls, keeping Read-Write for calls that create or update data.

    Using the New HTTP Connector for Webex Contact Center APIs · best practices section · Checked 2026-09-30
29. 29
    Flow Designer has no version control feature; the flow version number counts how many times the flow has been published.

    Build and manage flows with Flow Designer · flow version description (sentence returned verbatim by WebFetch) · Checked 2026-09-30
30. 30
    Without a connector, turn off Use Authenticated Endpoint, enter the complete request URL, and add an Authorization header whose value is Basic followed by the Base64 encoding of username:password.

    Configure HTTP Request on Call Flows with Authorization Type as Basic on WebEx Contact Center · Configure, method without connector · Checked 2026-09-30
31. 31
    An open request that carries a hand-built Basic Authorization header stores a reversible credential inside the flow definition rather than in a Control Hub connector, so anyone who can edit or export the flow can recover it.inferred

    Configure HTTP Request on Call Flows with Authorization Type as Basic on WebEx Contact Center · Configure, method without connector (header value is plain Base64) · Checked 2026-09-30
32. 32
    The HTTP Request activity exposes an httpResponseBody output variable that returns the response body of the request.

    Build and manage flows with Flow Designer · HTTP Request activity, output variables (search-engine index excerpt) · Checked 2026-09-30
33. 33
    The HTTP Request activity exposes an httpStatusCode output variable that returns the HTTP status code of the request.

    Build and manage flows with Flow Designer · HTTP Request activity, output variables (search-engine index excerpt) · Checked 2026-09-30
34. 34
    In the HTTP Request activity's Parse Settings, the response can be parsed into flow variables using a JSON Path expression to find specific fields.

    Create Webex Contact Center HTTP connector · Use the connector in Flow Designer; Parse Settings bullet · Checked 2026-09-30
35. 35
    Path Expression is required on each parsed variable row in Parse Settings; leaving it blank fails validation and the flow cannot be published.

    Build and manage flows with Flow Designer · HTTP Request activity, Parse Settings (search-engine index excerpt) · Checked 2026-09-30
36. 36
    With a connector selected, the Request Path holds only the API path, not the full URL; the connector supplies the base domain.

    Using the New HTTP Connector for Webex Contact Center APIs · HTTP Request activity configuration · Checked 2026-09-30
37. 37
    The Set Variable activity can set up to 10 variables or expressions in a single operation.

    What's new for administrators in Webex Contact Center · entry on enhanced Set Variable activity (search-engine index excerpt; entry date not seen) · Checked 2026-09-30
38. 38
    To use a connector, turn on Use Authenticated Endpoint in the HTTP Request activity and pick the connector from the Connector drop-down.

    Create Webex Contact Center HTTP connector · Use the connector in Flow Designer · Checked 2026-09-30
39. 39
    The Use Authenticated Endpoint toggle in the HTTP Request activity can be turned off.

    Configure custom connector for Webex Contact Center · use in Flow Designer note · Checked 2026-09-30
40. 40
    An error-handling path named Undefined Error can be configured to handle system errors.

    Build and manage flows with Flow Designer · activity error handling description (sentence returned verbatim by WebFetch) · Checked 2026-09-30
41. 41
    A flow must be validated and its errors fixed before it can be published; publishing stays disabled until errors are resolved.

    Build and manage flows with Flow Designer · Validate and publish a flow (Validation toggle in footer pane) · Checked 2026-09-30
42. 42
    The HTTP activity retrieves data from external systems with GET and sends data to them with the other supported verbs PUT, POST and DELETE.

    Design Delightful Customer Experiences with Webex Contact Center Flow Designer · HTTP Activity section · Checked 2026-09-30
43. 43
    Flow Designer lets you apply version labels such as Dev, Test and Live to a flow to support blue-green style deployment.

    Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer · Flow Versioning section · Checked 2026-09-30
44. 44
    Creating a Webex Contact Center HTTP connector requires a unique Name, an access level of Read-Only or Read-Write, and confirming authorization to read, write, modify and delete Contact Center data.

    Create Webex Contact Center HTTP connector · Create the connector procedure · Checked 2026-09-30
45. 45
    An organization can have at most 5 Webex Contact Center connectors.

    System limits in Webex Contact Center · Table 1, Number of Connectors row · Checked 2026-09-30
46. 46
    The Webex Contact Center HTTP connector handles authentication natively, removing the need for a separate integration and token server to call Contact Center APIs from a flow.

    Using the New HTTP Connector for Webex Contact Center APIs · introduction · Checked 2026-09-30
47. 47
    The Webex Contact Center HTTP connector lets flow developers invoke Webex Contact Center APIs from Flow Designer.

    Create Webex Contact Center HTTP connector · introduction · Checked 2026-09-30
48. 48
    For a Contact Center API call, the HTTP Request activity is configured with Connector, Request Path, Method (the REST verb), optional Query Parameters, and Content Type set to Application/JSON.

    Create Webex Contact Center HTTP connector · Use the connector in Flow Designer · Checked 2026-09-30

Documents

Cite this page

WarmTransfer. (2026, September 30). Calling an external API from a Webex Contact Center flow. WarmTransfer. https://warmtransfer.net/guides/wxcc-http-request-setup

@misc{warmtransfer-wxcc-http-request-setup,
  title  = {Calling an external API from a Webex Contact Center flow},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/guides/wxcc-http-request-setup},
  note   = {Verified 2026-09-30}
}