Workflow can embed variables using ${...} syntax. You can use built-in variables or define your own variables.
Here is the list of built-in variables:
| Name | Description | Example |
|---|---|---|
| timezone | Timezone of this workflow | America/Los_Angeles |
| project_id | The project ID of this workflow | 12345 |
| session_uuid | Unique UUID of this session | 414a8b9e-b365-4394-916a-f0ed9987bd2b |
| session_id | Integer ID of this session | 2381 |
| session_time | Time of this session with time zone | 2016-01-30T00:00:00-08:00 |
| session_date | Date part of session_time | 2016-01-30 |
| session_date_compact | Date part of session_time (compact) | 20160130 |
| session_local_time | Local time format of session_time | 2016-01-30 00:00:00 |
| session_tz_offset | Time zone offset part of session_time | -0800 |
| session_unixtime | Seconds since the epoch time | 1454140800 |
| task_name | Name of this task | +my_workflow+parent_task+child_task0 |
If schedule: option is set <scheduling_workflow.md>, last_session_time and next_session_time are also available as follows:
| Name | Example (hourly schedule) | Example (daily schedule) |
|---|---|---|
| last_session_time | 2016-01-29T23:00:00-08:00 | 2016-01-29T00:00:00-08:00 |
| last_session_date | 2016-01-29 | 2016-01-29 |
| last_session_date_compact | 20160129 | 20160129 |
| last_session_local_time | 2016-01-29 23:00:00 | 2016-01-29 00:00:00 |
| last_session_tz_offset | -0800 | -0800 |
| last_session_unixtime | 1454137200 | 1454054400 |
| next_session_time | 2016-01-30T01:00:00-08:00 | 2016-01-31T00:00:00-08:00 |
| next_session_date | 2016-01-30 | 2016-01-31 |
| next_session_date_compact | 20160130 | 20160131 |
| next_session_local_time | 2016-01-30 01:00:00 | 2016-01-31 00:00:00 |
| next_session_tz_offset | -0800 | -0800 |
| next_session_unixtime | 1454144400 | 1454227200 |
The timestamp of the last schedule is last_session_time. If the schedule is hourly, it’s the last hour. If the schedule is daily, it’s yesterday. It doesn’t matter whether the last schedule actually ran or not, then the timestamp is set to the last timestamp calculated from the current session time.