Build on Aktor

End users, the assistant, the widget and chat channels

Put agents in front of your own customers, each reaching only their own data.

Your customers aren't members of your organization. They sign in to your app, and Aktor accepts one of two credentials for them on the apps API:

  1. An Aktor end-user token. Your backend calls POST /api/v1/apps/{installId}/end-user-tokens with the solution's app key and { user_id, name }, and gets a short-lived aeu_… token (see Connect your app).
  2. Your own sign-in token (JWT). Declare your identity provider, and Aktor checks your JWTs against its published keys (RS/PS/ES algorithms):
end_users:
  jwt:
    issuer: https://auth.example.com/
    audience: my-app
    jwks_url: https://auth.example.com/.well-known/jwks.json
    user_claim: sub

The assistant is the agent your customers talk to:

assistant:
  name: Resident helper
  instructions_file: assistant.md
  data: { Ticket: write, Lease: read }
  allowed_origins: ["https://app.example.com"]
  max_messages_per_minute: 10
  monthly_cost_limit_usd_per_user: 2.00

Each conversation's tools are bound to that end user. For entities with an end_user field, it sees, changes and links only that user's records, whatever a prompt says. Rate limits hold across every server.

Embed it on your site:

<script src="https://YOUR-AKTOR/embed.js" data-install="sol-…" data-token-url="/api/aktor-token" async></script>

A workspace's webhook triggers have secret URLs, shown only when they're created: in the deploy dialog and in the workspace's chat. They're never shown in the triggers list, and they stay the same across upgrades.

The widget runs in a shadow DOM, follows light and dark mode, refreshes expired tokens through your URL, and keeps the conversation across page loads. You can also call /api/v1/apps/{installId}/conversations directly (AktorApp in the SDKs is coming soon).

Put it in Slack, Microsoft Teams or Google Chat. On the solution's Integrate tab, open Chat channels and follow the guide for each, with your own bot:

  • Slack: create a Slack app from the manifest shown (it has the events URL and only the scopes needed), install it, and paste its bot token and signing secret. People mention the assistant in a channel, keep going in its thread, or send it a direct message.
  • Microsoft Teams: create an Azure Bot, paste the messaging endpoint shown, paste its App ID, tenant ID and client secret, then download the Teams app package and upload it in Teams. People mention it in a team channel (it answers in the thread) or chat with it.
  • Google Chat: turn on the Chat API in a Google Cloud project, create a service account with a JSON key, configure the Chat app with the HTTP endpoint URL shown (not as a Workspace add-on), and paste the project number and the key. People message it directly or @mention it in a space.

Each person is one of your end users, with the same limits and data access as in the widget. To post alerts from a workflow, use the Microsoft Teams or Google Chat connector.