Adding or removing enabled actions later Guide

When you connect an app, you choose exactly which of its actions your assistant is allowed to perform. That choice isn't permanent — you can revisit it at any time to grant new actions or take some away. This article shows how to change an app's enabled actions after it's already connected.

Why you'd change enabled actions

The set of actions you enable acts as an allowlist for a connection. It controls what the assistant and your agents can do with that app on your behalf. Common reasons to revisit it:

• The assistant asked for an action that isn't turned on yet, and you want to enable it.
• You started with read-only access and now want to allow the assistant to make changes.
• You'd like to tighten a connection back down — for example, remove write actions and keep only the ones you use.
• You connected an app but left every action unchecked, so nothing is working yet.

Tip: Enabling more actions doesn't force the assistant to use them — it only widens what it's permitted to do when a task calls for it. Keep the list scoped to what you actually trust for that app.

Open Manage actions

1. Go to the Integrations page.
2. Find the app you want to adjust. Apps you've already connected are marked as connected, so they're easy to spot.
3. Open that integration to view its connection details.
4. Open Manage actions for the connection. This shows the full list of the app's available actions as checkboxes, with a Select all option.

Add or remove actions

1. Review the list of available actions. If the app is a large one, use the search within the list to jump to a specific operation.
2. To add an action, check the box next to it. To enable everything the app offers, use Select all.
3. To remove an action, uncheck its box. The assistant and your agents will no longer be able to perform it through this connection.
4. Save your changes. The updated set of actions takes effect for future requests.

Enabling a single action the assistant needs

If the assistant tells you an action "is not enabled" and points you to Manage actions, you don't need to turn on everything. Open Manage actions, check the one action it named, and save. The assistant can then complete that step the next time you ask.

Restricting an app to read-only

If you'd like the assistant to look but not change anything, keep the actions that read or fetch information and clear the ones that create, update, send, or delete. Action names usually make their intent clear. When in doubt, enable a smaller set first — you can always come back and add more.

Actions vs. triggers

Enabled actions control what the assistant and your agents can do in an app. Some apps also offer triggers — events that can start an agent automatically, such as a new order or an inbound message. Triggers are managed separately as part of an agent's setup and aren't part of the Manage actions list. If you're trying to make an agent run on its own, you're looking for a trigger, not an action.

Good to know

• Enabled actions are set per connection, so each connected app has its own allowlist.
• Your connections and their action settings are private to you and scoped to your workspace.
• Removing an action takes effect going forward; it doesn't undo work the assistant already completed.
• If an app supports connecting more than one account, review the enabled actions for each connection you care about.