User manual

Prepare, start and monitor a workflow

A workflow links available activities in a saved sequence. Check its inputs, version and permissions before starting or scheduling it. Each run stays tied to the version started, so the history shows what was carried out.

Section 2

Build a readable sequence

Start from an existing workflow or an available template. Catalogue nodes describe the activities you can add, not arbitrary operations. A readable sequence shows what each step will do before you start it.

Editing and saving the graph creates a new version. It does not retrospectively change the inputs or version of runs already started.

  1. Open the list or choose a template and check which brand it concerns.
  2. Add available nodes and read each node’s required inputs.
  3. Check their order and connections, then save the version to run.
The editor for a new version of a workflow: name, steps, links between steps, schedule and confirmation. (fictional brand, demo data)
Demo data · Ilmarde Audio

Section 3

Start the chosen version and follow its states

A run uses the selected saved version. A node requiring review, input or permission can stop the sequence at that point.

Starting a run does not mean every activity is complete. Proposals are not automatically approved; publication and paid activities retain their own controls.

  1. Check the version and inputs before confirming the start.
  2. Read the quote and credit consent when required.
  3. Open run details and check the node reached.
  4. Complete required reviews or inputs; resume only after reading their outcome.
An active run of a workflow: the status of each step and the selected step, ready to run once confirmed. (fictional brand, demo data)
Demo data · Ilmarde Audio

Section 4

Check the calendar and history

Scheduling needs a frequency and, for credit-based activities, consent to the terms shown. History keeps the outcomes available for review.

Changing the calendar frequency, period or status creates a new version and needs valid consent for that version. Missing consent or an unusable source means the calendar is not proof of completed work. Refresh the status before repeating a run with an uncertain outcome.

  1. In the calendar editor choose a one-off, daily or weekly run, start, end and planned or paused status, then save.
  2. Open the saved version’s calendar and read the maximum credits per run. The owner confirms consent using the checkbox and dedicated button, and can revoke it from the same panel.
  3. Check history, receipts and blocking reasons; pause or resume with the available controls.
The schedule of an open workflow: frequency, start, end, credit cap per run and consent. (fictional brand, demo data)
Demo data · Ilmarde Audio

Related paths

Definitions, FAQs, guides and methodology: from here you reach the material you need to read the results and explain them to your team in the same words.

From question to action

Learn how to use TrustInsider: choose the brand and the questions, read the collected answers, update your content and compare the results.

Read

Find the right answer

Help with access, credits, collections, integrations and data: guides, FAQs, the site assistant and support requests from your workspace.

Read