Skip to main content
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.
Select an app modal for the Action step

​
Two integration sources

Anyreach — native actions organized by entity:
  • Conversations — list, fetch, create, send a message into a live chat, end one
  • Phone Calls — place a single outbound call
  • Campaigns — create a campaign, load contacts in bulk, start/pause/close it, read its stats
  • Agents — list and fetch agents, create one from a website
  • Knowledge Base — search it, list its sources, crawl a URL into it
  • Custom Data — read and refresh the org tables an agent reads during a call
  • Workflows — run another workflow, and read an execution back
Anyreach native actions list
External Apps — 2,000+ third-party apps. Includes Slack, Google Sheets, Salesforce, HubSpot, Stripe, Notion, and more.
Selecting an external app in the Action step

​
When to use Action vs HTTP API

​
Adding an Action step

1

Click + below a node

The “Select next step” panel opens. Click Add Action.
2

Pick a source

The “Select an app” modal opens. Choose Anyreach for native actions or browse/search under External Apps for Pipedream integrations.
3

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.
4

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 }}.
5

Save

Click Save in the inspector to confirm the configuration.

​
What lands in ctx

After the Action step runs, its output is added to ctx under the step’s id:
Reference it downstream:

​
Examples

​
Send Slack notification

Pick Slack → Send message to channel. Fill in the channel and message text: