Skip to content

Input Formats

Step inputs support several value formats beyond plain strings.

The most common format — a literal value or pill reference:

inputs:
table: incident
message: "Hello $trigger.current.caller_id.name"

For scripted inputs, nest under a script key:

inputs:
result:
script: |
var gr = new GlideRecord('incident');
gr.get(fd_data.trigger.current.sys_id);
return gr.short_description;

Some inputs need both a display label and a raw value:

inputs:
assignment_group:
display: Service Desk
value: abc123def456abc123def456abc123de

Date and duration inputs:

inputs:
wait_until:
date_type: relative
duration: 2
duration_type: hours
schedule: abc123def456abc123def456abc123de
FieldNotes
date_typerelative, actual, etc.
durationNumber of time units
duration_typeminutes, hours, days, weeks, months
scheduleOptional schedule sys_id (for business time)

For Create Record, Update Record, and Create Task steps, the values input accepts a map of field assignments:

- action: create_record
inputs:
table: incident
values:
short_description: "Auto-created incident"
priority: "1"
assignment_group: $find_group.record.sys_id
caller_id: $trigger.current.caller_id

This is the YAML equivalent of Flow Designer’s field picker.

- action: update_record
inputs:
table: incident
values:
state: "6"
close_code: Solved (Permanently)
close_notes: "Resolved by automation."

If and Do Until steps support condition inputs for fine-grained control:

InputNotes
operator=, !=, >, <, LIKE, IN, etc.
rhsRight-hand side value
lhsLeft-hand side value (usually set by the condition string)
- if: "$trigger.current.state"
inputs:
operator: "IN"
rhs: "1,2,3"
then:
- action: log
inputs:
message: "State is 1, 2, or 3"

Different inputs on the same step can use different formats:

- action: create_record
inputs:
table: incident
values:
short_description: "Created by flow"
priority: "1"
wait:
date_type: relative
duration: 1
duration_type: hours