Seeing an integration's actions & triggers Guide

Every integration in Praxivara comes with a capabilities view that lists everything it can do. This is the fastest way to judge whether an app fits a workflow you have in mind — you can browse it before you connect, or revisit it any time afterward.

Actions vs. triggers

An integration's capabilities fall into two groups. Understanding the difference helps you read the list quickly.

• Actions are things your assistant and your agents can perform inside the app — for example, creating a record, sending a message, updating an order, or reading data. Actions run when the assistant or an agent decides to use them.
• Triggers are events that can start an agent automatically. When something happens in the connected app, a matching trigger can kick off an agent without anyone in chat. Examples include a new e-commerce order, a change to a CRM record, a bank event, or an inbound text or call.

Triggers are what let an agent run on its own. If you want a workflow to happen the moment something occurs in another tool — rather than only when you ask — look for an app that offers a trigger for that event.

Where to find the capabilities list

You can review an integration's capabilities from the Integrations hub, whether or not the app is connected yet.

1. Open the Integrations page.
2. Search for the app by name, or filter the catalog by category to narrow the list.
3. Open the integration's card to view its details.
4. Browse the listed Actions, and the Triggers where the app offers them.

Because the list can be long for feature-rich apps, use the search box within the capabilities view to jump straight to a specific operation instead of scrolling.

Using the list to decide whether an app fits

The capabilities view is meant to answer one question: can this integration do the thing you need? A few ways to get the most out of it:

Look before you connect

You don't have to link an account to see what an app supports. Browsing the actions first tells you whether it's worth connecting at all.

Search for the specific operation

If you have a concrete task in mind — "create an invoice," "add a contact," "post a message" — search the list for that word. Finding the matching action confirms the app can do it before you commit to setup.

Check whether automation is possible

If your goal is to have an agent respond automatically to events, scan the Triggers. Many apps offer actions only and have no triggers at all — that's normal, and it simply means the app can be used on request but can't start an agent by itself.

After you decide to connect

Seeing an action in the capabilities list means the app supports it — not that your assistant is already allowed to use it. When you connect an integration, you choose exactly which of its actions the assistant may perform. You can broaden or restrict that selection later from the connection's manage-actions view.

So the capabilities list and your enabled actions work together: the capabilities list shows the full range an app could do, and your per-connection selection controls what your assistant is allowed to do on your behalf.

Common questions

An app I want doesn't show the trigger I expected

Not every integration offers triggers, and those that do may not cover every event. If you don't see a trigger for a particular event, that app can still be used through its actions when you or an agent calls on it — it just can't start an agent on its own for that event.

I can't tell which action maps to my task

Use the search box in the capabilities view and try the verb for what you want done. If several actions look similar, the one whose name most closely matches your task is usually the right starting point. You can always adjust which actions are enabled after connecting.