Contact Center Flow Designer: Integrating Third-Party APIs with the HTTP Integration Connector

Publisher

Cisco Systems, Inc. (Webex for Developers)

URL

https://developer.webex.com/blog/contact-center-flow-designer-integrating-third-party-apis-with-the-http-integration-connector

Published

2024-05-13

Updated

unknown

Accessed

2026-09-04

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• To call a third-party API through a connector, turn on Use Authenticated Endpoint in the HTTP Request settings and pick the custom connector from the Connector list. in context
• A custom connector for a third-party API takes the API's resource domain URL, which must be HTTPS, and supports OAuth 2.0 (client credentials or password grant) or Basic Auth. in context
• The Flow Designer HTTP connector for WxCC APIs handles authentication tokens natively, removing the need for a separate token server that stores and refreshes integration tokens. in context
• When using the WxCC HTTP connector the flow author supplies only the API path, and the connector supplies the rest of the URL. in context
• Cisco recommends routing the HTTP connector result through a Case activity that handles every error code listed in the API definition. in context
• Webex Contact Center API calls made from Flow Designer (HTTP connector) are rate limited, and flows should handle 429 responses gracefully. in context
• Custom HTTP connectors configured for OAuth 2.0 support Client Credentials and Password grant types, requiring Client ID, Client Secret, Token URL, and Scope fields. in context
• A Webex Contact Center API connector can be created with Read-Only access, which covers GET calls only, or Read-Write access, which is needed for POST, PUT or update calls. in context
• API calls made from Flow Designer are rate limited, and Cisco advises flows to handle HTTP 429 responses gracefully. in context
• The HTTP Request activity has a 'Use Authenticated Endpoint' toggle: when it is on, the flow uses a connector configured in Control Hub and supplies only the request path, and the connector handles the base URL and OAuth tokens. in context
• An HTTP Request that sends a POST or PUT to Webex Contact Center APIs through a Read-Only connector is likely to fail authorisation, so connector access rights should be checked when write calls fail but reads succeed. inferred in context
• The HTTP Request activity has Response Timeout and Number of Retries fields, along with Use Authenticated Endpoint, Connector, Request Path, Method and Content Type. in context
• The HTTP Request activity has Parse Settings, an Output Variable and a Path Expression, that extract a value from the response into a flow variable for later activities. in context

Cite this source record

APA

WarmTransfer. (2024, May 13). Contact Center Flow Designer: Integrating Third-Party APIs with the HTTP Integration Connector. WarmTransfer. https://warmtransfer.net/knowledge/sources/webex-dev-blog-flow-designer-http-connector

BibTeX

@misc{warmtransfer-webex-dev-blog-flow-designer-http-connector,
  title  = {Contact Center Flow Designer: Integrating Third-Party APIs with the HTTP Integration Connector},
  author = {{WarmTransfer}},
  year   = {2024},
  url    = {https://warmtransfer.net/knowledge/sources/webex-dev-blog-flow-designer-http-connector},
  note   = {Cisco Systems, Inc. (Webex for Developers), accessed 2026-09-04}
}