Glossary

For the main ideas explained together, see Core concepts.

Agent. An AI assistant with instructions, tools and knowledge. Built in the full Designer view. In my.studio it’s called the Assistant. See Agents.

AI Agent step. A step that sends a prompt to one of your agents and passes its answer to the next step.

API endpoint. The URL every automation gets automatically, so code can run it with a POST and your tenant API key. Shown at the top of Trigger Management. See Triggers.

API key. A secret that lets your code call work.studio. Organization (tenant) keys start svx_tk_, customer keys start svx_ck_. Send one in the X-API-Key header. See API keys.

App. Connectors and automations packaged so your customers can turn them on. Built under Distribute › Apps. See Apps and customers.

Approval. A step that waits for a person to decide. Web buttons: Approve and Reject. Mobile buttons: Approve and Decline. See Approvals.

Automation. Steps that run when a trigger fires. The API and some labels call it a workflow.

Automation Plan. A layout of every automation a piece of work needs, made before any is built. See Describe it and let Flow build it.

Condition. A step that sends the run down the first branch whose rule matches.

Connection. Your signed-in access to a connector, such as your company’s Salesforce account. See Connections.

Connector. The definition of one outside system and the operations it offers. Listed under Setup › Connectors.

Cron expression. The text that sets a Schedule trigger’s times, such as 0 0 9 ? * MON-FRI. See Triggers.

Customer. A company or person using your apps. Some screens call this a scope.

Draft. The version of an automation you’re editing. Tests run the draft. The toolbar shows Draft v1, Draft v2 and so on.

Edited. Shown next to Live when the draft has changes that aren’t published yet.

Embed. The way your customers use your integrations and automations inside your own product. See Embed.

Environment. A separate space inside your organization, such as production or staging. Picked in the top bar.

Expression. A value in double braces, such as {{input.email}}, that’s filled in during a run. See Expressions.

Flow. The app where builders create automations, at flow.work.studio.

Full Designer view. Flow with every area shown, at designer.work.studio. Opened with Open full Designer.

Function step. A step that runs JavaScript you write.

Guardrail. A rule that checks what goes into and comes out of AI steps. In my.studio the page is Shield. See Guardrails.

Human Task. The settings panel for a step that asks a person something: an approval, a choice, some text or a form.

Knowledge base. Content an agent searches to answer questions. Flow’s area for it is Knowledge. See Knowledge.

Live. The published version, the one real runs use. The toolbar shows Live v1, Live v2 and so on.

Logs. The Flow page that lists runs and their status. In the full Designer view it’s called Runs & Logs. See Runs and logs.

my.studio. The app for everyone in your organization to ask the assistant, answer approvals and use automations, at my.work.studio. See my.studio.

Organization. The company account you sign in to.

Publish. Freezes the current draft as the live version and opens a new draft for later edits.

Run. One time an automation runs. See Run status.

Run status. Queued, Running, Waiting (for a person), Paused, Finished, Failed, Cancelled or Terminated.

Schedule. A trigger that runs an automation at set times.

Shield. The my.studio page with your guardrail settings.

Step. One unit of work in an automation. See Steps.

Step name. The label a step gets when you add it, such as FUNCTION_1. Expressions use it to read the step’s output.

Task. A piece of work assigned to a person. Approvals reach people as tasks.

Test. Runs the saved draft from the editor’s test panel, without publishing.

Test Customer. In the test panel, the customer whose connections a test uses. Leave it as Environment Default unless the automation uses customers’ connections.

Trigger. What starts an automation. See Triggers.

Version History. The list of an automation’s versions, with the changes in each and Revert to this version.

Webhook. A URL another system calls to start an automation. You get one by adding a Webhook trigger. See Incoming webhooks.

Workflow. The API’s word for an automation. It also appears in a few labels, such as the Sub-Workflow step.