Send data out with HTTP actions
Trigger external systems, sync state, or call custom services directly from the workflow.
Back to Workflow Platform
Integrations + Actions
Connect workflows to the rest of your stack
Workflows become useful when they can move data and trigger actions. Calypso gives you integration and action nodes so the workflow can read, write, notify, and hand off without leaving the canvas.
HTTP request nodeGoogle Sheets nodeWebhooksAction stepsConnected workflows
Workflow signals
HTTP
Request-based actions
Sheets
Structured updates
Webhooks
External triggers + calls
Why action nodes matter
A workflow should not stop at messaging. It should move information where it needs to go and trigger the next operational step.
Update structured records
Use nodes like Google Sheets to write data back into operational systems without extra glue code.
Keep actions in the same flow
Messages, routing, AI, and integration actions stay in one visible workflow instead of being split across tools.
What teams automate with action nodes
The strongest workflows are the ones that can both converse and act.
Lead enrichment and CRM sync
Capture a conversation outcome, enrich it, and send it to the correct destination automatically.
Ops updates and notifications
Write to shared systems, notify teams, or trigger downstream processes from the same workflow.
Custom backend workflows
Use HTTP calls to connect Calypso to internal tools or services that do not have a dedicated node.
How integrations fit the runtime
Action nodes are not add-ons. They are execution steps inside the same routing and state model.
Run as workflow steps
HTTP, Sheets, and other actions execute as nodes inside the path instead of being bolted on after the fact.
Use error-aware routing
Action nodes can be paired with error handling and next-step decisions inside the flow.
Keep context around the action
The workflow still knows what happened before and what should happen next after the action completes.
Related workflow features
Make workflows act, not just respond
Connect data, trigger systems, and move work forward without leaving the workflow canvas.