600+ pieces, one contract
A piece is GoRunner's unit of integration: the triggers and actions for one tool, wrapped in a contract that keeps someone else's API change from becoming your incident.
Built to outlive the APIs underneath
Typed at the boundary
Every trigger and action declares the shape of its payloads. Surprise fields from an upstream API become logged warnings, not broken flows.
Rate limits, absorbed
The engine tracks per-connection budgets and smooths bursts. Fan out 500 Slack messages without getting your workspace muted.
Versioned independently
Pieces upgrade per flow, by choice, with a diff of what changed. The flow you built in January still runs in December.
Tested nightly
Recorded fixtures and live sandboxes verify every piece each night. Upstream breakage should reach our changelog before your runs.
For developers: REST and webhooks
There is no SDK to learn and nothing to import. Trigger flows over HTTP, push results anywhere with a Run-finished trigger, and manage flows, connections, and runs through a clean REST API. If your stack speaks HTTP, it speaks GoRunner.
Read the API reference# start a run
curl -X POST https://api.gorunner.io/v1/flows/support-inbox-triage/runs \
-H "Authorization: Bearer $GORUNNER_KEY" \
-d '{"email_id": "msg_8d12"}'
# response, 38ms later
{"run": "#9f2k1d", "status": "completed", "duration_ms": 412 }
Missing a piece?
Tell us what you need. Popular requests usually ship within weeks, and the HTTP piece covers you in the meantime.
Ready when you say go.
Build your first flow in minutes. Free plan, no card, and the canvas is yours.
Free plan · 1,000 runs a month · self-host or cloud