Glossary

Loopfour terms in plain words, in alphabetical order. Each entry gives what the term means, what it is like in accounting, where you see it in Studio, and the word your developer may use.

A

Active

A workflow that has been deployed. Its trigger can start it, and you can press Run.

In Studio: the Active filter under Workflows > My workflows.

AI Agent step

A step that reads text or a document and returns the fields you ask for, or sorts items into groups you name.

Like in accounting: a clerk who keys in a bill's details for you to check. In Studio: AI Agent, under AI in the editor's block list. Developers say: agent block. See Where Loopfour uses AI.

API key

A developer tool: a key that lets another program use Loopfour on your company's behalf.

In Studio: Settings > API keys. See Authentication and API keys.

Approval

A pause where a named person approves or rejects before the workflow continues.

Like in accounting: sign-off on a payment run. In Studio: Approvals in the sidebar, and the Approval step in the editor. Developers say: approval block. See Approvals.

Archived

A workflow that has been put away. It cannot run. If you unarchive it, it comes back as a draft and needs deploying again.

In Studio: the Archived filter under Workflows > My workflows.

Audit trail

The company-wide record of who did what and when, such as runs started, workflows changed, files downloaded and systems connected.

Like in accounting: the audit log your auditors ask for. In Studio: Runs > Audit trail. Developers say: audit log. See Audit trail.

B

Block

How the editor shows a step on the canvas. See Step.

Browser step

A step that works in a web portal for you, such as a customer's payment portal, following plain-language instructions.

In Studio: under Browser Automation in the editor's block list. See Work in a web portal.

C

Chat

Where you ask Loopfour to build or explain something.

Like in accounting: asking a colleague who knows the system. In Studio: Home, and the AI Chat button at the top of other pages. Developers say: Copilot. See Chat.

Condition

A yes or no check that decides which path a workflow takes.

Like in accounting: a threshold test, such as an approval limit. In Studio: the Condition step. Developers say: condition block. See Make a decision.

Connection

Loopfour's saved, authorised access to one of your systems.

Like in accounting: a user login set up once for a system. In Studio: Integrations, where a connected system shows a status such as Connected, Expired or Error. See Connect a system.

D

Dashboard

Charts and tables built on your tables, arranged on one board.

Like in accounting: a management report pack. In Studio: Dashboards. Developers say: dashboard, widget. See Dashboards.

Deploy

Make the current version of a workflow live so its trigger can start it.

Like in accounting: moving a procedure from draft to approved. In Studio: the Deploy button in the editor's top bar. Developers say: deploy, version. See Deploy, test and change a workflow.

Draft

A workflow that is not live yet. Its trigger does not start it, and Run does not run it.

Like in accounting: a working draft. In Studio: the Draft filter under Workflows > My workflows.

F

File

A document a workflow reads or produces, such as a vendor bill as a PDF.

Like in accounting: source documents and support. In Studio: Files. Developers say: workspace file. See Files.

I

Inbound email

A trigger that starts a workflow when an email arrives at the workflow's own address. Useful for bills and remittances.

In Studio: the Inbound Email trigger. See Start a workflow when an email arrives.

Integration

A system Loopfour can connect to, such as your ledger, your bank or your CRM.

Like in accounting: a system in your finance stack. In Studio: Integrations. Developers say: provider. See Connect your systems.

L

Loop

A step that repeats the steps inside it for each item in a list, such as each invoice.

In Studio: the Loop step. See Repeat for each item, or do several things at once.

M

MCP

A developer tool that lets an AI assistant, such as Claude Code or Codex, work with your Loopfour workflows. An owner or admin switches it on.

In Studio: Settings > MCP. See MCP.

N

Needs attention

The runs that need a person: failed runs and runs waiting for approval.

In Studio: Runs > Needs attention. See Runs.

P

Parallel

A step that runs several branches side by side, when they do not depend on each other.

In Studio: the Parallel step. See Repeat for each item, or do several things at once.

Paused

A deployed workflow that has been taken offline. It keeps its setup but does not run until it is deployed again.

In Studio: the Paused filter under Workflows > My workflows.

Placeholder

A field in a step's settings that Loopfour fills in from an earlier step when the workflow runs.

Like in accounting: a mail-merge field in a letter template. Developers say: variable reference. See Use results from earlier steps.

R

Recipe

A guided setup view on some templates, where you choose which of your systems each part of the template uses.

In Studio: the Recipe view in a template's details, next to Flow. See Start from a template.

Role

What a person can do in your company's Loopfour. Each person is an Owner, Admin or Member.

In Studio: Settings > Team. See Team and access.

Run

One time a workflow ran, with a record of each step: what it received and what it produced.

Like in accounting: one processed batch with its support attached. In Studio: Runs. Developers say: run, execution. See Runs.

Run status

Where a run stands. Studio shows Queued, Running, Pausing, Paused, Waiting for approval, Completed, Failed or Stopped.

In Studio: the status on each run in Runs. See Runs.

S

Schedule

A trigger that starts a workflow at set times, such as every weekday morning or on the first of each month.

In Studio: the Schedule trigger. See Run a workflow on a schedule.

Secret

A developer tool: a password or key saved in Loopfour so steps can use it without showing it.

In Studio: Settings > Secrets, and Secrets in a workflow's menu in the editor. See Variable references.

Step

One action in a workflow, such as "create the invoice". The editor shows each step as a block.

Like in accounting: one line of the checklist. In Studio: the blocks on the editor's canvas. Developers say: block, step. See Steps: what a workflow can do.

Sub-Workflow

A step that runs another workflow as part of this one, so you can reuse a shared procedure.

In Studio: the Sub-Workflow step. See Reuse one workflow inside another.

T

Table

Rows of working data kept in Loopfour, which workflows can read and write.

Like in accounting: a schedule or listing that supports a balance. In Studio: Tables. Developers say: data table. See Tables.

Template

A ready-made workflow you copy and adjust.

Like in accounting: a standard working paper you roll forward. In Studio: Workflows > Templates. Developers say: system template. See Start from a template.

Transform

A step that reshapes data from one system's format into another's.

In Studio: the Transform step. See Reshape data between systems.

Trigger

What starts a workflow: a time, an email, a change in a connected system, or you pressing Run. Each workflow has one trigger.

Like in accounting: the event that starts a procedure, such as a bill arriving. In Studio: the first block on the canvas, chosen from Triggers in the block list. See Choose when a workflow runs.

V

Version

A saved, numbered state of a workflow. Each deploy makes the current version live.

In Studio: Current Version in the Deploy Workflow dialog, and Deployment history in the editor's top bar. See Deploy, test and change a workflow.

W

Wait

A step that pauses the workflow for a set time before it continues.

In Studio: the Wait step. See Wait before continuing.

Webhook

A developer tool: a way for another system to tell Loopfour that something happened, so a workflow can start.

See Webhook trigger.

Workflow

A saved set of steps Loopfour follows the same way each time.

Like in accounting: a written procedure for a recurring task. In Studio: Workflows. Developers say: workflow definition. See Workflows.