DocumentationWorkflowsLogic and data
Date & Time node
Generates the current date, adds/subtracts time units, or formats an existing date (ISO, Unix, regional notation). Handy for things like “in 7 days” or “next Monday at 09:00”. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
7 min readUpdated
What this node does
Generates the current date, adds/subtracts time units, or formats an existing date (ISO, Unix, regional notation). Handy for things like “in 7 days” or “next Monday at 09:00”.
Use Date & Time as a clearly defined step in an anymize workflow.
- Processes one input.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Date & Time 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
Choose the required function in Operation. The panel then shows the relevant settings.
- Now
- Add
- Subtract
Settings
| Field | Meaning | Area |
|---|---|---|
| Operation | Choices: Now, Add, Subtract | Standard |
| Source field | Configure this value in the node panel. | Standard |
| Amount | Configure this value in the node panel. | Standard |
| Unit | Choices: Seconds, Minutes, Hours, Days, Weeks, Months, Years | Standard |
| Format | Choices: ISO 8601, Unix seconds, Unix milliseconds, YYYY-MM-DD, HH:MM:SS | Standard |
| Target field | Configure this value in the node panel. | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | Receives the complete result from the previous step. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
Example and test run
Test-run example: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"input": "value"
}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.