The Action step runs pre-built integrations. Instead of crafting HTTP requests and managing OAuth yourself, you pick an app, pick an action, and fill in the parameters.Documentation Index
Fetch the complete documentation index at: https://docs.anyreach.ai/llms.txt
Use this file to discover all available pages before exploring further.

Two integration sources
AnyReach — native actions organized by entity:- Conversations
- Phone Calls
- Agents
- Knowledge Base
- Workflows


When to use Action vs HTTP API
| Use Action when | Use HTTP API when |
|---|---|
| The integration is available in the catalog | It’s a custom internal API |
| You want OAuth managed for you | Bearer-token auth is sufficient |
| You want a typed parameter UI | You need full control over the raw request |
Adding an Action step
Pick a source
The “Select an app” modal opens. Choose Anyreach for native actions or browse/search under External Apps for Pipedream integrations.
Authenticate (first time only)
For external apps, connecting a new app prompts OAuth. The connection is stored at the org level and reused across all workflows.
Pick an action and fill parameters
Each app exposes a list of actions (e.g., Slack → “Send message to channel”). Fill in the parameters — most fields accept expressions like
{{ ctx.input.name }}.What lands in ctx
After the Action step runs, its output is added toctx under the step’s id:
Examples
Send Slack notification
PickSlack → Send message to channel. Fill in the channel and message text:

