Skip to content

Read less, ship more

The docs are organized around what you are trying to do, written by the people who built the thing, and kept short on purpose.

REST + webhooks · no SDK required, none planned

request

curl -X POST https://api.gorunner.io/v1/flows/
  support-inbox-triage/runs \
  -H "Authorization: Bearer $GORUNNER_KEY" \
  -d '{"payload": {"from": "kai@acme.com"}}'

response200 · 412ms

{
  "id": "#9f2k1d",
  "flow": "support-inbox-triage",
  "status": "completed",
  "duration_ms": 412,
  "steps": 5
}
5 minQuickstartConnect two pieces and deploy your first flow in five minutes.
core · soonConceptsFlows, pieces, runs, connections, versions: the six words that explain everything else.
v1 · soonREST APITrigger runs, manage flows, and read history over HTTP. No SDK required, none planned.
events · soonWebhooksInbound webhook triggers, resume tokens for paused runs, and the Run-finished trigger for pushing results out.
copilot · soonGoRunner AIPrompting patterns for building and editing flows, and how drafts and reviews work.
ops · soonSelf-hostingThe binaries, Docker images, upgrades, backups, and air-gapped license keys.

docs / quickstart

Your first flow in five minutes

This walkthrough builds the classic: new Stripe payment, short Slack message. You will need a GoRunner account and admin access to a Slack workspace.

1. Connect Stripe and Slack

In the dashboard, open Connections, choose Stripe, and paste a restricted API key. Repeat for Slack with the OAuth prompt. Both connections are workspace-wide: every flow can use them.

2. Describe the flow

Press ⌘K and type what you want:

When a Stripe payment succeeds, post the amount and customer email to #revenue.

GoRunner AI assembles the two steps and shows you the draft. Check the field mapping, then deploy.

3. Test it for real

Use Stripe's test mode to fire a payment. The run appears in Runs within a second, with each step's input and output recorded. That is the whole loop: describe, deploy, verify.

Where next

Add a branch for large payments, a daily digest version on a schedule, or an approval step before refunds. All three are one sentence each in the copilot.