Dates and timing

Evaluate renewal and payment timing

Classifies a renewal or payment due date against now and a reminder window.

Available recipeIncludes configuration, sample data and tests

Make it your own

Review the setup and limits below, then open an editable copy in Turbyn.

Use this recipe

Your selection stays with you through signup.

What it does

Returns overdue, due today, reminder window, or not actionable.

What to customize

Set reminderDays and timezone.

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-09-20T00:00:00Z",
    "field2": "2026-09-13T00:00:00Z"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "reminder_window",
    "output2": "evaluated",
    "output3": "due=2026-09-20T00:00:00.000Z;reminderDays=7;calendar=UTC;no payment or reminder sent"
  }
}

Returned fields

output1: timing classification
output2: evaluated
output3: schedule reason

What changes when it runs

Reads schedule dates and performs local classification; sends no payment or reminder.

Ready to try it with your rules?

Map your inputs, test a sample and publish the version you’ve checked.

Use this recipe