Actions

Open Settings → Actions.

What this tab is for

Actions at account level are connections to external systems: credentials, base URLs, and tests. Individual agents still choose which actions are enabled and how they behave under Agents → Actions; this screen is where shared connections live.

Provider connections

The UI lists available providers (for example e-commerce or integrations your plan includes). For each provider you can:

• Configure API keys, OAuth, shop/domain identifiers, or other auth types the form exposes.
• Test the connection when supported.
• Remove or rotate credentials according to your security process.

Exact fields depend on the provider.

Custom HTTP actions

You can define custom HTTP actions with:

• Method, path, query parameters, and headers
• Body types: none, JSON, form-encoded, or raw
• Authentication: none, API key (header or query), Bearer, Basic, or custom header
• Timeouts and test requests against your endpoint

Use this when you need a bespoke API that is not shipped as a named provider.

Relationship to Agents → Actions

• Settings → Actions: shared connections and custom HTTP definitions.
• Agents → Actions: enable actions for that agent, map parameters, and use the Playground to verify.

If a connection fails, fix it here first, then re-test from the agent.