DocumentationWorkflowsTriggers
Schedule node
Kicks off the workflow at fixed times or in intervals, e.g. every hour, weekdays at 09:00, or on the 1st of each month. Multiple rules possible. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
7 min readUpdated
What this node does
Kicks off the workflow at fixed times or in intervals, e.g. every hour, weekdays at 09:00, or on the 1st of each month. Multiple rules possible.
Use Schedule as a clearly defined step in an anymize workflow.
- Starts a new workflow run.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Schedule from the node catalog.
- 02Complete the required fields and map values from previous steps.
- 03Run the node with a small test record and inspect its output.
- 04Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Schedule has one focused purpose. Its available settings appear when you select the node.
Settings
| Field | Meaning | Area |
|---|---|---|
| Rules | You can set up multiple rules, the workflow runs every time one of them matches. | Standard |
| Timezone | Choices: Europe/Berlin, Europe/Vienna, Europe/Zurich, Europe/London, Europe/Paris, UTC, America/New_York, America/Los_Angeles, America/Chicago, Asia/Tokyo, Asia/Singapore, Australia/Sydney | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | This trigger does not require an input. | JSON |
| Output | Meaning | Type |
|---|---|---|
| firedAt | Time the workflow was started. | text |
| ruleIndex | Which rule fired (when there are several rules). | number |
| timezone | Timezone the rule is defined in. | text |
Example and test run
Example scheduler payload: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"firedAt": "2026-04-18T09:00:00Z",
"ruleIndex": 0,
"timezone": "Europe/Berlin"
}Access and security
Before activation, review which data enters this step and what its output contains.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.
- Workflow does not start: activate it and check the trigger's test and production mode.