Dates and timing
Derive dates around an event
Derives named dates from an event anchor and offsets.
Make it your own
Review the setup and limits below, then open an editable copy in Turbyn.
Use this recipeYour selection stays with you through signup.
What it does
Supports day, hour, and minute offsets and flags past derived deadlines.
What to customize
Pass offsets as a JSON object of named value/unit pairs.
Run the included tests with your configuration and mappings. Review success, missing-input and failure results before publishing.
Expected outcome
This included example runs in dry-run mode with synthetic data. Integration tests separately cover provider responses using test doubles. It is not a live customer result.
Sample input
sample-input.json
{
"inputFields": {
"field1": "2026-01-01T00:00:00Z",
"field2": "{\"deposit\":{\"value\":-30,\"unit\":\"days\"}}"
}
}Sample output
sample-output.json
{
"outputFields": {
"output1": "{\"deposit\":\"2025-12-02T00:00:00.000Z\"}",
"output2": "calculated",
"output3": "{\"timezone\":\"UTC\",\"preserved\":[],\"past\":[],\"evaluatedAgainst\":null}"
}
}Returned fields
- output1
- named dates JSON
- output2
- calculated or past deadline
- output3
- policy summary
What changes when it runs
Performs local calculations and returns JSON dates.
Ready to try it with your rules?
Map your inputs, test a sample and publish the version you’ve checked.