Trello Card Synchronization, Supabase Storage, and Telegram Alerts - n8n Workflow

• Teams using Trello for project management who require persistent data storage outside of Trello.
• Developers looking for advanced n8n templates integrating Supabase and Trello.
• Project managers needing automated, timely Telegram alerts for task deadlines.
• Users seeking a powerful, multi-step n8n node automation solution for DevOps or project operations.

Managing complex projects across multiple platforms can be challenging. This comprehensive n8n workflow solves the problem of decentralized task data and delayed communications by creating a robust synchronization layer.

It leverages the powerful capabilities of the n8n platform to monitor Trello events (new card creation, member additions, due date changes) in real-time. All relevant data—including card details, user information, and card-user relationships—is meticulously stored and maintained in a Supabase database. Furthermore, this n8n template includes a crucial scheduled n8n trigger that checks daily for tasks due today, ensuring the assigned members receive urgent, personalized notifications directly via Telegram. This integrated n8n solution ensures no deadline is missed and project data remains consistent across the stack.

This complex n8n workflow operates across three main logical branches:

1. New Card Creation & Webhook Setup

1. The process begins with the Trello Trigger n8n trigger, firing upon a new card creation event.


2. The 'Create card' Supabase n8n node inserts the basic card details into the Supabase cards table.


3. The 'Create Card Webhook' HTTP Request n8n node then dynamically registers a card-specific webhook with the Trello API. This ensures all future actions on that specific card are routed back to the main n8n webhook.

2. Real-time Trello Updates via Webhook

1. The primary Webhook n8n trigger receives real-time updates from Trello.


2. The flow branches: 'Update card due-date' synchronizes critical information like the due date and completion status into Supabase.


3. The 'Trello Action Type Check' and 'Add/Remove Member from Card Switch' n8n nodes analyze the action type (e.g., addMemberToCard).


4. If a member is added, the n8n workflow uses the 'Get user row' Supabase n8n node and the 'Does User Exist?' If n8n node to check if the user is already registered in the Supabase users table. If not, the user is created.


5. Custom JavaScript n8n node prepares the data, and the 'Create user card relation' n8n node establishes the necessary relationship in Supabase.


6. Finally, a customized, randomized Telegram message is generated using a Code n8n node and sent via the 'Send a text message' Telegram n8n node, notifying the user about their new assignment (or removal).

3. Scheduled Due-Date Notifications

1. The 'Due-Date Notification Schedule Trigger' is an essential n8n trigger that runs twice daily.


2. The 'Get all cards due today' Supabase n8n node fetches all tasks whose due_date matches the current date.


3. Subsequent Supabase n8n nodes ('Get user-card' and 'Get users in card') retrieve the associated users for these urgent tasks.


4. A Set n8n node maps the user's name to their Telegram username.


5. The final 'Send a text message1' Telegram n8n node sends a critical, highly formatted alert to the user, reminding them that their assigned task is due today. This proactive notification is a highlight of this particular n8n workflow.

To install and utilize this high-performance n8n workflow, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON data and import it directly into your n8n instance using the 'New' -> 'Import from JSON' option.


2. Set Up Trello Credentials: You will need a Trello API Key and Token. Configure the Trello credentials in the 'Trello Trigger' n8n node and ensure you replace placeholders like [BOARDID], [TRELLOTOKEN], and [TRELLOAPIKEY] as indicated in the Sticky Notes.


3. Configure Supabase Connection: Establish a connection credential for Supabase (Service URL and Anon Key). Ensure this credential is applied to all Supabase n8n node instances ('Create card', 'Get user row', 'Create user', etc.).


4. Database Schema: Verify that your Supabase instance includes the necessary tables: cards, users, and carduser with appropriate fields as referenced in the n8n nodes.


5. Telegram Integration: Configure your Telegram Bot credentials. Replace [TELEGRAMCHATID] in the Telegram n8n nodes.


6. Webhook Setup: In the 'Create Card Webhook' n8n node, replace [WEBHOOKURL] with the public URL of your primary 'Webhook' n8n trigger node. You must also set the [WEBHOOK_PATH] in the 'Webhook' n8n node.


7. Activate: Once all credentials and parameters are updated, activate the n8n workflow. The 'Due-Date Notification Schedule Trigger' will begin running immediately according to its schedule.

Trello Trigger (n8n trigger):
Function: Starts the workflow when a specific Trello board event occurs (e.g., new card).
Key Configuration: Uses Trello API credentials and requires manual configuration of the [BOARDID].
Webhook (n8n trigger):
Function: Acts as the dynamic listener for all card-specific updates triggered by Trello webhooks.
Key Configuration: Configured for POST method and requires a custom [WEBHOOKPATH].
Supabase (Create card, Get user row, Update card due-date, etc.):
Function: Central data management. These n8n nodes handle inserting new cards, checking user existence, updating due dates, and querying tasks due today.
Key Configuration: Utilizes the Supabase credential setup and interacts with tables like cards, users, and carduser using various operations (Insert, Get, Update).
If/Switch (Trello Action Type Check, Add/Remove Member from Card Switch):
Function: Core Logic Flow Control. Determines the execution path based on the incoming Trello action type (e.g., routing traffic for member addition versus member removal).
Code in JavaScript (n8n node):
Function: Used for complex data manipulation, including formatting dates, preparing bulk relationship creation data, and generating the customized, random Telegram notification messages using Markdown V2 escaping.
Telegram (Send a text message):
Function: Sends structured notifications to users regarding assignment status and urgent due-date reminders.
Key Configuration: Requires Telegram Bot credentials and the target [TELEGRAMCHAT_ID].
Schedule Trigger (n8n trigger):
Function: Initiates the due-date check routine at predefined intervals (configured here for every 12 hours). This is a vital n8n trigger for proactive alerts.