Glossary
The words Flowmage uses, each with one meaning.
Tenancy and access
Organization
Your company in Flowmage: it holds your plan, your members and your workspaces.
Workspace
A space inside your organization where you build flows and keep the connections, tables, files and secrets they use.
Organization member
Someone who belongs to your organization, with one organization role.
Organization role
Owner, Admin or Member: what a member may do across your whole organization.
Workspace member
A member of your organization who has access to a workspace, with one workspace role there.
Workspace role
Admin or Member: what someone may do in one workspace. Organization owners and admins are admins of every workspace.
Workspace admin
Someone with the Admin role in a workspace. Only a workspace admin can change what runs on Prod.
Invitation
An email that offers someone a place in your organization, with a role and the workspaces they get. It expires after seven days.
Plan
Free or Pro: the limits your organization's workspaces get.
Environment
Test or Prod, the two places every workspace runs flows in. You build in Test, and a flow runs on Prod only once you put it there. Each keeps its own data, secret values and credentials.
Building a flow
Flow
An automation: it starts when something arrives and runs a chain of nodes.
Draft
The copy of a flow you edit. It may be unfinished; a trigger only ever starts a version.
Flow version
A numbered copy of a flow, saved when you publish. A version never changes.
Publish
Saving your draft as a new version and putting that version on Test.
Put on Prod
Making a version the one Prod runs. For a table, giving Prod the columns Test has.
Take off
Removing a flow from Test or Prod, so it no longer runs there.
Roll back
Putting an earlier version back on Test or Prod.
Node
One box on the canvas: one thing your flow does, with its own settings.
Disabled node
A node you switched off. Runs pass over it and go straight on to the node after it.
Start node
The node every flow begins at. It is on the canvas but does no work itself.
Edge
A line from one node to the node that runs next.
Port
A named exit of a node, such as true or false on a Condition, that an edge leaves from.
Output
What a node produced the last time it ran in the editor, so you can pick its fields in the nodes after it.
Pinned output
An output you froze, so the editor reuses it instead of running the node again.
Trigger sample
The input the editor gives your flow when you try it, in place of what a trigger would hand it.
Test node
Running one node on its own from the editor, for real, in Test.
Maturity
Beta or Stable: how proven an integration is. A Beta integration works, but may still change.
Stored things
Connection
The sign-in details your workspace keeps for one service, with separate ones for Test and Prod.
Secret
A named value your workspace keeps hidden, with one value for Test and one for Prod. A flow uses it by its name.
Table
Rows of data your workspace keeps, under typed columns. Test and Prod each have their own rows.
Column
One field of a table, with a fixed key and a name you can change.
Row
One entry in a table.
Schema
A named JSON document your workspace keeps. A run works on its own copy.
File
A file your workspace keeps in Test and in Prod. Each upload saves a new version of it.
Expression
The part of a field between {{ and }} that is worked out when the node runs.
Getting work in
Trigger
What starts your flows when something happens: something in a connected service, a schedule or a webhook. Several flows can be on one trigger.
Watch
A trigger that keeps an eye on one list in a connected service and says which items were added, updated or removed.
Item
One entry in a watched list, such as an employee or a task.
Check
One look a watch takes at its list. A check that finds nothing new starts nothing.
Added / Updated / Removed
What a check found about an item: new in the list, one of its watched fields different, or gone from the list.
Flow on a trigger
What links a flow to a trigger: the flow starts each time the trigger delivers to it.
Arrival
One request a trigger received, or one tick of a schedule.
Delivery
One thing a trigger hands to one flow on it. A trigger with two flows on it makes two deliveries of everything it gets.
Trigger payload
The data a trigger hands the run it starts, as the run's input.
Rejected
Said of a request a trigger turned away, such as a webhook with a wrong signature. No run was started.
Refused
Said of a delivery that could not start its run, such as when your workspace has used up its tasks.
Running
Run
One time a flow works through its nodes, from start to end.
Draft run
A run of your draft, started with Test run in the editor, in Test, without publishing a version.
Step
One node's turn in a run. A node inside a loop over three items takes three steps.
Attempt
One go at a step. A step that is retried has several attempts.
Task
What your plan counts: one attempt of one step. Each retry costs a task; a step that never ran costs none.
Retry
Flowmage trying a failed step again by itself, inside the same run.
Re-run
A new run started with the same input as an earlier run.
Queued
A run waiting for its turn, because its flow runs only a few at a time.
Running
A run Flowmage is working on now.
Sleeping
A run paused on a timer, such as a delay. It goes on by itself.
Waiting
A run that does nothing until a person or an outside system answers, or until the wait runs out.
Succeeded
A run that ended without an error.
Failed
A run that ended on an error.
Cancelled
A run that a person or Flowmage ended before it was done.
Approval
A run asking a person to choose how the flow goes on.
Decision
The option a person chose on an approval.
Retention
How long a finished run's logs and outputs are kept. Your plan sets it.
Facts and notifications
Alert rule
A rule that emails the people you pick when something happens in the flows you pick.
Incident
One stretch of an alert rule going off for one flow, from when it fires until it is resolved.
Event
Something that happened in Flowmage, such as a run that failed or a member who joined. Alert rules and event sources listen for them.
Outside the platform
Service
An outside system your flows reach or hear from, such as Stripe, AFAS or Exact.
Integration
Flowmage's support for one service: its nodes, how to connect to it, and whether it is Beta.
Fixed IP
Flowmage's own outgoing address, for a service that only accepts known addresses. A node can choose to send from it.