Bidirectional Synchronization Between Freshdesk and Linear - n8n Workflow

• Companies using Freshdesk for customer support and Linear for development task management.


• Technical teams requiring seamless, real-time ticket-to-issue syncing.


• Automation specialists seeking advanced n8n templates involving complex data transformation.


• Users who need built-in logging and error management within their n8n workflow.

Maintaining data consistency between customer support systems (like Freshdesk) and internal project tracking tools (like Linear) is critical but often manual. This comprehensive n8n workflow solves this synchronization headache by creating a robust, bidirectional bridge. This specific n8n workflow template ensures that changes made in one platform are instantly reflected in the other, guaranteeing that development teams have the latest information and support staff can track progress accurately. This specialized n8n node setup includes custom field mapping logic for priority and status fields, making it far more reliable than standard integrations. Furthermore, the n8n workflow incorporates detailed logging for both success and error states, providing a high degree of auditability and ease of troubleshooting.

This powerful n8n workflow operates in two main synchronization paths, each initiated by a specific n8n trigger:

1. Freshdesk to Linear (Creation & Initial Sync)

1. Trigger: The process begins with the 🆕 New Ticket Webhook or 📄 Update Ticket Webhook n8n trigger, which captures ticket creation events from Freshdesk.


2. Mapping: The 🗺️ Map Freshdesk Fields to Linear function n8n node translates Freshdesk priority (1-4) and status (Open, Pending, Resolved, Closed) into Linear's specific state IDs and priority values. It also formats the title and description.


3. Linear Creation: The 🎯 Create Linear Issue n8n node uses an HTTP Request to perform a GraphQL mutation against the Linear API, creating the new issue.


4. Validation: The ✅ Check Linear Creation Success IF n8n node verifies the API response to confirm the issue was created successfully.


5. Linking (Success Path): If successful, the 🔗 Link Freshdesk with Linear ID HTTP Request n8n node updates the original Freshdesk ticket, embedding the Linear Issue ID for future bidirectional synchronization.


6. Logging (Success Path): The 🎉 Log Linear Creation Success n8n node records the successful operation details.


7. Error Handling (Failure Path): If Linear creation fails, the ❌ Log Linear Creation Error n8n node captures the response details for debugging.

2. Linear to Freshdesk (Update Sync)

1. Trigger: The 🎣 Linear Issue Updated Webhook n8n trigger captures changes made to Linear issues (e.g., status changes).


2. Reverse Mapping: The 📄 Map Linear to Freshdesk Fields function n8n node reverses the mapping, translating Linear states and priorities back to corresponding Freshdesk status and priority values. Critically, this n8n node extracts the necessary Freshdesk Ticket ID from the Linear issue description.


3. ID Check: The 🔍 Check if Freshdesk Ticket ID Exists IF n8n node ensures that a valid Freshdesk ID was extracted, preventing API calls with missing identifiers.


4. Update (Success Path): If the ID is found, the 🎫 Update Freshdesk Ticket HTTP Request n8n node updates the Freshdesk ticket via the REST API with the new status and priority.


5. Logging (Success Path): The ✅ Log Freshdesk Update Success n8n node logs the successful reverse synchronization event.


6. Error Handling (Missing ID Path): If the Freshdesk Ticket ID is missing from the Linear issue description, the ⚠️ Log Missing Ticket ID Error n8n node logs this failure.

To deploy this powerful n8n workflow, follow these steps:

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


2. Credentials Setup:

1. Workflow Variables: Navigate to the workflow settings or use the Environment Variables feature to define the following variables used by the n8n node configuration:

1. Webhook Activation: Copy the URLs generated by the Webhook n8n trigger nodes (create-ticket, update-ticket, linear-issue-updated).


2. Platform Configuration: Set up webhooks in your Freshdesk and Linear accounts, pointing to the respective n8n trigger URLs. Ensure Freshdesk sends POST requests for ticket creation/updates and Linear sends updates to the designated n8n trigger path.


3. Activate: Set the n8n workflow to 'Active' to start listening for incoming synchronization requests.

🆕 New Ticket Webhook / 📄 Update Ticket Webhook / 🎣 Linear Issue Updated Webhook
Function: These are the critical n8n trigger nodes that initiate the synchronization process upon specific events in Freshdesk (new/updated ticket) or Linear (updated issue).
Key Configuration: Configured to accept POST requests on specific paths (create-ticket, update-ticket, linear-issue-updated).
🗺️ Map Freshdesk Fields to Linear (Function n8n node)
Function: Transforms Freshdesk status (numerical codes) and priority into the corresponding Linear state IDs and priority numbers (1-4). This custom code logic is essential for data fidelity in this n8n workflow.
🎯 Create Linear Issue (HTTP Request n8n node)
Function: Executes the core Linear issue creation using a GraphQL mutation, authenticated via the Linear API key.
Key Configuration: URL set to https://api.linear.app/graphql. Uses Authorization header with the LINEARAPIKEY variable.
✅ Check Linear Creation Success (IF n8n node)
Function: Directs the n8n workflow flow based on the API response, ensuring subsequent linking steps only run if the Linear issue was created successfully.
🔗 Link Freshdesk with Linear ID (HTTP Request n8n node)
Function: Updates the originating Freshdesk ticket with the Linear Issue ID obtained from the previous step, establishing the required bidirectional reference.
📄 Map Linear to Freshdesk Fields (Function n8n node)
Function: Performs the reverse data mapping. It converts Linear state names (e.g., 'done') and priority back into Freshdesk numerical codes. Crucially, it uses regex to extract the Freshdesk Ticket ID from the Linear description field for accurate updates.
🔍 Check if Freshdesk Ticket ID Exists (IF n8n node)
Function: Verifies the existence of the Freshdesk ID extracted by the previous n8n node. If the ID is missing, the n8n workflow logs an error instead of attempting an update.
🎫 Update Freshdesk Ticket (HTTP Request n8n node)
Function: Handles the final synchronization step, updating the Freshdesk ticket status and priority based on Linear changes.
🎉 Log Linear Creation Success / ❌ Log Linear Creation Error / ⚠️ Log Missing Ticket ID Error / ✅ Log Freshdesk Update Success
Function: These Function n8n nodes manage comprehensive logging, providing audit trails and detailed information for tracking success and diagnosing failures throughout this complex n8n workflow.