Skip to main content
Actions are configured in the dashboard, and the chat UI renders their results automatically: product cards, result lists, forms, and navigation cards all appear inline in the conversation without integration code. The two payloads worth knowing as an integrator are navigation cards, because you wire them to your router, and sign-in cards, because they involve your auth flow. When the agent answers a “where do I…” question, it can attach a navigation card that deep-links into your product:
  • Web embed: the card click posts a message to your host page. Your embed snippet’s listener handles it; see Embed navigation.
  • React Native: the SDK calls your onNavigate(path) callback:
Paths always come from your workspace’s navigation route registry, never from user input. See Navigation routes for how the registry is built.

​
Sign-in cards (customer login)

When a customer-authorized tool requires sign-in, the agent can return a sign-in card instead of running the operation. Keep the authorization flow in your backend or connector and treat the card as UI, not proof of identity. Mount the widget with a consistent endUserId so sessions and memory remain associated with the same application user. Treat that value as context only; private account authorization belongs in your backend or connector. See Authentication & identity.

​
Other widgets

Result lists, forms, and custom widgets configured under Widgets render automatically in the web embed. The React Native SDK currently renders NavigationCard natively and shows a JSON fallback for other custom widgets; see React Native SDK limitations.

Skills

How builders create the actions behind these payloads.

Response mapping

How API JSON becomes widget props.

Manage tokens

Static and customer-login credentials for actions.

Embed navigation

Navigation card clicks on the host page.