Input Formats
Step inputs support several value formats beyond plain strings.
String
Section titled “String”The most common format — a literal value or pill reference:
inputs: table: incident message: "Hello $trigger.current.caller_id.name"Script
Section titled “Script”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;Display / Value Pair
Section titled “Display / Value Pair”Some inputs need both a display label and a raw value:
inputs: assignment_group: display: Service Desk value: abc123def456abc123def456abc123deDate Object
Section titled “Date Object”Date and duration inputs:
inputs: wait_until: date_type: relative duration: 2 duration_type: hours schedule: abc123def456abc123def456abc123de| Field | Notes |
|---|---|
date_type | relative, actual, etc. |
duration | Number of time units |
duration_type | minutes, hours, days, weeks, months |
schedule | Optional schedule sys_id (for business time) |
Field Map
Section titled “Field Map”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_idThis 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."Condition Inputs
Section titled “Condition Inputs”If and Do Until steps support condition inputs for fine-grained control:
| Input | Notes |
|---|---|
operator | =, !=, >, <, LIKE, IN, etc. |
rhs | Right-hand side value |
lhs | Left-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"Mixing Formats
Section titled “Mixing Formats”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