What it does
A coworker that can’t reach your systems can only advise. One that can reach them can finish the job: find the thread, update the record, log the result. Attaching an app takes a few seconds. The part worth your attention is the second half — deciding which actions inside that app your coworker is allowed to take. Reading your inbox and sending from it are very different levels of trust, and this is where you draw that line. You can connect thousands of apps — the same catalogue the rest of CogniAgent uses, so anything your workspace has connected is already available here.When you’d use it
- Give a research coworker read-only Gmail so it can find a thread but never send from your inbox
- Let an SDR coworker create contacts in the CRM, but not delete them
- Allow a spreadsheet append so results get logged, while nothing can be overwritten
- Attach Slack so a coworker can post its finished report to the team
- Let a support coworker look up an order without touching the payment side
- Give an assistant your calendar so it can find a free slot
Attaching an app
Open App connections
Add a connection
Check what it can do
Narrow it down
The configure drawer
This is where the real control lives. Open it and you get the full list of what the app can do — Gmail alone offers twenty-one actions, from Find Emails and Create Draft to Add Label to Email, Archive Email and Download Attachment. Four things to know about it:- Select all and Select none for the broad strokes
- A search box, which you’ll want — some apps have long lists
- A switch per action, so “read but don’t send” is a real, enforceable setting
- A when to use note on each action
Use this to send the summary once the research is done.Without it, a coworker with a Slack action attached might post at the wrong moment. With it, it knows to wait.

Gmail narrowed to four actions: it can find a thread, read it and draft a reply — but not send, label, archive or delete.
Custom API calls
Sometimes the action you need isn’t on the app’s list. Custom API calls lets your coworker reach the rest of the app’s API with the same connected account, and you decide how far it may go. The setting sits near the top of the configure drawer, above the list of actions:How approvals work for these calls
- A lookup runs on its own. Reading data (a
GET) needs no approval. - Anything that changes data asks. The approval card shows the method (
POST,PATCH,DELETEand so on), the app and the address it wants to call, and the start of what it would send. You see exactly what goes out before you approve. - There’s no Always allow. One standing yes would cover every future change to any part of the app, so each call asks on its own.
- Read only means read only. With Read only, a call that would change data is refused, not asked about.
Saved custom actions
Your team can save a call as a custom action for the whole workspace. Saved ones appear in the same drawer, marked Custom, and you switch them on like any other action. One that only reads runs without asking. One that changes data asks first, and its card does offer Always allow, because that covers this one action only. To build, test and save one, see Custom actions.Good to know
Common questions
Does attaching an app give it access to everything in that account?
Does attaching an app give it access to everything in that account?
Can my coworker do something the app's actions don't cover?
Can my coworker do something the app's actions don't cover?
What if I do not see the app I need?
What if I do not see the app I need?
Can I require approval instead of blocking an action?
Can I require approval instead of blocking an action?
Does my coworker get confused with a lot of apps attached?
Does my coworker get confused with a lot of apps attached?
What happens if a connection stops working?
What happens if a connection stops working?
