Mankomail

Compute a date ​

Adds a delay — calendar or business — to a date, to write it elsewhere: a table, a draft, a CRM.

The Compute a date node adds a delay to a date and publishes the result, so you can write it somewhere: a table row ("follow-up planned on…"), a draft ("we will get back to you before…"), a CRM field. It uses exactly the same rules and the same business calendar as the Wait node, so the date you write is the date a wait with the same settings would wake up.

The start is either now or a date from the data. Counting is either in calendar units (minutes to years; months and years are civil, so 31 January + 1 month is 28 or 29 February) or in business days or hours, skipping weekends, public holidays and closures declared in Administration → Business calendar (by default: Monday to Friday, 09:00–18:00, French public holidays, Europe/Paris).

At a glance ​

  • Type: date.compute · version 1
  • Category: Data
  • Kind: Step — one stage of a run
  • Effect: No external effect (none) — nothing is written outside Mankomail; safe to replay
  • Needs a carrier email: No
  • Connection: None
  • Inputs: main
  • Outputs: main

Parameters ​

base ​

Starting from

  • Type: One choice (options)
  • Required: Yes
  • Default: now
  • Options:
    • now — now
    • date — a date from the data

date ​

Start date — 2027-05-04 is read at midnight in the time zone below, never in UTC.

  • Type: Text (string)
  • Required: Yes
  • Default: "" (empty)
  • 200 characters at most
  • Example: {{ data.extract_1.deedDate }}
  • Shown when: base is date
  • Expressions: {{ }} accepted

kind ​

How to count

  • Type: One choice (options)
  • Required: Yes
  • Default: calendar
  • Options:
    • calendar — in calendar days
    • business — in business days or hours: The instance business calendar: weekends, public holidays, closures.

amount ​

How many

  • Type: Number (number)
  • Required: Yes
  • Default: 8
  • Whole number, from -100000 to 100000

unit ​

Unit

  • Type: One choice (options)
  • Required: Yes
  • Default: days
  • Options:
    • minutes — minutes
    • hours — hours
    • days — days
    • weeks — weeks
    • months — months
    • years — years
  • Shown when: kind is calendar

businessUnit ​

Business unit

  • Type: One choice (options)
  • Required: Yes
  • Default: businessDays
  • Options:
    • businessDays — business days
    • businessHours — business hours
  • Shown when: kind is business

atClock ​

Time of day — HH:MM. Empty: the computed time.

  • Type: Text (string)
  • Required: No
  • Default: "" (empty)
  • 80 characters at most
  • Example: 09:00
  • Expressions: {{ }} accepted

timezone ​

Time zone — IANA name. Empty: the calendar one.

  • Type: Text (string)
  • Required: No
  • Default: "" (empty)
  • 100 characters at most
  • Example: Europe/Paris
  • Shown under “Advanced” in the editor
  • Expressions: {{ }} accepted

Outputs ​

  • main

Data produced ​

What this node adds to the run data, and how to read it in an expression. <step> stands for the step key: the node name turned into an identifier (see Data and expressions).

  • {{ data.<step>.iso }} — string. The computed instant, in ISO 8601 UTC (2026-10-14T16:00:00.000Z). The form to pass to another node.
  • {{ data.<step>.date }} — string. The calendar date in the time zone used, YYYY-MM-DD. The form for a table cell.
  • {{ data.<step>.time }} — string. The time of day in the time zone used, HH:MM.
  • {{ data.<step>.timezone }} — string. The IANA time zone used: the one set in the node, otherwise the organisation calendar's.
  • {{ data.<step>.summary }} — string. A one-line summary in the member's language, e.g. 'Computed date: 2026-10-14.' (with summaryKey and summaryParams).

Example ​

An acknowledgement must promise an answer within 8 business days. Add a Compute a date node named Deadline:

base:         now
kind:         business
amount:       8
businessUnit: businessDays
atClock:      18:00

On Friday 2 October 2026, {{ data.deadline.date }} is 2026-10-14 and {{ data.deadline.time }} is 18:00. Write "We will answer by {{ data.deadline.date }}" in the reply, and store {{ data.deadline.iso }} in a table column.

Tips ​

  • Dates from the data. A date alone such as 2027-05-04 is read at midnight in the chosen time zone, never in UTC; a full ISO 8601 instant is also accepted. An empty or unreadable date, a time not written HH:MM, or an unknown time zone makes the step fail with node_invalid_param.
  • Going back in time. In calendar units, a negative amount goes back ("10 days before the deadline"). In business units, the sign is ignored: the count always goes forward.
  • Business hours are consumed day after day, within opening hours: 48 business hours span more than five calendar days. "Time of day" is ignored with this unit.
  • "Now" is the moment the step runs. A retried step computes again from its own run time.
  • The node only computes: it reads and writes nothing outside the working data, and behaves the same in test runs.