Bidirectional ClickUp task & Google Calendar sync with multi-calendar routing
Who’s it for
Teams that manage tasks in ClickUp and want those tasks reflected—and kept in sync—in Google Calendar automatically.
How it works
A ClickUp Trigger captures task events (create, update, delete). For new tasks, the workflow creates a Google Calendar event with the correct start/end. It stores a mapping between clickupTaskId and calendarEventId in a Google Sheet so later updates and deletions can target the right event. Multiple lanes (personal/school/tech/internship) let you route tasks to different calendars.
How to set up
- Assign ClickUp OAuth, Google Calendar, and Google Sheets credentials to the nodes.
- Open the Configuration node and fill:
calendarId_*for each lanesheetIdandsheetTabNamefor the mapping sheet- (optional)
clickupTeamId
- Enable the ClickUp Trigger and run a manual test to validate mapping creation and event syncing.
Requirements
- ClickUp workspace with OAuth permissions
- Google Calendar & Sheets access
- A Google Sheet for the event↔task mapping
How to customize the workflow
- Edit the calendar routing in Edit Fields nodes or point them to different
calendarId_*values. - Adjust event colors/fields in Google Calendar nodes.
- Extend the mapping sheet with extra columns (e.g., status, labels) as needed.
Bidirectional ClickUp Task & Google Calendar Sync with Multi-Calendar Routing
This n8n workflow provides a robust solution for synchronizing tasks between ClickUp and Google Calendar, supporting bidirectional updates and intelligent routing to multiple Google Calendars based on task attributes. It ensures that your tasks and events are always up-to-date across both platforms.
What it does
This workflow automates the following processes:
- ClickUp Task Trigger: Listens for new tasks or updates in ClickUp.
- Google Sheets Lookup: Queries a Google Sheet to determine which Google Calendar to use for synchronization based on task data (e.g., a specific tag or custom field).
- Conditional Routing: Uses an
Ifnode to check if a matching calendar is found in the Google Sheet. - Google Calendar Event Management:
- If a matching calendar is found, it creates or updates an event in the designated Google Calendar.
- If no matching calendar is found, it can route to a default calendar or skip the Google Calendar action.
- Data Transformation: Utilizes
Setnodes to format data appropriately for each service. - Merge Paths: Combines different execution paths back together for a cleaner workflow structure.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- ClickUp Account: With an API key configured as an n8n credential.
- Google Calendar Account: With OAuth2 credentials configured in n8n, granting access to create, update, and delete events in your calendars.
- Google Sheets Account: With OAuth2 credentials configured in n8n, granting access to read from your routing spreadsheet.
- Google Sheet: A spreadsheet containing your routing logic (e.g., mapping ClickUp tags/fields to Google Calendar IDs).
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Set up your ClickUp API Key credential.
- Set up your Google OAuth2 credential for Google Calendar and Google Sheets. Ensure it has the necessary scopes for both services.
- Configure ClickUp Trigger (Node 130):
- Select your ClickUp credential.
- Choose the ClickUp Space, Folder, List, or Workspace you want to monitor for task changes.
- Specify the events you want to trigger the workflow (e.g.,
Task Created,Task Updated).
- Configure Google Sheets (Node 18):
- Select your Google Sheets credential.
- Specify the Spreadsheet ID and Sheet Name that contains your calendar routing information.
- Ensure the sheet has columns that can be used to map ClickUp task data to Google Calendar IDs.
- Configure Google Calendar (Node 317):
- Select your Google Calendar credential.
- Configure the operations (e.g.,
Create Event,Update Event) and map the data from ClickUp and the Google Sheet to the appropriate Google Calendar event fields (summary, description, start/end times, calendar ID).
- Customize Routing Logic (Node 20 - If, Node 112 - Switch):
- Adjust the conditions in the
Ifnode (Node 20) to match your Google Sheet lookup results. - If you have complex routing to multiple calendars, customize the
Switchnode (Node 112) to direct tasks to different Google Calendar actions based on the calendar ID retrieved from the Google Sheet.
- Adjust the conditions in the
- Activate the Workflow: Once configured, activate the workflow to start synchronizing tasks.
Note on Bidirectional Sync: While the workflow description implies bidirectional sync, the provided JSON only shows a ClickUp Trigger and Google Calendar actions. To achieve full bidirectional sync, you would need a separate Google Calendar Trigger that detects new/updated events and then creates/updates tasks in ClickUp, potentially using a similar routing and lookup mechanism. The current workflow focuses on ClickUp to Google Calendar sync.
Related Templates
Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API
Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen
Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack
📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.
Automate Gmail responses with GPT and human-in-the-loop verification
Try It Out! This n8n template uses AI to automatically respond to your Gmail inbox by drafting response for your approval via email. How it works Gmail Trigger monitors your inbox for new emails AI Analysis determines if a response is needed based on your criteria Draft Generation creates contextually appropriate replies using your business information Human Approval sends you the draft for review before sending Auto-Send replies automatically once approved Setup Connect your Gmail account to the Gmail Trigger node Update the "Your Information" node with: Entity name and description Approval email address Resource guide (FAQs, policies, key info) Response guidelines (tone, style, formatting preferences) Configure your LLM provider (OpenAI, Claude, Gemini, etc.) with API credentials Test with a sample email Requirements n8n instance (self-hosted or cloud) Gmail account with API access LLM provider API key Need Help? Email Nick @ nick@tropicflare.com