Docs / Strand / getting-started/first-workflow

Deploy your first workflow

The fastest way to a working workflow is to start from a template rather than an empty canvas. Templates arrive pre-wired — nodes, connections, and sensible defaults — so you can see a complete pipeline before you change anything.

Start from a template

1. Open Flows and click Templates in the toolbar above the list.
2. Pick a template that resembles what you want. Each one describes the trigger it

expects and the services it touches.

3. Give the workflow a name and create it. You land in the

workflow editor with the template already laid out.

Templates are a starting point, not a contract — every node stays editable. See Templates for the full catalogue.

Build from scratch instead

If no template fits, create an empty workflow and add nodes yourself. The two pages worth reading first:

• Creating workflows — the canvas, adding

nodes, and saving

• Connecting nodes — how execution flows from

one node to the next

What a workflow is made of

Every workflow is a graph of nodes. A minimal one looks like this:

[Trigger] → [Transform] → [HTTP Request]

• Nodes are the steps. See Node types for what is available.
• Connectors hold credentials for external services so nodes can reuse them without

embedding secrets. See Connectors.

• Templating moves data between steps — see

Templating overview.

Secrets never belong in node configuration. Put them in the Vault and reference them.

If you get stuck building it

Nothing here can fail at runtime — a workflow does nothing until it runs — so problems at this stage are editor-shaped rather than error-shaped:

• Nodes won't connect, or a connection is refused — see

Connecting nodes; outputs and inputs have to be compatible.

• You can't find the node you need — Node types lists everything

available.

• A node needs credentials — those live in Connectors, not

in the node itself.

Errors that appear once a workflow actually executes are covered in When a run fails.

Next

Once the workflow is saved, trigger a test run to watch it execute end to end.

← Back to Strand docs