Relative Due Date Triggers
Trigger automations a set time before or after a record's due date — not on a fixed schedule.
Relative due date triggers fire automations based on a record’s own due date rather than a wall-clock time. Schedule an action “1 day before due”, “2 hours after due”, or “on the due date itself” and Blue computes the exact moment per record.
This is the right fit when timing should follow the work, not the calendar — reminders before a deadline, escalations after one, day-of-day prompts to a client.
Setting one up
- Open the Automations panel for the workspace.
- Create a new automation and pick the Relative to due date trigger.
- Choose:
- When — Before due, After due, or On due date.
- Offset — minutes, hours, days, weeks. Required for Before and After, ignored for On due date.
- Pick the date field. The built-in record due date is the default; any custom date field works too.
- Add conditions if you only want it to fire on a subset of records.
- Add the actions to run.
Examples
- 1 day before due → send a reminder email to the assignee.
- On due date → post to a Slack channel.
- 3 days after due → reassign to a manager and tag Escalated.
- 1 week before due on a custom “Renewal date” field → create a follow-up record in a different workspace.
Behavior
- The trigger fires once per record at the computed time. Changing the due date after the trigger has already fired does not re-fire it.
- Changing the due date before the trigger fires reschedules it automatically — push a deadline out a week and the reminder moves with it.
- Records without a value in the chosen date field never fire.
- Completed records are skipped by default. You can override this in the trigger settings if you need post-completion follow-ups.
Pair Before due reminders with Conditional Automations to skip records that are already in a “Done” or “Cancelled” status — saves your team from chasing work that’s no longer relevant.