Flows

A Flow is an automation. In the product’s own words: it reads your source cards, thinks, and drops the result on your canvas on a schedule.

Where a Shape draws a relationship for a human to read, a Flow is a relationship that actually runs.

Before you build one

A flow needs something to read. Flows work on source cards — the live data already arriving in your workspace — so connect at least one source first. A workspace with no sources has nothing to automate.

Build a flow

1. Open Flows in the rail
2. Go to the Builder
3. Choose what it reads — the source card or cards it should look at
4. Say what it should do with what it reads
5. Set the schedule — how often it runs
6. Save it

From then on it runs on its own and puts its result on your workspace. You do not have to be in the app.

Manage the ones you have

Library lists the flows you have made. Open one to edit it, or disable it to stop it running without deleting it — useful when a flow is noisy for a week rather than wrong.

Run history shows what happened each time a flow fired.

This is the first place to look when a flow’s output is missing or looks wrong, because it answers the question that matters first: did the run happen at all? A flow that never fired and a flow that fired and produced nothing are different problems with different fixes.

Flows versus the agent versus Vlynks

Three things in Vexlynk look at your data, and it is easy to reach for the wrong one.

	When it runs	What it produces
The agent	When you ask	An answer, in conversation
A Vlynk	Continuously, in the background	Intelligence the agent uses when you ask
A Flow	On a schedule you set	A card on your workspace

Ask the agent for a one-off. Install a Vlynk when you want something watched. Build a Flow when you want a result placed on the canvas, repeatedly, without being asked.

Next

• Connecting Sources — what a flow reads from
• Vlynks — background intelligence rather than scheduled output