Chat apps
Chat apps bring the events from the tools your team uses into a room's chat. A merged pull request, a failed pipeline, a new Sentry issue, a paid invoice or a new support ticket arrives as a card in the conversation, where the team can open it, turn it into a task or ask the agent about it.
The room agent sets up each app for you. Tell it which app to connect and it signs in, lets you pick the projects or sources to follow, adds the webhook and chooses a starter set of events. You check the result in the connector studio, edit what posts and how it reads, and press Go live. From then on, room owners and hosts tune the app in one editor, with no agent and no credits needed.
What you can connect
- 259 apps in 14 categories — Dev & DevOps, Monitoring & incidents, Project & work, Support, Sales & CRM, Payments & billing, Accounting, E-commerce, Marketing & email, Forms & scheduling, Analytics, Files & docs, HR & people, and Security & cloud. See All apps.
- Ready recipes — GitHub, GitLab and GitLab Self-Managed come with tested event recipes, so they connect in a few clicks.
- Every other app, and any API — the agent reads the app's own webhook or API docs and writes the recipe. The recipe is saved for your company, so every room that connects the same app reuses it. See Custom APIs.
How events arrive
- Webhook — when the app offers webhooks, events arrive the moment they happen. Qik adds the webhook for you, or shows you the address and secret to add by hand.
- Hourly sync — when the app has no webhook, Qik reads it every hour and posts what is new.
What a chat app message looks like
Each event is a card in the chat, with the app's logo as the avatar and a coloured edge that shows how it went (green for success, red for a failure, amber for a warning). A card shows a top line, a title, the details that matter and the people involved — matched room members are @mentioned and notified.
Every card has three buttons:
- Open in <App> — opens the pull request, issue, payment or ticket in the app.
- Make a task — creates a task in the room with the title and link filled in.
- Ask agent — opens the room agent with the event attached, so you can ask what it means or what to do next.
Events about the same item reply into one thread. All the updates about one pull request, one incident or one deal stay together under the first card, so the main chat stays readable.
Each event can post in one of three styles:
| Style | How it shows |
|---|---|
| Card | The full card with its details and buttons. |
| Compact | One line with the essentials and a link to the app. |
| Digest | Gathers the event into one message an hour, with a count for each kind. |
Where to find chat apps in a room
- Chat header — the room's app marks sit before Threads. Select them to see the connected apps, drafts and Add an app.
- Room settings › Chat — Connected apps, Draft apps and the Add an app gallery.
- Message ⋯ menu on any app message — Edit events for <App> (owners and hosts) and Mute <App> for me.
Who can do what
| Action | Who |
|---|---|
| Connect a new app | Company owners, admins and creators who are also the room's owner or host, with the agent switched on for the company. |
| Edit events, messages, people and delivery | Room owners and hosts. No agent and no credits needed. |
| Disconnect, connect again or delete an app | Room owners and hosts. |
| See which apps post in a room | Every room member. |
| Mute an app for themselves | Every room member. |
In this section
- Connect an app — ask the agent, sign in, pick sources, check the studio and go live.
- Edit events and messages — choose what posts, how it reads and who is mentioned.
- Custom APIs — connect any app or API from its docs.
- Company chats — company chat, department chats and the company's chat app switches.
- Plans and limits — how many chat apps each plan includes.
- Security and privacy — how keys, webhooks and app data are kept safe.
- FAQ