Integrations
2 min read
Integrations connect Kujira to the services your team already uses. Depending on the provider, an agent can receive events, hold conversations, or act with an authorized account.
Gmail, Calendar, and Drive through a Google Cloud application.
GitHub
Repository activity, issues, and pull requests.
Telegram
Conversations through bots and private messages.
Discord
Channels, servers, and direct messages.
Slack
Channels, threads, files, and approvals.
Internal conversations through QR linking.
IMAP/SMTP
Email mailboxes compatible with IMAP and SMTP.
Webhooks
HTTP events and requests with security controls.
Accounts, channels, and scope
A connected account lets an agent act with an authorized identity. A channel defines where it receives events or has conversations. Some integrations combine both pieces.
Configure channels from each agent's profile. You can disable them without deleting their configuration or history.
Always review scope
Filters determine which events an agent receives, but do not automatically reduce the permissions of an authorized account. Connect and assign only the accounts it needs.
In messaging channels, an empty allowed-chat list blocks incoming messages. In email, an empty list does not restrict senders, and you can allow individual addresses or a whole domain (*@yourcompany.com). In an internal mailbox, anyone writing without having linked that address to their account is not treated as someone from the organization, but their conversation still belongs to the internal mailbox: it does not appear in Agent Desk. Only conversations from external channels are handled from Agent Desk.