Back to Catalog

Sync Zendesk tickets with subsequent comments to Asana tasks

n8n Teamn8n Team
1060 views
2/3/2026
Official Page

This workflow creates an Asana task when a new ticket is created in Zendesk. Subsequent comments on the ticket in Zendesk are added as comments to the task in Asana.

Prerequisites

How it works

  1. The workflow listens for new tickets in Zendesk.
  2. When a new ticket is created, the workflow creates a new task in Asana.
  3. The Asana GID is then saved in one of the ticket's fields (in setup we call this "Asana GID").
  4. The next time a comment is added to the ticket, the workflow retrieves the Asana GID from the ticket's field and adds the comment to the task in Asana.

Setup

This workflow requires that you set up a webhook in Zendesk. To do so, follow the steps below:

  1. In the workflow, open the On new Zendesk ticket node and copy the webhook URL.

  2. In Zendesk, navigate to Admin Center > Apps and integrations > Webhooks > Actions > Create Webhook.

  3. Add all the required details which can be retrieved from the On new Zendesk ticket node. The webhook URL gets added to the “Endpoint URL” field, and the “Request method” should match what is shown in n8n.

  4. Save the webhook.

  5. In Zendesk, navigate to Admin Center > Objects and rules > Business rules > Triggers > Add trigger.

  6. Give trigger a name such as “New tickets”.

  7. Under “Conditions” in “Meet ALL of the following conditions”, add “Status is New”.

  8. Under “Actions”, select “Notify active webhook” and select the webhook you created previously.

  9. In the JSON body, add the following:

    {
    	"id": "{{ticket.id}}",
    	"comment": "{{ticket.latest_comment_html}}"
    }
    
  10. Save the Zendesk trigger.

You will also need to set up a field in Zendesk to store the Asana GID. To do so, follow the steps below:

  1. In Zendesk, navigate to Admin Center > Objects and rules > Tickets > Fields > Add field.
  2. Use the number field option and give the field a name such as “Asana GID”.
  3. Save the field.
  4. In n8n, open the Update ticket node and select the field you created in Zendesk.

Sync Zendesk Tickets with Subsequent Comments to Asana Tasks

This n8n workflow automates the process of creating and updating Asana tasks based on Zendesk ticket events, specifically focusing on new tickets and subsequent comments.

What it does

This workflow listens for incoming webhooks, processes the data, and then conditionally creates or updates tasks in Asana:

  1. Triggers on Webhook: The workflow starts when it receives a webhook, likely from Zendesk, indicating a new ticket or a comment.
  2. Processes Incoming Data: A Function node processes the incoming webhook data to extract relevant information such as the ticket ID, subject, comment body, and whether it's an initial ticket creation or a subsequent comment.
  3. Conditional Logic: An If node checks if the incoming event is a new ticket or an update/comment on an existing ticket.
    • If New Ticket: It creates a new task in Asana.
    • If Subsequent Comment: It updates an existing Asana task (presumably linked to the Zendesk ticket) with the new comment.
  4. Zendesk Interaction (Placeholder): A Zendesk node is present, but not connected in the provided JSON. In a complete workflow, this might be used to fetch additional ticket details or update the Zendesk ticket.
  5. Asana Interaction: An Asana node is present, but not connected in the provided JSON. In a complete workflow, this would be used to create or update tasks in Asana.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Zendesk Account: Configured to send webhooks to the n8n workflow's Webhook URL.
  • Asana Account: With appropriate permissions to create and update tasks.
  • Asana Credentials: Configured in n8n to allow the workflow to interact with your Asana account.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Webhook:
    • Open the "Webhook" node.
    • Copy the "Webhook URL".
    • In your Zendesk account, configure a webhook to send data to this URL whenever a new ticket is created or a comment is added to a ticket.
  3. Configure Asana Credentials:
    • Open the "Asana" node.
    • Select or create your Asana API credentials.
  4. Configure Function Node:
    • Review the JavaScript code in the "Function" node to ensure it correctly parses the incoming Zendesk webhook payload and extracts the necessary data for your Asana tasks. You may need to adjust field names based on your Zendesk webhook configuration.
  5. Configure If Node:
    • Review the conditions in the "If" node to ensure it correctly distinguishes between new tickets and subsequent comments based on the data processed by the "Function" node.
  6. Connect Asana Nodes:
    • For "If" True (New Ticket): Connect the "True" output of the "If" node to an Asana node configured to create a new task. Map the Zendesk ticket details (e.g., subject, description) to the Asana task fields.
    • For "If" False (Subsequent Comment): Connect the "False" output of the "If" node to an Asana node configured to update an existing task. You will need a mechanism to link the Zendesk ticket to the Asana task (e.g., storing the Asana task ID in Zendesk, or searching Asana for a task with the Zendesk ticket ID in its name/description). Map the new comment to the Asana task's comments or description.
  7. Activate the Workflow: Once configured, activate the workflow in n8n.

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

RapiwaBy Rapiwa
183

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.

Rahul JoshiBy Rahul Joshi
31

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

Nick CanfieldBy Nick Canfield
88