Multi-Channel Event Countdown Manager - n8n Workflow

• Project Managers who need automated reminders for product launches or deadlines.


• HR Teams looking to automate birthday or anniversary announcements.


• Teams requiring a centralized system for multi-channel event communication.


• Automation Enthusiasts looking for complex examples of using the Code n8n node for data processing and routing in a large n8n workflow.

Manually tracking critical dates and ensuring timely communication across different platforms can be time-consuming and error-prone. This specialized n8n workflow solves this challenge by centralizing event data and automating the entire notification process.

The system wakes up daily via an n8n trigger, determines which events are due for a notification (e.g., 30, 14, 7, 1 day, or day of), and then routes the message to the specified channel, be it Slack or Email.

By leveraging custom scripting within a Code n8n node, this n8n template provides flexible message formatting tailored to the urgency and type of event (birthdays, launches, etc.), ensuring your team receives professional and context-aware reminders automatically.

This comprehensive n8n workflow operates primarily on a schedule, but also contains an auxiliary webhook path for external inputs.

1. Scheduled Execution: The n8n workflow starts with the Schedule Trigger n8n trigger, configured to run every day at 9:00 AM.


2. Data Processing & Filtering: The flow proceeds to the Events Database Code n8n node. This customized n8n node holds the list of upcoming events. It calculates the days remaining until each event and filters the list, keeping only those events that require a notification based on predefined rules (e.g., 30, 14, 7, 1, or 0 days remaining).


3. Channel Routing: The filtered events are split into two parallel paths using Is Slack? and Is Email? If n8n nodes, routing the data based on the event's channel property.


4. Slack Notification Path: If the channel is Slack, the Format Slack Message Code n8n node generates a rich, emoji-enhanced message specifically structured for Slack's markdown. This data is then sent using the Send to Slack HTTP Request n8n node to the event's specified webhook URL.


5. Email Notification Path: If the channel is Email, the Format Email Code n8n node constructs a full HTML email body, complete with stylized countdown elements and a professional layout. The final message is dispatched using the Send Email n8n node, utilizing existing SMTP credentials.


6. Auxiliary Webhook Path: Separately, a Webhook Trigger n8n trigger is available to receive external event data, which is instantly processed and acknowledged via the Webhook Response n8n node.

To deploy this powerful n8n workflow, follow these steps:

1. Import: Copy the entire JSON code and paste it into your n8n instance via the 'Import from JSON' function.


2. SMTP Setup: Configure the Send Email n8n node with your required SMTP credentials. (The placeholder name is 'SMTP - test' and must be replaced).


3. Customize Event Data: Open the Events Database Code n8n node and update the events array with your actual event names, dates (in 'YYYY-MM-DD' format), types, and preferred communication channels ('slack' or 'email').


4. Slack Webhooks: If using Slack, ensure you replace the placeholder webhookUrl values in the event list within the Code n8n node with your actual Slack incoming webhook URLs.


5. Activation: Ensure the Schedule Trigger n8n trigger is correctly configured to run daily. Activate the n8n workflow to begin automation.

This n8n workflow utilizes several key nodes to manage scheduling, data processing, and multi-channel communication:

Schedule Trigger (n8n trigger): Sets the automation to run daily at 9:00 AM (0 9 ).
Events Database (Code n8n node): Acts as the data source and processor. It contains custom JavaScript to define events, calculate daysRemaining, and filter the list, ensuring only relevant events flow downstream in the n8n workflow.
Is Slack? / Is Email? (If n8n node): These flow control n8n nodes are essential for routing. They check the channel property of the processed event item to direct the payload to the correct formatting branch.
Format Slack Message (Code n8n node): Dynamically generates the Slack message text, applying emojis and urgency indicators (TODAY, TOMORROW) based on the event details. This prepares data for the subsequent HTTP Request n8n node.
Send to Slack (HTTP Request n8n node): The final communication step for Slack, executing a POST request to the pre-configured webhook URL found in the event item.
Format Email (Code n8n node): Builds a complete, responsive HTML body and appropriate subject line for email notifications, applying color coding based on event type and proximity. This complex logic is held entirely within this n8n node.
Send Email (EmailSend n8n node): Sends the fully formatted email using the configured SMTP credentials, completing the email path of the n8n workflow.