Choosing which actions the assistant can perform Guide

When you connect an app, you decide exactly which of its actions the assistant is allowed to take. This per-connection allowlist lets you link even a powerful tool while keeping the assistant limited to only the actions you trust — for example, read-only access, or just the few operations you actually need.

Why the allowlist matters

Some apps expose dozens or hundreds of possible actions, and not all of them are ones you want an assistant performing on your behalf. Rather than granting everything at once, Praxivara lets you turn on individual actions one at a time.

This gives you a simple way to stay in control: connect a CRM but allow only the assistant to look up records, connect an accounting tool but allow only reading reports, or connect a store and enable a specific handful of operations you rely on.

Tip: If you're unsure, start narrow. You can always add more actions later once you've seen how the assistant uses the connection.

Choose actions while connecting

As you connect an app, you'll see its available actions presented as a checklist:

1. Begin connecting the app from the Integrations hub and complete the app's sign-in or setup step.
2. Review the list of available actions shown for that connection.
3. Use Select all to enable everything, or check only the specific actions you want the assistant to be able to perform.
4. Confirm to finish. The actions you selected become available to the assistant in chat and to your agents.

If you leave every action unchecked, the connection is linked but the assistant won't be able to do anything with it — so be sure to enable at least the actions you need.

Change allowed actions later

You can revisit your choices at any time:

1. Go to the Integrations hub and open the connected app.
2. Open Manage actions for that connection.
3. Check additional actions to enable them, or uncheck actions to remove them.
4. Save your changes.

Your selections apply to that specific connection and stay in effect until you change them.

Enable a single action the assistant asked for

Sometimes the assistant will tell you a particular action isn't enabled and point you to manage the connection. When that happens, open Manage actions for the app, turn on the one action it mentioned, and save. The assistant can then complete the task on your next request.

Restricting the assistant to read-only

If your goal is to let the assistant look things up without making any changes, enable only the actions that retrieve or view information and leave out the ones that create, update, or send. Action names generally describe what they do, so you can pick the read-style operations and skip anything that writes or modifies data. When in doubt, enable a small set and confirm the behavior before adding more.

Actions vs. triggers

It's worth knowing the difference between the two kinds of capabilities an app can offer:

• Actions are things the assistant or your agents perform — the items you turn on in the allowlist.
• Triggers, where an app supports them, are events that can automatically start an agent (for example, a new order or an inbound message). Not every app offers triggers.

The allowlist covers actions. Triggers are managed separately when you set up an agent to run automatically.

Common questions

The assistant says an action "is not enabled"

That action simply hasn't been turned on for the connection yet. Open Manage actions, enable it, and save.

I connected an app but nothing works

Check that at least one action is enabled. A connection with every action left unchecked is linked but can't do anything until you turn actions on.

Do my choices affect other people?

Your connections and their allowed actions are private to you and scoped to your workspace, so your selections don't change anyone else's setup.