Restricting an integration to read-only Guide
Connect a powerful app while limiting your assistant to look-but-don't-touch by enabling only its read actions.
Last updated July 16, 2026
On this page
Every integration you connect lets you choose exactly which of its actions your assistant is allowed to perform. That means you can connect a powerful app and still keep your assistant to look-but-don't-touch, enabling only the actions that read data and leaving the ones that create, change, or delete things switched off.
What read-only means here
When you connect an app, Praxivara shows you a list of that app's available actions as a checklist. This list is your allowlist: only the actions you check can ever be used by your assistant or your agents. Restricting an integration to read-only simply means checking the actions that retrieve or look up information and leaving the rest unchecked.
A read-only connection is useful when you want the assistant to reference a system — pulling contact details from your CRM, summarizing recent orders, checking a calendar — without any risk of it changing records on your behalf.
How to enable only read actions
- Open the Integrations page and find the app you want, either by searching for it by name or by filtering to its category.
- Start the connection and complete the app's sign-in or authorize step. Depending on the app, this may be a sign-in popup, a hosted connect window, or a pasted API key.
- When the list of available actions appears, do not use Select all. Instead, check only the actions that read data.
- Finish connecting. Your assistant can now use the checked actions and nothing else.
Tip: If you connected an app but left every action unchecked, the assistant won't be able to do anything with it. For a read-only setup, you still need to enable the read actions you want.
Telling reads from writes
Action names are usually the clearest signal of what an action does. Reads tend to describe fetching or looking something up, while writes describe changing the underlying data.
| Usually a read (safe to enable) | Usually a write (leave off for read-only) |
|---|---|
| Get, List, Search, Find, Fetch, Retrieve, Show, View | Create, Add, New, Update, Edit, Change, Set |
| Look up a record or contact | Send, Post, Reply, Message |
| Download or export existing data | Delete, Remove, Archive, Cancel |
When an action name is ambiguous, open the integration's capabilities view before connecting. It lists everything the app can do and lets you search within the list, so you can read each action's description and decide whether it belongs in a read-only set.
A quick sanity check
Ask yourself: "If the assistant ran this action, could it change or remove anything in the connected app?" If the answer is no, it's a read and safe to include. If you're unsure, leave it off — you can always add it later.
Adjusting the allowlist later
Your choices aren't permanent. You can tighten or loosen a connection at any time:
- Open the Integrations page and select the connected app.
- Open Manage actions to see the full checklist again.
- Uncheck any write actions you want to remove, or check additional read actions you want to allow.
- Save your changes. The new set takes effect immediately.
If your assistant ever reports that a specific action "is not enabled," that's your cue that the action is switched off in the allowlist. For a read-only connection, only turn it back on if it's genuinely a read action.
Actions versus triggers
Some apps also offer triggers — events that can start an agent automatically, such as a new order or an incoming message. Triggers are separate from actions and don't grant the assistant any ability to change data on their own. Restricting an integration to read-only is about the action allowlist; enabling a trigger simply lets an event kick off an agent, which will still be bound by whatever actions you've allowed.
Note: Connections are private to you and scoped to your workspace. Restricting an app to read-only affects only your connection — it doesn't change anything for anyone else.