CRM integration guide
Freshsales + UbiGrowth workflows
Freshsales is the Freshworks sales CRM, built around leads, deals, and activity tracking for growing sales teams. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Freshsales part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a CRM workflow around Freshsales with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Contact, Account, Deal, Task, Appointment, and Sales Sequence. Freshsales merges leads and contacts into a single Contact record, so there is no conversion event to hook. A workflow that expects a lead-to-contact transition has nothing to listen for.
Freshsales is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
Grow is the usual destination for this connection, because the value shows up as outreach, reply handling, scheduling, and pipeline execution against the connected records.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
The recurring failure with a Freshsales integration is not connectivity. It is that the CRM ends up holding a record of what someone remembered to log, while the work itself happened in an inbox, a call, a spreadsheet, and a separate AI tool that never saw the account.
When that gap exists, everything built on top of it inherits it. Forecasts describe logged activity rather than real activity, outreach is written without the reply history that would make it relevant, and the team spends its day reconciling systems instead of working accounts.
You're likely here because
- Pipeline data is only as current as the last time someone logged activity
- Outreach is generated without the account history that would ground it
- The same account context is rebuilt in several tools each day
Record model
What a Freshsales integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Freshsales's.
Identity and matching
Freshsales merges leads and contacts into a single Contact record, so there is no conversion event to hook. A workflow that expects a lead-to-contact transition has nothing to listen for.
Start here
Read Deals whose expected close date has passed with no Task or Appointment logged, and stage the reset conversation with the deal history attached.
What this will not do
It will not score deals meaningfully out of the box. Freshsales scoring reflects configured rules; a connected workflow should read the underlying activity rather than the score.
The constraint to plan around
Freshworks products share an account boundary but not a record model, so Freshsales and Freshdesk views of the same customer do not join without an explicit key.
Build notes
What you actually have to reason about in Freshsales.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| lead_score | computed from configured rules, so it encodes an opinion rather than an observation |
| deal_stage_id | pipeline position, configured per instance |
| sales_account_id | the account link, which is the only thing that aggregates contacts into a company view |
| updated_at | the incremental cursor, moved by automation as well as by people |
| territory_id | routing and visibility, and the reason two users see different pipelines |
Authentication
API key per user with a bundle-specific endpoint domain. Freshworks products share sign-in but not authorization, so a Freshdesk credential does not reach Freshsales even for the same person.
Events and delivery
Webhooks fire from workflow automations rather than as a raw change feed, which means an event exists only where somebody built a workflow to emit it. Absence of events is a configuration state, not a quiet system.
Workflow
How the Freshsales workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Read the pipeline as it stands
The workflow starts from live Freshsales accounts, contacts, and opportunities rather than an export, so prioritization reflects today's pipeline.
Step 02
Assemble the account context
Reply history, documents, and prior activity are brought together so the next action is grounded in what actually happened with the account.
Step 03
Decide the next action
ARIA proposes the specific next step for the account, with the supporting context attached, instead of producing a message with no stated reason.
Step 04
Execute through Grow
Outreach, reply handling, and scheduling run against the same record, staged for review while the motion is being proven.
Design decisions
The CRM decisions this connection forces.
Each of these has to be settled before the Freshsales workflow is allowed to write anything.
Step 01
Resolve the account identity
Decide how a person and a company are matched between Freshsales and the rest of the stack before any write happens. Most CRM integration damage is duplicate records created by a weak match rule.
Step 02
Keep execution attached to the opportunity
Outreach, replies, meetings, and stage changes should resolve back to the same opportunity, so the CRM reflects what actually happened rather than a parallel activity log.
Implementation path
How to implement the Freshsales workflow.
- 01
Decide which fields Freshsales owns and which the workflow may write, and write that decision down before enabling anything.
- 02
Define the identity match rule for contacts and companies, including what happens on an ambiguous match.
- 03
Start read-only. Prove that the workflow reads the right records before it is allowed to change any of them.
- 04
After stalled-deal detection works, add territory-aware routing so the reset conversation reaches the person who actually owns the account.
Governance
Controls that matter.
Control 01
CRM write scopes are limited to the specific objects the workflow needs, never blanket admin access.
Control 02
Duplicate creation is treated as a defect, not an acceptable side effect of syncing.
Control 03
Stage changes and closed-won updates stay under human control; automation prepares them rather than deciding them.
Failure modes
How a Freshsales integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
Contacts are duplicated against people sales is already working.
Cause
There is no lead-to-contact conversion event to deduplicate against.
Fix
Match on email and phone before creating, and route ambiguous matches for review.
Symptom 02
A Freshdesk credential returns unauthorised against Freshsales.
Cause
Freshworks products share sign-in but not authorization.
Fix
Issue product-specific credentials and store them separately.
Symptom 03
Expected webhook events never arrive.
Cause
Events originate from workflow automations, and none was configured for that change.
Fix
Create the workflow that emits the event, or poll — silence here is configuration, not quiet.
What changes at scale
Rate limits are per account per minute and vary by plan. Bulk operations are limited enough that large syncs should be scheduled off-peak rather than parallelised.
Examples
What a working Freshsales workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Lead management
With Freshsales connected, ARIA works from live account, contact, and opportunity records instead of an export, so prioritization reflects the pipeline as it stands today.
Grounded outbound
Grow drafts outreach against the account history already in Freshsales, so the message references what actually happened with the account rather than a generic template.
Limitations and considerations
What to validate before you depend on this.
- Freshworks products share an account boundary but not a record model, so Freshsales and Freshdesk views of the same customer do not join without an explicit key.
- Because there is no lead-to-contact conversion event, an integration that creates contacts directly can duplicate people the sales team is already working, with no conversion moment to deduplicate against.
- When the team needs deep customization. Freshsales trades configurability for simplicity, and pushing past that boundary produces workarounds rather than a system.
- If Freshsales data is incomplete, the workflow inherits that gap. Connected context is not automatically accurate context.
- Custom objects, custom fields, and heavily-customized permission models change what an integration can safely do; validate them against your own instance rather than the vendor default.
FAQ
Freshsales integration questions.
What records does a Freshsales integration actually work with?
The primary records are Contact, Account, Deal, Task, Appointment, and Sales Sequence. Freshsales merges leads and contacts into a single Contact record, so there is no conversion event to hook. A workflow that expects a lead-to-contact transition has nothing to listen for.
What should the first Freshsales workflow be?
Read Deals whose expected close date has passed with no Task or Appointment logged, and stage the reset conversation with the deal history attached.
What will a Freshsales integration not do?
It will not score deals meaningfully out of the box. Freshsales scoring reflects configured rules; a connected workflow should read the underlying activity rather than the score.
What is the main constraint to plan around?
Freshworks products share an account boundary but not a record model, so Freshsales and Freshdesk views of the same customer do not join without an explicit key.
What changes about a Freshsales integration at scale?
Rate limits are per account per minute and vary by plan. Bulk operations are limited enough that large syncs should be scheduled off-peak rather than parallelised.
How does authentication work for Freshsales?
API key per user with a bundle-specific endpoint domain. Freshworks products share sign-in but not authorization, so a Freshdesk credential does not reach Freshsales even for the same person.
Does Freshsales support webhooks, and can they be trusted?
Webhooks fire from workflow automations rather than as a raw change feed, which means an event exists only where somebody built a workflow to emit it. Absence of events is a configuration state, not a quiet system.
What is the risk of writing to Freshsales?
Because there is no lead-to-contact conversion event, an integration that creates contacts directly can duplicate people the sales team is already working, with no conversion moment to deduplicate against.
When is connecting Freshsales the wrong call?
When the team needs deep customization. Freshsales trades configurability for simplicity, and pushing past that boundary produces workarounds rather than a system.
What should a Freshsales integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Freshsales to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Will this create duplicate records in Freshsales?
Only if the identity match rule is weak. Define how people and companies are matched, and how ambiguous matches are handled, before enabling any write path.
Does Freshsales stay the system of record?
Yes. The design assumption is that Freshsales remains authoritative for the objects it owns and the workflow builds around it rather than replacing it.
Can pipeline stages be updated automatically?
Stage progression should stay under human control. Automation can prepare and propose the update, but deciding that a deal moved is a judgment call.
How this access is governed
What ARIA is allowed to do in Freshsales, and who decides.
Connecting Freshsales is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.