FRESHDESK n8n INTEGRATION: AUTOMATE FRESHDESK WITH N8N

The "Create a contact" action allows you to automatically add new contacts to your Freshdesk help desk directly from your n8n workflows. This is essential for maintaining an up-to-date customer database without manual intervention.

Key parameters:

• Credential to connect with: Required dropdown to select your authenticated Freshdesk account for API requests.
• Resource: Set to "Contact" to indicate you're working with contact records.
• Operation: Set to "Create" for adding new contacts.
• Name: Text input field for the contact's full name—this helps your support team identify customers at a glance.
• Email: Required email input field (format: name@email.com) which serves as the primary identifier for the contact.
• Additional Fields: Expandable section where you can add optional properties like phone number, company, address, or custom fields specific to your Freshdesk setup.

Typical use cases:

• Automatically create a Freshdesk contact when a new customer signs up on your website
• Sync new CRM leads to your support system for proactive outreach
• Import contacts from form submissions (Typeform, Google Forms) directly into Freshdesk
• Create support contacts when new orders are placed in Shopify or WooCommerce

This action is ideal when you need to ensure every new customer or lead has a corresponding support profile ready before they ever submit their first ticket.

The "Get a contact" action retrieves detailed information about a specific contact from Freshdesk using their unique Contact ID. This is your go-to action when you need to fetch individual customer data for processing in subsequent workflow steps.

Key parameters:

• Credential to connect with: Required dropdown for selecting your Freshdesk account credential to authenticate the request.
• Resource: Set to "Contact" indicating the entity type being retrieved.
• Operation: Set to "Get" for fetching a single record.
• Contact ID: Required text input field accepting the unique identifier of the contact you want to retrieve. Supports expressions (indicated by the fx icon) for dynamic input from previous workflow nodes.

Typical use cases:

• Fetch contact details before sending a personalized email through SendGrid or Mailchimp
• Retrieve customer information to populate a support ticket response template
• Check contact properties before deciding which workflow branch to execute
• Pull contact data to update records in another system like Airtable or Google Sheets

Use this action when you have a specific contact ID (perhaps from a webhook or previous lookup) and need their full profile data—name, email, company, custom fields—for downstream processing.

The "Get many contacts" action retrieves multiple contact records from Freshdesk in a single API call, optionally filtered by specific criteria. This is essential for bulk operations and data synchronization workflows.

Key parameters:

• Credential to connect with: Required dropdown to select the Freshdesk account credential for authentication.
• Resource: Set to "Contact" to specify you're working with contact entities.
• Operation: Set to "Get Many" for retrieving multiple records.
• Filters: Expandable section with an "Add Filter" dropdown button where you can add filter criteria to narrow down results—for example, filtering by company, email domain, or custom field values. No filters configured by default, which returns all contacts (respecting pagination limits).

Typical use cases:

• Export all Freshdesk contacts to a Google Sheet for reporting or analysis
• Sync your entire contact database to a CRM on a scheduled basis
• Retrieve contacts matching specific criteria for targeted campaigns
• Audit your contact database for duplicates or incomplete records

This action is perfect for batch processing scenarios—whether you're running a nightly sync job, generating reports, or performing bulk updates across your contact database.

The "Update a contact" action modifies existing contact records in Freshdesk, allowing you to keep customer information current across your systems automatically. This is crucial for maintaining data integrity as customer details change over time.

Key parameters:

• Credential to connect with: Required dropdown for selecting your authenticated Freshdesk account.
• Resource: Set to "Contact" indicating the record type being modified.
• Operation: Set to "Update" for modifying existing data.
• Contact ID: Required text input accepting the unique identifier of the contact to update. Supports expression input for dynamic values from previous nodes.
• Additional Fields: Expandable section where you click "Add Field" to select which properties to update—name, email, phone, company, or any custom fields. Only the fields you add will be modified; others remain unchanged.

Typical use cases:

• Update contact email when a user changes it in your app's profile settings
• Sync company name changes from your CRM to Freshdesk
• Add phone numbers when customers provide them through support chat
• Update custom fields (like subscription tier or account status) when billing events occur

Use this action whenever you need to keep Freshdesk contacts synchronized with your source of truth—whether that's your CRM, billing system, or main application database.

The "Delete a contact" action permanently removes a contact record from Freshdesk. This is useful for maintaining a clean database by removing duplicates, test entries, or contacts who have requested data deletion (GDPR compliance).

Key parameters:

• Credential to connect with: Required dropdown to select the Freshdesk account credential for authentication.
• Resource: Set to "Contact" specifying the entity type to delete.
• Operation: Set to "Delete" for removing the record.
• Contact ID: Required text input field for the unique identifier of the contact to be deleted. Accepts string or expression input for dynamic specification.

Typical use cases:

• Automatically remove contacts when users delete their account from your platform
• Clean up test contacts created during development or QA processes
• Process GDPR "right to be forgotten" requests by triggering deletion workflows
• Remove duplicate contacts identified by a deduplication workflow

Important consideration: Deletion is permanent and may affect associated tickets and history. Use this action carefully and consider whether archiving or deactivating contacts might be more appropriate for your use case. Always test with non-production data first.