Glossary

The words GoRunner uses, and what they mean.

account

In Embed, one customer of the partner, with its own organization, workspaces and people inside the partner’s product.

In the API: accountId in the Partner API

action

What a step does in an app. Sending an email is an action of Gmail.

On screen: the Operation field, where an app has one

Not called: operation

AI app

ChatGPT, Claude, Cursor, VS Code, Raycast and the others, connected to GoRunner so they can build, test and run your workflows.

In the API: they connect through MCP (Model Context Protocol)

Not called: AI client, MCP client, connected application, agent

API token

A token that lets your own code use the API in one workspace, limited to the scopes you give it.

On screen: Settings › Workspace › API tokens

In the API: Authorization: Bearer grt_…

Not called: API key, PAT, access token, secret

app

A service or built-in tool you add as a step, such as Gmail, Google Sheets, HTTP Request or Code.

In the API: piece (/api/pieces, pieceId)

Not called: piece, integration, connector, node, plugin, catalog

connection

Saved sign-in details for one account of an app. Every workflow in the workspace can use it.

On screen: Works, Not working, Signed out, Not signed in, Expiring, Never tested, Not available

Not called: credential, auth, key, integration

customer

Someone who uses GoRunner inside a partner’s product. Each customer is an account there.

draft

The version of a workflow you edit. A test run runs the draft; nothing reaches production until you publish it.

On screen: Draft

In the API: the workflow’s definition (hasUnpublishedChanges says it differs from the live one). The status draft means never published.

Not called: unpublished snapshot

Embed

Putting GoRunner inside a partner’s own product, so their customers build and run workflows there.

Not called: white-label, iframe integration

expression

A value written in double braces, such as {{trigger.body.email}}, that a step reads from earlier steps.

Not called: placeholder, mustache

folder

A group of workflows in a workspace.

GoRunner Cloud

GoRunner as a service at app.gorunner.io. There is nothing to install.

Not called: SaaS, hosted version

installation

One running copy of GoRunner, with its own database, people and settings. GoRunner Cloud is one. A self-hosted installation is yours, on your own server.

Not called: instance, deployment

Keel

GoRunner’s assistant. It builds and fixes workflows from what you describe. In Embed it shows the name the partner gives it (Keel unless renamed), so the Embed pages call it “the assistant”.

Not called: GoRunner AI, the AI, AI assistant, Keel assistant

license

The right to run a self-hosted installation. It sets which features the installation has.

Not called: licence

live

The published version of a workflow, the one its trigger runs. Publishing makes the draft live.

On screen: Live, Paused

In the API: active (a workflow’s status)

Not called: armed, active

MCP

Model Context Protocol, how AI apps connect to GoRunner. Also the page in GoRunner where you connect them and see your workflow tools.

On screen: MCP, in the sidebar under Keel

In the API: /mcp/build and /mcp/tools

member

A person in a workspace, with a role there.

On screen: Members (workspace), People (organization)

In the API: user

Not called: user

organization

The company account that holds workspaces and people.

Not called: org, team, tenant, company

partner

A company that embeds GoRunner in its own product, for its customers.

partner key

The key an Embed partner’s server uses for the Partner API.

On screen: Platform › Partner keys

In the API: Authorization: Bearer gre_…

Not called: embed API key

platform admin

A person who runs a self-hosted installation from the Platform console: organizations, people, settings and the license.

On screen: Platform

provider

When GoRunner is inside another company’s product, that company. It chooses which apps and features its customers get. The Embed pages, written for that company, call it the partner.

role

What a person may do. In a workspace: Viewer, Operator, Editor or Admin. In an organization: Owner or Admin.

run

One time a workflow runs, from its trigger to its last step.

On screen: Worked, Failed, Running, Queued, Waiting, Held, Cancelled

In the API: pending, running, completed, failed, cancelled, paused, waiting

Not called: execution, job, instance

self-hosted installation

Your own copy of GoRunner, on a server you run.

Not called: instance, deployment, on-prem

step

One box on the canvas after the trigger. Each step runs one action of one app.

In the API: an action in the definition (nextAction)

Not called: node, task

Steps for

The one setting in these docs. It shows the steps for Cloud, Self-hosted or Embed.

Not called: edition switcher

template

A saved workflow that people start new workflows from.

test run

A run of the draft, started from the editor with Test. It never touches the live version.

On screen: Test

In the API: environment=test

Not called: dry run

trigger

What starts a workflow: a form someone sends, a schedule, a webhook, or a new email. A workflow has exactly one.

In the API: trigger (its type is lowercase)

Not called: event, starter, hook

variable

A named value stored on the workflow. A sensitive variable is hidden once saved.

Not called: secret, env var, constant

workflow

A trigger, then the steps it runs. Nothing runs until you publish it.

Not called: flow, automation, scenario, zap, pipeline

workspace

Where workflows, runs and connections live. An organization can have several.

Not called: project, space, environment