Docs / Reference

Glossary

The words this site and the product use, in one place. Each is the platform’s own meaning; where a word is common elsewhere with another meaning, the difference is said. What the words are for is What this platform is.

Activate — the one write in the browser: the environment’s whole draft saved as one numbered version.

Automation — a named group of scripts, connections and functions that belong together. It runs nothing itself.

App user — a person who calls your endpoints, signed in at your environment. Never a user of the platform.

Configured function (configured call) — an operation configured once and called from a script by name. Kinds: http, llm, email, text, csv, jsonmap.

Connection — where a system is and who you are to it: an address, a credential the platform attaches, and the endpoints the system reaches you on.

Dataset — a named table of records in the integration store, where bulk work stages its rows.

Debug run — a sandbox run that keeps every outbound request and every attempt’s response, for a retention window.

Draft — the working copy of an environment in your browser; Activate saves it.

Endpoint — a path on a connection that others call you on; read as a webhook, an API, an MCP server or an app.

Environment — sandbox or production, sealed off from its sibling; the only way between them is a promotion.

Grant — what makes an environment visible to a person or a token; what you are not granted answers not found.

Health — red (something is not working) or amber (something worth knowing) on an entity, latched until somebody acknowledges it.

Integration store — id mappings, small durable state and datasets, per environment, outside any run.

Library script — shared code linked into a main script, in order.

Main script — a script that runs from a trigger.

Mapping — the recorded pair of a record’s id in one system and its id in another, kept in the integration store; also the csv and jsonmap function kinds.

Operation — a named entry on an API or MCP endpoint that points at a configured function or a script.

Parameter structure — a named description of a JSON value’s shape.

Probe — one configured call fired ad hoc from the command line, with the request as sent and the far end’s own answer.

Promotion — copying entities from one environment to the other, from a plan you read first; a credential never crosses.

Run — one execution of a script, written down as it goes, continued from its last saved point after any interruption.

Sender profile — how one webhook sender proves a request is its own, held as data.

Settings script — the one script per main whose result reaches every run as input.settings.

Stepped run — a sandbox run that parks after every external call and continues on your command.

Tenant — your organisation on the installation, fully isolated from every other.

Token — a machine credential bound to one tenant and one environment, minted by a signed-in person, always expiring.

Trigger — what starts a script: a webhook, a synchronous API call, a schedule, a mailbox message, a system event, or a person.