Webex Contact Center — Express OAuth token service (Contact Center)

Webex Contact Center — Express OAuth token service

Playbook by Webex for Developers

Webex Contact Center — Express OAuth token service

Flow Designer–friendly: store Webex tokens, scheduled refresh, GET /api/token with trusted headers.

Flow Designer–friendly: store Webex tokens, scheduled refresh, GET /api/token with trusted headers.
View Playbook
Playbook by Webex for Developers

A compact Node.js and Express service for teams that need a durable Webex access token for Webex Contact Center automation—especially Flow Designer HTTP Request blocks—without embedding long-lived secrets in the flow itself.

What you get

  • Browser OAuth — Visit /login once; the callback exchanges the authorization code and stores tokens.
  • Scheduled refresh — A background job loads the refresh token from SQLite (Sequelize), refreshes with Webex, and keeps access tokens current.
  • GET /api/token — Trusted callers retrieve a token when headers (org, cluster, source IP) match the checks in this Playbook—mirroring the kind of alignment WxCC integration guides recommend.

Good for

Backend developers and contact-center engineers who want a repeatable pattern to experiment with token storage, refresh timing, and header validation before moving to vault-backed secrets, full authz, and multi-tenant operations.

Demonstration code for learning; not a production-hardened service.


Preview listing

This App Hub entry was published from an open pull request. Review the change.

Support

Third-Party Tool

Estimated Implementation Time

2-4 hours

Categories

A compact Node.js and Express service for teams that need a durable Webex access token for Webex Contact Center automation—especially Flow Designer HTTP Request blocks—without embedding long-lived secrets in the flow itself.

What you get

  • Browser OAuth — Visit /login once; the callback exchanges the authorization code and stores tokens.
  • Scheduled refresh — A background job loads the refresh token from SQLite (Sequelize), refreshes with Webex, and keeps access tokens current.
  • GET /api/token — Trusted callers retrieve a token when headers (org, cluster, source IP) match the checks in this Playbook—mirroring the kind of alignment WxCC integration guides recommend.

Good for

Backend developers and contact-center engineers who want a repeatable pattern to experiment with token storage, refresh timing, and header validation before moving to vault-backed secrets, full authz, and multi-tenant operations.

Demonstration code for learning; not a production-hardened service.


Preview listing

This App Hub entry was published from an open pull request. Review the change.