Connected Apps in Chat
Besides working with your Arketic data, the assistant can also reach the outside services you already use — such as Slack, Notion, Confluence, or Google. You ask in plain language, and the assistant works with the app on your behalf.
Nothing here happens quietly. Anything that sends or changes data in a connected service shows you an approval card first, and the whole capability has to be switched on by an admin before an assistant can use it at all.
What a Connected App Is
A connected app is a third-party service that has been linked to Arketic — a chat workspace, a wiki, a document store, and so on. Connections are set up outside the chat window, on the Connections page.
Once a service is connected and your admin has enabled the capability, you can simply mention it in a chat:
"What can I do with Notion?" · "Read the latest messages in that Slack channel" · "Look up that page in Confluence"
The assistant only works with services you have connected. If a service isn't connected, the assistant will tell you rather than guess.
Which Services
Which apps are available depends on what your organization has connected and what your admin has enabled. Services you may see include:
| Service | Typical use |
|---|---|
| Slack | Read a channel |
| Notion | Look up a page |
| Confluence | Find and read wiki content |
| Work with your Google account's content |
These are examples, not a complete list. To see what's actually available to you, just ask the assistant — for example "Which services am I connected to?" or "What can I do with Slack?"
How the Assistant Works With an App
When you ask for something that involves a connected service, the assistant works through it step by step:
- Finds the matching action — it looks for what can be done in your connected services that fits your request.
- Checks what the action needs — which details (a channel, a page title, a message body) must be filled in.
- Checks your connections — which services you've connected, and whether each connection is still valid or has expired.
- Runs the action — for anything that sends or changes data, only after you approve it.
You'll see the assistant's progress in the chat as it goes. See Using AI Tools for how status chips and approval cards behave in general.
The Confirmation Step
Before the assistant sends or changes anything in a connected service, an "Action Requires Approval" card appears in the chat. It reads:
"This will run an action on one of your connected third-party services on your behalf."
The card shows exactly what is about to be sent:
| Row | What it shows |
|---|---|
| Service | The connected app the action will run in — for example Slack |
| Action | The specific operation to be performed |
| What it does | A short, plain-language summary of the action |
| (one row per detail) | Every value that will be sent — the channel, the title, the message text, and so on |
Then choose:
| Button | Result |
|---|---|
| Approve | The action runs. The card switches to "Executing..." with a spinner while it works. |
| Cancel | Nothing runs. The assistant is told you declined, and you can rephrase your request. |
:::caution Read the card before you approve The card is your last checkpoint. Check the Service, the Action, and every detail row — especially anything that will be visible to other people, like a message body or a page title. If anything looks wrong, choose Cancel and ask again with clearer instructions. :::
Be specific in your request — name the channel, the page, or the recipient. The more precise you are, the more likely the confirmation card is correct on the first try.
Who Can Turn This On
Working with connected apps is off by default for every assistant. It has to be deliberately enabled — it is never available just because a service happens to be connected.
| Step | Who does it | Where |
|---|---|---|
| Connect the service | You or an admin | Connections |
| Enable the capability on an assistant | Admin | AI Assistant Configuration → the assistant's Tools step |
Until both are in place, the assistant will simply say it can't do it.
Different assistants can be set up differently. One assistant may be allowed to work with connected apps while another isn't — so the same request can succeed in one chat and be declined in another.
What to Expect
- Looking things up is the everyday use — reading a channel, finding a page, pulling in content you need for an answer.
- Anything that sends or changes data always goes through the approval card first. There is no way for the assistant to send or change something in a connected service without you clicking Approve.
- Availability can change. Your admin can enable or disable this per assistant at any time, and a connection can expire and need to be re-authorized.
Troubleshooting
| Problem | What to do |
|---|---|
| The assistant says it can't work with your apps | The capability is probably not enabled on this assistant. Ask your admin, or try another assistant. |
| The assistant says a service isn't connected | Set it up on the Connections page, then ask again. |
| The assistant says a connection is expired | The link to that service needs to be re-authorized on the Connections page. |
| The approval card shows the wrong details | Choose Cancel, then rephrase your request with the exact channel, page, or wording you want. |
| The action failed after you approved it | Read the message in the chat — it usually explains what the service rejected. Correct the details and ask again. |
Related Pages
- Using AI Tools — approval cards and status chips across all actions
- Starting a Chat — the chat window and its toolbar
- Connections — connecting accounts and credentials
- AI Assistant Configuration — enabling actions on an assistant (admin)