Data and expressions

​

Insert a value

1

Pick a step or form field

Type {{ ctx.steps[' to list the workflow’s steps and pick one that runs before this step, or {{ ctx.params. to pick a field of the trigger’s form.

2

Add the field you want

The picker inserts the whole output, {{ ctx.steps['Prepare details'] }}. Add the field before }}: {{ ctx.steps['Prepare details'].fullName }}. For a list, add the item’s position: {{ ctx.params.starters[0].firstName }}. A Group field’s sub-fields aren’t listed, so type them.Click away from the box when you’ve finished: Enter or Tab replaces the template with the suggestion. The list only appears in single-line fields; in Body, Comment and Code, type the path.

3

Check the names in a test run

Click Manual Trigger, then a step in the run: its Output lists the fields you can read.

In the run, click Set Debug Context. Each step’s panel then has a Debug tab with that run’s Output and context, beside the fields you’re editing.

​

What you can read

​

How templates fill in

• The result is always text: numbers and true/false become text, lists and objects become JSON, and null becomes nothing.
• | json is the only filter. It writes the value as JSON, adding quotes and escaping to text.
• There are no defaults, maths or functions: {{ ctx.params.a || 'x' }} and {{ ctx.params.name | upper }} fail. Use a Code step.
• A path that doesn’t exist fails the step, as does anything between {{ and }} that isn’t a ctx. path, even inside an inserted value such as a form answer.

​

Build JSON

{
  "name": {{ ctx.steps['Prepare details'].fullName | json }},
  "notes": {{ ctx.params.notes | json }},
  "licences": {{ ctx.params.licences | json }},
  "clientId": "{{ ctx.client.id }}"
}

​

Conditions, loops and Code

​

Recipes

• Code reads ctx directly. Whatever you return is the step’s output; returning nothing gives false.
• A new Code step’s JavaScript box starts with three comment lines: replace them with your script.
• An error in the script fails the step. Check the step’s Output in a test run after each change.
• Don’t end the script with a // comment line: the step then fails with a syntax error.
• There’s no console, no web requests and no await. Use HTTP Request to call other systems.

// A form's Date field sends local midnight as a UTC timestamp, e.g. 2026-06-30T23:00:00.000Z
// for 1 July in UK summer time. Adding 12 hours gets back the day that was picked.
const picked = new Date(Date.parse(ctx.params.startDate) + 12 * 60 * 60 * 1000);
const day = String(picked.getUTCDate()).padStart(2, '0');
const month = String(picked.getUTCMonth() + 1).padStart(2, '0');
return {
  fullName: ctx.params.firstName + ' ' + ctx.params.lastName,
  upn: (ctx.params.firstName + '.' + ctx.params.lastName).toLowerCase() + '@acme.com',
  ukStartDate: day + '/' + month + '/' + picked.getUTCFullYear(),
  startDay: picked.getUTCFullYear() + '-' + month + '-' + day,
  licenceList: ctx.params.licences.join(', '),
  manager: ctx.params.managerEmail || 'it@example.com'
};

​

Shape a list for later steps

// One clean record per starter, ready for Create account
const domain = ctx.client.microsoftTenantDomain;
const starters = ctx.params.starters.map(s => {
  const first = s.firstName.trim();
  const last = s.lastName.trim();
  return {
    displayName: first + ' ' + last,
    upn: (first + '.' + last).toLowerCase().replace(/[^a-z.]/g, '') + '@' + domain,
    jobTitle: s.jobTitle || 'New starter'
  };
});
return { starters: starters, count: starters.length };

​

Collect results in a loop

const done = ctx.steps['Collect results'] || [];
done.push({ name: ctx.starter.displayName, upn: ctx.account.userPrincipalName });
return done;

const done = ctx.steps['Collect results'] || [];
return {
  count: done.length,
  lines: done.map(r => r.name + ' (' + r.upn + ')').join('<br>')
};

• When you save, Validation lists STEP_REFERENCE_UNREACHABLE (“Step ‘Collect results’ is not reachable before this step executes”) for a step after the loop that reads it. The run isn’t affected.
• Push into the list you return. A change to a list inside an object from ctx, such as prev.lines.push(x), isn’t kept.
• In the collector, read its own output as ctx.steps['…'], not by a Context Variable Name, which Validation also flags.
• Use one collector per loop. If the Body branches on a Condition, join the branches at the collector.
• Keep one For Loop per path. For a list inside each item, use Trigger Workflow with Await Completion and loop in the other workflow.

​

Save an output under a short name

​

When a step fails

• HTTP Request and Generic Integration Action: tick Allow Non-2xx Status and branch on status or statusCode with a Condition.
• Use the branching steps: Execute PowerShell (Timeout), Check Agents Online, Await Webhook and Check If Integrated.
• An awaited Trigger Workflow carries on when the other workflow fails, with status failed.
• End a path on purpose with Finish Workflow set to Fail.
• Trigger Workflow, Create Ticket, Log to Ticket, Add User to Group, Remove User from Group, Assign Licenses, Edit User and Revoke User Sessions accept continueOnError, which outputs success: false and error instead of failing. The designer doesn’t show it; an AI tool connected through MCP can set it.

​

FAQ