Workflow triggers, actions, tests, and runs

Use this reference while you build or audit a Workflow. The editor checks the graph and refuses to run anything it cannot resolve safely, such as a missing Type, property, relation, mapping, or branch.

Triggers

Every Workflow has exactly one trigger. To change it, select the trigger node and choose Change trigger.

Capture

Starts when an item lands in Captures. Use From to limit it to certain sources, such as Quick capture, Clipboard, Share sheet, AI agent, API, or Integration. Its conditions can also check:

The content kind: text, URL, file, image, audio, or HTML.
The link’s host, such as youtube.com.
Text in the title or the captured text.
The Object Type, optionally with Include subtypes.
Property filters.

Capture triggers act only on Captures, never on notifications.

Object created or changed

Starts when an Object of the chosen Type is Created, or when a property changes (Property changed). A property-change trigger can watch one property or Any property.

Lar batches bursts of edits for a moment, and it briefly ignores changes that a Workflow itself just made. This reduces loops but does not make two Workflows that edit each other’s watched properties safe, so test them together.

Schedule

Runs Every hour, Every day at a time, or Every chosen weekday at a time. The time is read in the time zone shown next to it, which starts as your current one; choose another to run at that zone’s clock time. A time that does not exist on a daylight-saving day runs once, right after the clock jumps, and a time that happens twice runs once.

If Lar was closed when a run was due, it catches up with only the most recent missed run. A For each step in a scheduled Workflow processes a limited number of Objects per run, so do not rely on one run for a bulk migration.

Date property

Runs On the day, a number of Days before, or a number of Days after a date or date-time property, at a local time you choose. Pick the property from the Workflow’s Type; if it stops being a date property, the editor flags the trigger.

An empty or malformed date never matches. Changing the date re-arms the Workflow for the new date.

Manual

Runs only when you start it: choose Run workflow from an Object’s ⋯ menu or the command palette, or select several Objects and run it on all of them at once. A manual Workflow can ask a free-text question (Ask a question) or offer options (Ask to choose) before it runs.

Match scope and filters

The trigger decides which event wakes the Workflow; the scope and filters decide whether it matches.

Choose a Type, or leave Any type where the editor allows it.
Turn on Include subtypes when Objects of child Types should match too.
Add filters on properties, relations, dates, or system fields.
For a Capture trigger, choose sources under From.
For a Capture trigger, check the live count, such as “3 items in Captures match right now”.

If a condition cannot be checked, because a field or relation no longer exists, an operator is not supported, or the nesting is too deep, Lar turns matching off for safety and names the condition.

Actions

Choose Add node and pick a step. The menu groups them like this:

Group	Steps
Organize	Set properties, Add tags, Remove tags, Add to collection, Remove from collection, Link relation, Apply template, Convert to type, Delete object
Create	Create object, Send notification, Append to body, Compute formula, Run workflow, Send webhook, Identify entity, Enrich entity, Pick an object
AI	AI: Classify, AI: Extract fields, AI: Summarize
Input	Ask a question, Ask to choose (Manual trigger only)
Captures	Archive, Discard (Capture trigger only)
Control	If, Switch, For each

Pick an object is offered only for a Schedule trigger, and Delete object is not offered for a Capture trigger.

Send webhook includes presets with setup instructions for n8n, Zapier, Make, and Pipedream, or you can use a Generic webhook.

Map values into a step

Each field in a step can be:

Fixed value: text or a value you enter.
Item field: a field from the triggering Object or Capture.
AI output: the result of an earlier AI step.
Template: text with fields inserted, such as {{title}}.

Workflows have no general-purpose scripting. Compute formula uses Lar’s bounded formula language, and templates only substitute values.

Control flow

Use If to branch on a condition, Switch to route a value to one of several cases (a value that is missing, such as the result of a lookup that found nothing, matches only a case left empty, and otherwise takes the fallback exit), and For each to run steps once per matching Object.

An AI step placed behind a Switch on a lookup result cannot be used, because AI steps are resolved before the run starts, when the lookup has found nothing, so the run stops safely. A newly added Switch case you have not filled in yet is empty, so it also matches a missing value.

A For each node has two exits:

Each item runs once for every matching Object.
Done continues after the last one.

A For each node processes up to 100 Objects by default; raise its Limit to at most 500. Run history summarizes loop steps instead of recording a row for every item.

Test a Workflow

Open the Workflow and choose Test.
Under Test with, choose Use suggested or Choose… to pick a test subject.
Choose Preview.
Check the path, the branch each node took, and each step’s Data in / out.
Fix any mapping or branch you did not expect.
When you are ready, choose Run for real and confirm.

Preview shows what would happen without changing anything. Run for real performs the actual writes and can create, edit, archive, discard, delete, or send data. The confirmation names the subject so you can check the target.

Read run history

Open the Workflow’s Test & runs dock, or choose View runs from its row. Runs appear newest first; filter them with All or Errors.

Each run shows:

The outcome: Succeeded, Partial, Failed, or Denied.
The origin: Capture, Object event, Schedule, Date property, or Manual.
The subject Object, or Deleted object if it no longer exists.
The step count and, under Step details, each step’s result and the branch it took.

Run history is stored in the encrypted workspace database on this device. It does not sync, so each device keeps its own history.

When an automatic run fails, Lar also adds a notification, so you see the failure without opening the editor.

Retry a run

Open View runs.
Expand the failed or partial run and review Step details.
Choose Retry.
Read the confirmation, then choose Re-run.

A retry starts the whole Workflow again from the same saved snapshot; it does not resume at the failed step. To avoid repeating work:

AI results from the earlier run are reused.
Send webhook, Send notification, Run workflow, Identify entity, Enrich entity, and Pick an object steps that already succeeded are not sent again, unless they are inside a For each loop.

Every other step runs again.

Handle failures

By default, a Workflow stops at the first failed step and records a Failed or Partial run. Turn on Continue if this step fails in a step’s options to keep going; later steps then run without that step’s output.

Use this only for optional steps. It does not replace checking required values or webhook destinations.

Checklist before running automatically

The Type and filters exclude unrelated Objects.
Untrusted Capture sources are excluded, or named deliberately and reviewed.
Every create, append, notification, and webhook step is safe to repeat.
Delete object is the last step on its path, and restoring from Trash is acceptable.
Standing AI consent and your provider’s spending cap fit how often the Workflow will run.
What this sends lists only fields the webhook destination should receive.
Scheduled and date-property rules cannot fan out to more Objects than you expect.
Preview follows the intended branches for a few typical subjects.
After one live run, run history and notifications show what you expected.