Convert UTC to MENA Local Time in n8n (Ramadan Send Rules)

Convert UTC to MENA local time—then apply Ramadan-aware sending rules in n8n

This n8n sub-workflow converts a UTC timestamp into MENA local time (based on your IANA time zone), computes workweek/weekend status, derives Umm al-Qura Hijri dates, and decides whether a message is sendable—including Ramadan late-night and Friday-prayer blocking—returning a clear contract for downstream automation.

What this workflow does

• Accepts inputs from a parent workflow (or a manual self-test): ts_utc, tz (IANA), country, and audience.
• Applies defaults when values are missing (e.g., Baghdad time zone, Iraq country code, and a current UTC timestamp).
• Converts time and computes context: converts UTC to the target time zone, calculates the UTC offset, determines the local weekday, and flags workdays vs weekends using a per-country weekend table.
• Supports scheduling rollups: computes local day boundaries in UTC and calculates the next workday start time for scheduling.
• Derives Hijri + Ramadan flags: derives Umm al-Qura Hijri date and flags Ramadan, Eid al-Fitr, Eid al-Adha, and the Hajj window, including any user-provided holiday overrides.
• Evaluates sendability windows: classifies local time into a daypart and checks whether the timestamp is inside an allowed send window (with Friday prayer blocking and Ramadan late-night rules).
• Outputs a dependable contract: returns is_sendable, block_reason, and—when blocked—send_after. You can also run a self-test report with pass/fail assertions.

Use cases

• Scheduling campaigns across MENA countries with accurate local time and weekend rules.
• Preventing outbound messages during blocked periods (e.g., Friday prayer and Ramadan late-night).
• Building reliable “send later” logic that schedules at the next allowed workday start.

Technical details

• Nodes/logic used: if, set, code, sticky note, manual trigger, execute workflow trigger.