Buy

Workflows

Free & Premium

Workflows are local flows built from nodes: a trigger starts them, the steps run on this Mac. A workflow might call a site every 15 minutes and tell you when it does not answer, or build your project as soon as a file changes. Nothing runs in the cloud. Workflows are a beta feature, in the sidebar the entry carries the Beta badge.

What you do here

Page layout

Part Content
List every workflow in a table with Import and New workflow. It appears when you open Tools › Workflows
Editor the canvas of one workflow with head line, toolbar and the form of the selected node. It opens with a click on a workflow
Runs the panel below the editor with the tabs History and Memory

How to start

  1. Open Tools › Workflows and click New workflow.
  2. Choose a template, for example Check a site and report, or Empty workflow.
  3. Choose a trigger in the editor and attach further nodes with Next step.
  4. Fill in the fields of every node. The note in a template says what you have to enter.
  5. Click Run and check in the Runs panel what every step received and emitted.
  6. Switch the workflow on with the On switch. From then on its triggers start it.

⌘K finds every workflow with Run workflow: … and starts it from there.

What happens in the background

  • The steps run in the app. Schedule, webhook and file change only fire while WebDonkey is open. A date that passed while the app was closed is caught up once at the next start.
  • A webhook trigger only listens on 127.0.0.1, so only for programs on this Mac.
  • Workflows, the shared variables and the memory travel along in the app backup in the Workflows category. The run history stays on this Mac.
  • With wd workflows you list, start and switch workflows from the terminal too, see More tools.

Free and Premium

Free Premium
Workflows 3 any number
Runs kept per workflow the last 20 up to 200
Triggers Manual start, Schedule, Webhook plus App event and File change
Nodes requests, commands, files, notifications, logic and data plus Only new, Remember value, Run code, Send mail, Database query, Control service, Control site, Remote command and AI prompt

You can always look at, edit, save, export and delete any workflow. Switching it on and running it only works if it is within the Free limit and has no Premium nodes. Prices are at webdonkey.io/pricing.

The list Free & Premium

On Tools › Workflows you see every workflow in a table: what starts it, when it last ran, when it is due next and whether it is on. From here you create new ones, from templates too, and import and export them.

Where to find it

Sidebar Tools › Workflows. From the editor, All workflows takes you back.

How to do it

Create a workflow

  1. Click New workflow. The dialog New workflow opens.
  2. Choose Empty workflow (empty canvas, then choose a trigger) or a template.
  3. The editor opens with the new workflow. It is switched off.

While there is no workflow yet, the page shows Build your first workflow with the same choices.

The templates

Template Does Needs
Check a site and report calls a site every 15 minutes and tells you when it does not answer Free
Deploy on a webhook a local webhook takes the deploy signal and runs your commands in the site's folder Free
Nightly database dump writes a dump of one database every night at 3 and reports back Free
Summarise incoming test mail sums up an arriving test mail in two sentences with the local AI Premium
Build when files change watches a folder and starts your build as soon as a file in it changes Premium

Every template has a note saying what you have to enter, mostly under Variables (such as site_url or site_dir). On the Free plan a Premium template opens the dialog The template “…” needs Premium with the nodes concerned instead.

