Connect Salesforce with Freshdesk to sync contacts, accounts, and ticket updates, giving sales and support one view of every customer across teams.
• Freshdesk tickets are linked to Salesforce Accounts and Contacts via mapped identifiers such as email, external ID, or Freshdesk requester ID.
• Ticket fields (status, priority, type, group, agent, tags, and custom fields) are mapped to Salesforce objects/fields to support a consistent taxonomy.
• Salesforce case or custom object records can be created or updated from Freshdesk ticket events, with ownership rules applied to queues or users.
• Comments, public replies, and internal notes are synchronized as timeline entries based on direction rules, with author and timestamp preserved.
• Attachments are transferred as references or files depending on storage rules, with size limits and MIME types validated during processing.
• Sync jobs run as near-real-time webhooks where available, with scheduled delta sync as a fallback for missed or retried events.
• Error handling logs failed payloads, applies idempotency keys to avoid duplicates, and routes exceptions to an alerting channel for review.
.png)
We map Salesforce Accounts and Contacts to Freshdesk requester and company records, then sync ticket fields, statuses, and notes via API and webhooks. You decide what is bi-directional and what stays source-of-truth in Salesforce.
Typical sync includes contacts, accounts, ticket status, priority, tags, assignee, internal notes, and links to Opportunities or cases. We also support custom fields, so your workflows do not need to change to fit the integration.
Yes, we can connect multiple Freshdesk products and groups to one Salesforce org, or handle separate orgs where needed. The key is consistent ID mapping and rules for routing, ownership, and visibility.
We use deterministic matching rules, external IDs, and field normalization to avoid creating “new” requesters for existing customers. If the data is messy, we add a one-time cleanup and a validation layer to keep it stable.
Most builds take a few weeks once field mapping, permissions, and workflows are agreed. scandiweb has delivered 2,100+ projects since 2003, so we can move fast without skipping QA.





