Connecting apps with an API key (Firecrawl, IPinfo, Twilio) Guide

Most apps in Praxivara connect through a sign-in popup or a hosted connect window. A few connect a little differently: you paste an API key or account credentials directly. Firecrawl, IPinfo, and Twilio work this way. This article walks you through those connections and how to manage them.

Before you start

Key-based apps ask you to copy a credential from the provider's own dashboard and paste it into Praxivara. Have the provider's site open in another tab so you can find and copy the right value.

• Firecrawl — an API key, which typically begins with fc-.
• IPinfo — an access token from your IPinfo account.
• Twilio — your Account SID and Auth Token, both found in the Twilio Console.

Your connections are private to you and scoped to your workspace. Credentials you paste are used only to let the assistant and your agents act in that app on your behalf.

Connect a key-based app

1. Open the Integrations hub from your account.
2. Search for the app by name, or filter by category, and open its card.
3. Click Connect. For these apps you'll see fields for an API key or credentials rather than a sign-in popup.
4. Paste the required value or values (for Twilio, both the Account SID and the Auth Token).
5. Confirm to save the connection. Praxivara validates the credential with the provider before finishing.
6. Return to the hub and confirm the app now shows as Connected.

Choose which actions the assistant can perform

When you connect an app, you decide exactly which of its actions the assistant is allowed to take. Actions appear as a checklist, with a Select all option.

1. Review the list of available actions for the app.
2. Check only the actions you want to enable, or select all of them.
3. Save. The assistant and your agents can now use the actions you enabled — and only those.

You can revisit this at any time. Open the connection and use Manage actions to add or remove enabled actions later.

If the assistant tells you an action "is not enabled," open the connection, go to Manage actions, and turn that action on.

A note on triggers

Some apps can also start an agent automatically when something happens — for example, an inbound Twilio SMS or call. These are called triggers, and they're separate from actions. You can review an app's actions and any available triggers on its capabilities view before you commit to connecting.

Troubleshooting

"Couldn't validate" your key or credentials

Double-check that you copied the full value with no extra spaces, and that it comes from the correct account. For Firecrawl, confirm the key begins with fc-. For Twilio, make sure the Account SID and Auth Token are paired from the same account.

The connection didn't save

Confirm the credential is still active in the provider's dashboard. Keys that were revoked or regenerated on the provider's side will no longer validate — generate a fresh one and paste it in.

Nothing happens after connecting

If you connected the app but left every action unchecked, the assistant has nothing it's allowed to do. Open the connection, choose the actions you want, and save.

Update or reconnect later

If you rotate a key in the provider's dashboard, update it in Praxivara by reconnecting the app and pasting the new value. From the connection you can also disconnect the app entirely when you no longer need it. Your enabled actions are preserved with the connection, so you won't need to reselect them unless you choose to.