Qiscus Omnichannel icon

Qiscus Omnichannel

Consume Qiscus Omnichannel API

Actions6

Auth → Get Identity Token

AI-generated

Summary

Requests an identity token from Qiscus Omnichannel (POST api/v1/auth/get_identity_token) for SDK JWT authentication, using an admin/user token and optional user identity details.

Inputs

  • userToken (required) — User/admin authentication token, sent as the Authorization header. Typically piped from a Login Admin node via expression.
  • email — Email of the user identity to authenticate. Sent as email only if non-empty.
  • name — Display name of the user. Sent as name only if non-empty.
  • avatarUrl — Avatar image URL of the user. Sent as avatar_url only if non-empty.
  • nonce — Nonce value for replay protection. Sent as nonce only if non-empty.

Output shape

One output item per input item, containing the API response as JSON (an array response is split into multiple items).

The request is sent as form data with app_id taken from the Qiscus credentials, and the Qiscus-App-Id header is also set. The request uses json:false, so the response may come back as a raw string rather than a parsed object. If Continue On Fail is enabled, errors are returned as an item with an error message.

Examples

Example 1: Issue an identity token for a web chat user after admin login

Chain Login Admin first, then set User Token to the expression for its token. Set Email and Name from the customer data, optionally Avatar URL and Nonce.

Links

Discussion