Run, switch on, duplicate, export, delete

  • Run (play button in the row if there is room, or the row's menu): starts the workflow through its manual start, otherwise through its first trigger. If the manual start has input fields, the editor opens and asks for them. Without a trigger the list says “…” has no trigger that could start it.
  • Status: the On or Off switch turns the triggers on or off.
  • Duplicate: creates a switched-off copy "… (copy)".
  • Export: saves the workflow as a JSON file. Variables of this workflow travel along, secrets never.
  • Import (at the top): reads such a file. The workflow arrives switched off.
  • Delete: asks Delete workflow? and removes the workflow together with its runs and its memory. This cannot be undone.

The row's menu has Open, Run, Duplicate, Export and Delete. A click on the name opens the workflow in the editor.

Fields and options

Column Shows
Workflow name, below it the description, a lock note or the badge Imported
Triggers the triggers, as icons when space is tight. No trigger if there is none
Last run status of the last run (Running, Succeeded, Failed, Cancelled) and when, or Never run
Next run time and distance of the next scheduled run, otherwise a dash
Status the On or Off switch

In a narrow window the list hides Triggers and Next run. At the top stand the counters Total, On and, where needed, Locked. On the Free plan a counter shows how many of the 3 free workflows you use.

Lock notes below the name

Note Meaning
Needs Premium: … the workflow has Premium nodes, which are named
Past the Free limit the workflow is above the limit of 3 workflows

Checking imported workflows

An imported workflow runs with your rights. That is why it carries the badge Imported until you switch it on or run it for the first time. Before that, the dialog Check the imported workflow shows what it does on this Mac:

  • Runs commands
  • Writes files
  • Goes online

If it does none of these, it says It runs no commands, writes no files and does not go online. Look at it opens it in the editor, Switch on or Run confirms. Look at foreign workflows before you switch them on.

Free and Premium

  • On the Free plan you have 3 workflows. At the limit, New workflow opens the dialog Free limit reached.
  • If you have more workflows than allowed, after a downgrade for example, the 3 oldest stay active. The others show Past the Free limit: looking, editing, exporting and deleting still work, switching on and running only with Premium again.
  • A workflow with Premium nodes can be saved on Free but not switched on or run.

Troubleshooting

What you see Why What you do
This is not a workflow file. The chosen file is not a workflow export Choose a file made with Export
The workflow in this file cannot be used. The workflow is broken or comes from a newer version Read the details below the message, update WebDonkey
The switch will not turn on, a Premium dialog opens Free limit or Premium nodes Read the dialog: it names the limit or the nodes
A workflow does not start on schedule It is off, or WebDonkey was closed at the time Switch it on. A missed date is caught up once at the next start

See also

The editor Free & Premium

In the editor you build a workflow on a canvas: place nodes, connect them with lines, fill in their fields. At the top you save, switch on and run, at the bottom the Runs panel shows what happened.

Where to find it

Sidebar Tools › Workflows, then click a workflow or choose Open in the row's menu. A new workflow opens straight in the editor.

How to do it

  1. For an empty workflow, choose a trigger under Choose a trigger, such as Schedule.
  2. Click Next step below the node and choose the next node, such as HTTP request. It is attached and already connected.
  3. Click the node. Its form opens on the right, fill in the fields.
  4. Repeat for further steps.
  5. Click Run. The editor saves first if needed and starts a run.
  6. Check in the Runs panel what every step emitted, and switch the workflow on with On.

Fields and options

The head line

Element Meaning
All workflows back to the list. With unsaved changes the editor asks with Save, Discard changes and Back to it
Workflow name the name. Without a name it cannot be saved
Unsaved changes badge while something is not saved
On / Off switch on: the triggers start the workflow. off: it only runs when you press Run. The switch takes effect at once
Save saves the workflow (⌘S)
Run starts a run now through the manual start, otherwise through the first trigger, and saves first if needed. While the run is under way, the button reads Stop
Settings opens Workflow settings
More Duplicate, Export … and Delete workflow

If the manual start has input fields, Run asks for them in the dialog Run workflow.

The canvas

Element Meaning
Add step opens the node picker with Search nodes. The new node goes after the selected one
Next step below every node, attaches right after it
Add note puts a note on the canvas, double-click to write. It is not run and cannot be connected
Undo (⌘Z), Redo (⇧⌘Z) takes changes to the canvas back or redoes them
Variables opens Variables and secrets
Zoom out, Zoom in, Fit to window zoom. Fit to window shows the whole flow
Overview the minimap of the whole flow, when the window is wide enough

The node picker is sorted by Triggers, Logic, Data, Input / output, WebDonkey, AI and Canvas. On the Free plan Premium nodes carry a lock. If you pick one, a dialog explains what Premium covers instead of placing the node. With Hide Premium features switched on (Settings › Navigation), they are missing from the picker.

Connect, move, delete

  • Connect: drag from an output of a node to the input of another. If you let go over empty canvas, the picker asks what should follow there.
  • Several outputs: If has "true" and "false", Switch has one output per rule and "otherwise". With Use the error output in a node's settings, an Error output is added.
  • Move: drag nodes with the mouse.
  • Duplicate: ⌘D duplicates the selected nodes. In the form, Duplicate node does the same.
  • Delete: click a node or line, then Backspace or Delete. In the form, Delete node does the same.

As long as you have not moved or zoomed anything, the canvas fits itself to the window size. After that your zoom stays until you click Fit to window.

A node's form

A click on a node opens its form on the right. At the top sit Duplicate node, Delete node and Close, below that its fields and at the bottom the node's settings. Long hints unfold with Show more. In fields that take expressions, Insert field helps. You drag the form's width at its left edge, a double-click there restores the standard width.

On the node itself, marks show whether it is switched off, how its last run went and whether it needs Premium.

What happens in the background

On saving, WebDonkey checks the flow and marks what is wrong:

  • The workflow needs a name.
  • This node needs a name. or a duplicate node name
  • an empty required field (“…” is required.). WebDonkey skips switched-off nodes here
  • a connection to a node that no longer exists, a duplicate connection or a connection from an output the node does not have
  • A trigger cannot receive a connection. and A note cannot be connected.
  • The connections form a circle.

The On switch and Run check the Free limit and Premium nodes first.

Troubleshooting

What you see Why What you do
Add a trigger first: a run starts there. The workflow has no trigger Choose a trigger
This node needs Premium. The workflow can be saved, but not switched on or run. A Premium node on the Free plan Replace the node or activate Premium
This version of WebDonkey does not know this kind of node. The workflow comes from a newer version Update WebDonkey
A question when opening another workflow The current one has unsaved changes Save or Discard changes

See also

The nodes Free & Premium

Every node is a step. It receives items from the node before it, works on them and hands items on. In the picker the nodes are sorted by Triggers, Logic, Data, Input / output, WebDonkey, AI and Canvas. A step may hand on 10,000 items at most.

Where to find it

In the editor through Add step or Next step. Search nodes finds nodes by their name. Every field of a node has a short hint in the form, long hints unfold with Show more.

How to do it

Check a site every 15 minutes and report a failure:

  1. Trigger Schedule with */15 * * * *.
  2. HTTP request with the site's URL, such as {{ vars.site_url }}, Fail on an HTTP error status off.
  3. If with the condition {{ json.status }} less than 400.
  4. At the "false" output a Notification with the title "Site not reachable".

The template Check a site and report is exactly this flow.

Triggers

A workflow starts at a trigger. No connection leads into a trigger.

Node Does Important fields
Manual start starts through Run in the app, through ⌘K or with wd workflows run Input fields (type Text, Number or Yes / no, with Default). They are asked for at the start and arrive as fields of the first item
Schedule starts on a cron expression in local time: minute, hour, day, month, weekday Schedule, default 0 * * * * (every full hour). Only runs while WebDonkey is open. A missed date is caught up once at the next start
Webhook starts on a request to an address only this Mac can reach, for Git hooks, your own scripts, local programs and containers Method (default POST, also Any method), Answer: At once (202 with the run's id) or When the run has ended (its result), plus Wait at most (seconds), default 30
App event (Premium) starts on a WebDonkey notification Notification: Every notification or one kind such as Backup created, Process aborted, Mail in Mailpit, Subscription due, Claude is waiting
File change (Premium) starts when a file or folder changes File or folder, Include subfolders (on), Only these files (patterns with * and ?, separated by commas), Wait for quiet (ms), default 1000

More on the webhook

  • The trigger shows the Address in the form http://127.0.0.1:<port>/hook/<token>, with Copy address and Copy curl command. It stays the same after a restart too. Only if the remembered port is taken does WebDonkey choose a new one. A new workflow shows the address once it is saved.
  • Next to it, it says whether it is listening. It only answers while the workflow is on.
  • The run starts with one item made of method, path, query, headers and body. JSON is parsed, anything else is text, 1 MB at most.
  • Methods other than the chosen one get 405. From a Docker container, use host.docker.internal instead of 127.0.0.1.

More on the app event

The run starts with one item made of kind, title, body and route of the notification. Kinds you switched off in the settings do not arrive. Notifications of workflows never start a workflow. The choices are Package installed, Update available, Backup created, Scheduled task ran, Process aborted, AI model ready, ISO downloaded, Mail in Mailpit, Monitoring, Subscription due, Claude is waiting, WebDonkey Editor found and Transfer finished.

More on the file change

The run starts with one item made of the changed paths and the kind of change (created, modified, removed, renamed). Changes in node_modules, .git, target and vendor never count. Changes in quick succession start one run together.

Logic

Node Does Important fields
If sends every item to the output "true" or "false" depending on the condition Conditions, “True” when: all conditions hold or at least one holds
Switch sends every item to the output of the first matching rule, otherwise to "otherwise" Rules: the first row leads to output 0, the second to output 1 and so on
Wait pauses the run and then hands the items on, once for all of them together Duration (default 5), Unit: Seconds or Minutes. The run's time limit keeps running
Stop ends the run here End the run as: Success or Error, plus Message. With success the message shows at the run as a note, with error as the error message

A condition consists of Value, Comparison and Compare with. Comparisons: equals, does not equal, greater than, greater or equal, less than, less or equal, contains, does not contain, starts with, ends with, matches the pattern, is empty, is not empty, is true, is false. WebDonkey compares numbers as numbers, everything else as text. Case matters.

Data

Node Does Important fields
Set fields adds or changes fields of every item Fields (name and value, a dot in the name reaches into an object such as address.city), Keep other fields (on)
Filter only lets items through that meet the conditions. The rest ends here Conditions, An item passes when
Split list turns a list inside an item into one item per entry List field, without braces, such as positions. Keep other fields (off)
Aggregate combines all items into one: list and count, optionally sum, minimum, maximum and average Name of the list (default items), Collect only this field, Field with numbers
Merge merges the items of several branches into one list Pass on only this field
Only new (Premium) only lets items through whose key the workflow has not seen yet, across runs too. It remembers the last 10,000 keys Key, an expression such as {{ json.id }}
Remember value (Premium) stores a value in the memory. Later nodes and runs read it as state.<name> Name, Value. Leaving it empty forgets the name
Run code (Premium) runs your own script once with all items: JSON in through stdin, JSON out through stdout Language: JavaScript (Node.js), PHP, Python 3 or Shell (sh), Script, Site, Working folder

Input / output

Node Does Important fields
HTTP request sends one request per item and hands on status, headers, body and duration_ms Method, URL, Query parameters, Headers, Body (None, JSON, Text, Form fields), Sign-in (None, Bearer token, User name and password (Basic)), Time limit (seconds) (30), Fail on an HTTP error status (on), Accept invalid certificates (off)
Shell command runs one command per item through sh -c, with the PHP and Node versions chosen in WebDonkey. Hands on exit_code, stdout, stderr and duration_ms Command, Site (the command then runs in its folder with its PHP version), Working folder, Fail on an exit code other than 0 (on)
Read file reads a file up to 10 MB, as text in the field content or as JSON in the field data File, Content is: Text or JSON, One item per line
Write file writes text into a file per item and hands the item on unchanged File, Content (just {{ json }} writes the whole item), If the file exists: Replace it, Append to it, Only create (fail if it exists), Create folders (on)
Notification files one notification per item in WebDonkey's bell. While WebDonkey is in the background, macOS shows it as a banner. A click opens the workflow Title, Text
Send mail (Premium) sends one mail per item, by default to the local Mailpit (nothing is delivered) or through your own SMTP server To, Subject, Format (Text or HTML), Message, From, Send through, plus for SMTP SMTP server, Encryption (STARTTLS, TLS, None (unencrypted)), Port, User name, Password (name of the secret)

Paths in File, File or folder and Working folder are full paths or start with ~/.

WebDonkey

Node Does Important fields
Control service (Premium) starts, stops or restarts a service and hands on the state afterwards Service such as mysql or php@8.3, Action: Start, Stop, Restart
Control site (Premium) starts, stops or restarts a site Site (also by its domain such as shop.test), Action
Database query (Premium) runs SQL against a local database and hands on every row as an item Database: MySQL, MariaDB, PostgreSQL or SQLite file, Database name or File, SQL, Allow writing (off), Row limit (500, at most 1000 from a database service)
Remote command (Premium) runs a command over one of your saved SSH connections and hands on exit_code, stdout and stderr Connection, Command, Fail on exit code (on). Also needs Premium's remote features

AI

Node Does Important fields
AI prompt (Premium) sends a prompt per item to a local Ollama model and hands on the answer in the field text. Nothing leaves your Mac, the node refuses cloud models Model (Ollama has to run), Prompt, System text, Temperature, JSON answer (the parsed answer is then in the field json as well)

Canvas

Node Does Important fields
Note a note on the canvas, never run Text, Colour (Yellow, Blue, Green, Pink, Grey), Width, Height

What happens in the background

  • Nodes such as HTTP request or Shell command work per item, so once for every incoming item. Run code, Aggregate, Merge, Only new, Wait and Stop work once with all of them together.
  • Some nodes have a time limit of their own: 60 seconds for HTTP request, Send mail and Database query, 120 seconds for Control service and Control site, 300 seconds for Shell command, Run code, Remote command and AI prompt. You can change it per node.
  • In SQL and commands, text inserted with {{ … }} becomes part of the statement. Put values from outside, such as from a webhook, in quotation marks. In Shell command and Run code, variables and secrets are also available as environment variables ($name), then their text does not become part of the command.

Free and Premium

Nodes marked (Premium) only run with Premium. A workflow with such a node can be saved and edited on the Free plan, but not switched on or run. A lock on the node shows that it needs Premium.

Troubleshooting

What you see Why What you do
Ollama is not running. … The Ollama service is off Start the Ollama service and run again
The model “…” is not installed in Ollama. … The model is missing Install it on the AI page or choose another one
Message that the step delivered more items than a step may hand on More than 10,000 items Filter or aggregate before
Several sites are called “…”. … or Several connections are called “…”. … The name is ambiguous, the run stops Choose the site or connection directly in the node, for sites the domain works too
The site “…” does not exist (any more). The site was deleted or renamed Choose an existing site in the node

See also

Data, expressions and variables Free

Items flow between the nodes: small packets of fields, such as { "status": 200, "body": "…" }. In a node's fields you reach this data with expressions, for example {{ json.status }}. For values you need in several nodes, and for passwords, there are variables and secrets.

Where to find it

  • You write expressions into the fields of a node's form. The Insert field button on every suitable field helps.
  • You open variables and secrets in the editor through Variables in the canvas toolbar.

How to do it

Insert a value of the previous node

  1. Run the workflow once. Only after that does the editor know the fields of the earlier nodes.
  2. Open the form of the node that needs the value.
  3. Click Insert field on a field and pick the field from the list, for example under Current item. Search fields filters the list.
  4. The expression is in the field, such as {{ json.status }}.

Before the first run it says Run the workflow once, then the fields of the earlier nodes can be picked here.

Create a variable

  1. Click Variables in the editor. The dialog Variables and secrets opens.
  2. Under This workflow, enter name and value, such as site_url and https://shop.test.
  3. Save the workflow. From now on the value is available as {{ vars.site_url }}.

Create a secret

  1. Open Variables and go to All workflows.
  2. Enter name and value and switch on Secret.
  3. Click Add. The secret is stored at once and available in every workflow as {{ secrets.name }}.

Fields and options

What an expression sees

Name Content
json the current item, for example json.total
item.index its position, counting starts at 0
nodes["Name"].json the output of another node by its name, .items for all its items
trigger the trigger's data
vars your variables, for example vars.site_url
secrets your secrets, for example secrets.api_token
state the workflow's memory, for example state.last_id
workflow.id, workflow.name id and name of the workflow
run.id, run.started_at id and start time of the run
now the current time

Insert field groups these values under Current item, the names of the earlier nodes, Trigger, Variables, Secrets, Memory and General (with current time and position of the item).

Rules for expressions

  • Strict: a field that does not exist is an error, not an empty text. That way a typo in a field name shows at once. For a field that may be missing, write {{ json.note | default('') }}.
  • Types are kept: if a field consists of exactly one expression, such as {{ json.total * 2 }}, the result keeps its type: number, list, object or boolean. If there is more around it, such as Total: {{ json.total }}, it becomes text.
  • Filters are attached with |: default, upper, join, tojson, urlencode and more, plus fromjson, date(format), regex_replace(pattern, replacement), basename, dirname, sha256, b64encode and b64decode. date takes a format such as '%d.%m.%Y', without a format %Y-%m-%d %H:%M applies.
  • Node names: you address a node through nodes["Name"]. Its name has to be unique, you change it in the node's settings.

Variables and secrets

Section Meaning
This workflow variables saved and exported with the workflow. They win over a shared variable of the same name
All workflows variables and secrets for every workflow. They are stored at once. A Secret is stored encrypted, never shown again and never exported. To replace it you type it anew (Stored. Type to replace it.)

Names consist of letters, digits and _ and do not start with a digit. A name that already exists says This name is already in use.

What happens in the background

  • In Shell command and Run code, variables and secrets are also available as environment variables under their name, $name in the shell, process.env.name in JavaScript. That way their text does not become part of the command.
  • In the run history WebDonkey does not show secrets in plain text.
  • An expression may not compute forever. WebDonkey stops a loop over billions of entries long before.
  • In the app backup, the shared variables travel along, secrets encrypted.

Troubleshooting

What you see Why What you do
Error that a field is undefined A typo in the name or the field is missing in this item Check the name in the history under Output, use default('') for optional fields
A number arrives as text There is more text around the expression Cut the field down to exactly one expression
nodes["…"] does not find the node The node has another name or was renamed Look the name up in the node's settings
Letters, digits and _ only, not starting with a digit. The variable's name is invalid Adjust the name

See also

Settings and error handling Free & Premium

What happens when a step fails? How long may a run take? You set this on two levels: in the settings of one node and in the Workflow settings.

Where to find it

  • Node: click the node, at the bottom of the form on the right the section Settings.
  • Workflow: the Settings button in the editor's head line. It opens the dialog Workflow settings.

How to do it

Build an error branch that notifies you of a failure:

  1. Click the node that can fail, such as an HTTP request.
  2. At the bottom under Settings, set On error to Use the error output. An Error output appears on the node.
  3. Drag a line from the Error output to a new Notification.
  4. Save the workflow.

If the step fails, the error runs as an item into the new branch, and the run does not count as failed.

Fields and options

A node's settings

Field Meaning Default
Name expressions reach the node through nodes["Name"]. It has to be unique the name of the node kind
Switched off a switched-off node hands its input on unchanged off
Attempts how often the step is tried in total before it counts as failed. 1 means no retry 1
Pause between (ms) waiting time between two attempts 0
Time limit (seconds) how long one attempt may take. Empty: the usual limit of this kind of node empty
On error see below Stop the run
Note a reminder about the node empty

On error

Choice What happens
Stop the run The run ends as failed.
Continue The error is noted at the step; the run goes on with the input.
Use the error output The error leaves the node as an item on its Error output.

Workflow settings

Field Meaning Default
Description stands under the name in the list empty
Time limit of a run (seconds) a run that takes longer ends as failed 600 (10 minutes)
Notify on failure a failed run files a notification in the bell on
Runs kept in the history how many runs the history keeps, up to 200. Older runs go when a new one starts 200

What happens in the background

  • A node's time limit applies per attempt. If it runs out, WebDonkey tries the step again while Attempts are left.
  • The run's time limit runs across everything, Wait included. Once it is reached, the run ends, whatever On error says.
  • The notification from Notify on failure names the node and the error.

Free and Premium

On the Free plan the history keeps the last 20 runs, even if Runs kept in the history says more. The dialog says Free keeps the last 20 runs, Premium up to 200. Every other setting is free.

Troubleshooting

A failed run names the reason in plain words, for example:

Message What you do
This step took longer than its time limit of … s. Raise the node's Time limit (seconds)
The run took longer than the workflow’s time limit of … s. Raise the Time limit of a run
WebDonkey was quit while this run was under way. Run it again
This workflow is already running. Wait until that run has ended, or cancel it. Wait, or click Cancel in the Runs panel
WebDonkey knows no service called “…”. Check the name in the Control service node
The connection “…” does not exist (any more). Choose an existing connection in the node

A Stop node with success shows its message at the run as a note (Ended on purpose with this note:), not as an error.

See also

Runs Free & Premium

Below the editor sits the Runs panel. The History tab shows every run of a workflow step by step: how many items each node received and emitted, how often it tried, how long it took and what exactly it put out. Next to it sits the Memory tab.

Where to find it

In a workflow's editor, the Runs panel at the bottom, tab History. Fold runs and Unfold runs make room, you drag the height at the top edge.

How to do it

  1. Start the workflow with Run. The new run appears at the top of the history with Running.
  2. Click the run. On the right stands the table Steps, and on the canvas the editor marks how each node ended.
  3. Click a step. Output shows its items, one after the other.
  4. Use the field names from the output for the expressions in the next node, such as {{ json.status }}.

Fields and options

History

The newest run is at the top. Every run carries a status:

Status Meaning
Running the run is not finished yet
Succeeded every step ran through
Failed a step failed or a time limit ran out, the reason is at the run
Cancelled you ended the run with Cancel
Skipped for a step: it did not come up in this run

Without a run it says No runs yet.

Steps

Column Shows
Step the node
Items how many went in and out
Attempts how often the step ran
Duration how long it took

Output

Output shows the selected step's items as foldable JSON, Copy as JSON puts them on the clipboard. For large outputs it says Showing … of … items: the stored output is capped. The counts are exact.

Buttons on a run

  • Cancel ends a run that is under way.
  • Run again starts a new run with the trigger data of this one, such as the same webhook body.

What happens in the background

  • How many runs the history keeps is set in the Workflow settings. Beyond that, the oldest goes when a new one starts.
  • The history stays on this Mac and does not travel in the app backup.
  • With wd workflows runs <workflow> you read the history in the terminal too.

Free and Premium

On the Free plan the history keeps the last 20 runs per workflow, with Premium up to 200.

Troubleshooting

What you see Why What you do
The runs could not be loaded. The history data cannot be read right now Reopen the workflow
The run could not be started. A trigger is missing, the Free limit is reached or a Premium node is in it Read the message, it names the reason
This step was skipped. The branch with this node did not come up, such as the "false" output of an If Nothing, that is intended

See also

Memory Premium

A workflow can keep things between two runs: the highest id it has already processed, or which mails it has already seen. The Memory tab in the Runs panel shows what that is and clears it up. Memory is a Premium feature.

Where to find it

In a workflow's editor, the Runs panel at the bottom, tab Memory. At the top it says What this workflow keeps between runs.

How to do it

Only process new orders:

  1. Fetch the orders with an HTTP request and use Split list to make one item per order.
  2. Put an Only new node after it with the Key {{ json.id }}.
  3. Run the workflow. In the first run every order gets through, in the next only the new ones.
  4. The Memory tab now says how many keys the node has remembered.

Fields and options

Entry Origin
a name with its value stored by the Remember value node. Later nodes and runs read it as {{ state.name }}
node name with … keys remembered how many keys an Only new node has already seen, the last 10,000 at most. If the node no longer exists, Removed node stands in place of its name
  • Forget … on an entry removes only that one.
  • Reset memory deletes everything. The question Reset the memory? explains: the workflow forgets everything, also what Only new has already seen, and the next run starts from scratch. Confirm with Reset.

If nothing is stored yet, it says This workflow remembers nothing yet.

What happens in the background

  • A node sees in state what was there at the start of its step. As long as no run has stored a value, {{ state.last_id | default(0) }} avoids an error.
  • Names starting with two underscores belong to WebDonkey itself. Remember value does not take them.
  • If you delete a workflow, its memory goes with it.
  • Memory travels along in the app backup in the Workflows category.

Free and Premium

Remember value and Only new are Premium nodes. On the Free plan a workflow with them can be saved but not switched on or run.

Troubleshooting

What you see Why What you do
Only new lets nothing through any more Every key is known already Check that the key tells every item apart, for testing use Reset memory
Error at state.name in the first run The value is not stored yet Append `

See also

Cookie preferences

This website uses cookies to ensure the best experience possible. Your choice applies to webdonkey.io and the shop at shop.webdonkey.io. More information...

Technically required

Cookies required for this website to function:

Always on
WebDonkey
WebDonkey
Provider: BuI Hinsche GmbH, Neumarkt 7, 06712 Zeitz, Germany
Purpose: Your consent, colour scheme and language for website and shop, price switches; with wd_debug in the address, the measurement events in the developer console for troubleshooting
Cookies and storage: Cookie wd_consent on .webdonkey.io, shared with shop.webdonkey.io (12 months); cookies wd_theme and wd_lang on .webdonkey.io, shared with shop.webdonkey.io, only when you switch colour scheme or language yourself (365 days); localStorage wd:consent, wd:theme, wd:lang; sessionStorage wd:acc, wd:term, wd:debug (only with wd_debug in the address; until the tab closes)

Statistics

Shows us which pages and products people look at on webdonkey.io and in the shop, where visitors come from and how they get to a purchase (with order number, amount and products, without name or email address). Provider: Google. Transfer to the USA possible (EU-US Data Privacy Framework). Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Google Analytics 4
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Google Analytics 4
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Usage statistics: page views, clicks, scroll depth, sources, devices, load times; in the shop also basket, checkout, purchases, registration and sign-in
Cookies and storage: _ga, _ga_<ID> (2 years)
Privacy policy

Marketing

Measures whether our ads on Facebook, Instagram and TikTok lead to visits and downloads on webdonkey.io and to registrations and purchases in the shop, and builds audiences for ads. Providers: Meta and TikTok, with whom we are jointly responsible for this. With this consent Google may also set advertising cookies (_gcl_…). Transfer to the USA and other countries outside the EU possible. Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Meta Pixel (Facebook, Instagram), TikTok Pixel
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Meta Pixel (Facebook, Instagram)
Provider: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland
Purpose: Ad measurement and target groups on Facebook and Instagram, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _fbp (3 months), _fbc (3 months, only if you arrive through an ad), fr on facebook.com (3 months)
Privacy policy
TikTok Pixel
Provider: TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland
Purpose: Ad measurement and target groups on TikTok, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _ttp, _tt_enable_cookie (13 months)
Privacy policy