Send your event data from RudderStack to Freshsales.
6 minute read
Freshsales is a CRM tool that lets you discover the best leads, drive them to closure, and nurture them to boost contextual engagement.
RudderStack supports Freshsales as a destination where you can seamlessly send your event data.
Getting started
Before configuring Freshsales as a destination in RudderStack, verify if the source platform is supported by Freshsales by referring to the table below:
Connection Mode
Web
Mobile
Server
Device mode
-
-
-
Cloud mode
Supported
Supported
Supported
To learn more about the difference between cloud mode and device mode in RudderStack, refer to the RudderStack Connection Modes guide.
Once you have confirmed that the source platform supports sending events to Freshsales, follow these steps:
From your RudderStack dashboard, add a source. Then, from the list of destinations, select Freshsales.
Assign a name to the destination and click Continue.
Connection settings
To successfully configure Freshsales as a destination, you will need to configure the following settings:
API Key: Enter your Freshsales API key.
For more information on obtaining your Freshsales API key, refer to the FAQ section below.
Domain: Enter the full organization URL associated with your Freshsales account. For example, testcompany.myfreshworks.com.
For more information on your organization URL and how to change it, refer to this Freshsales support guide.
Map your events with Freshsales Standard Events: Use this setting to map the standard Freshsales events with the custom event names.
Identify
You can use the identify call to create or update your Freshsales contact.
RudderStack uses the Freshsales Upsert a Contact API to pass the relevant user information via the following parameters:
Attribute
Type
Description
unique_identifier
String
RudderStack passes the user’s email.
contact
Hashed Object
RudderStack passes the other relevant user details required to create or update the user in Freshsales.
If email already exists, the contact details are updated. Otherwise, RudderStack creates a new user in Freshsales.
The track call can be used to track the user activities in Freshsales.
To make a track call successfully, you must map the event to be sent in the track call in the Map your events with Freshsales Standard Events dashboard setting.
RudderStack supports the following track events:
Lifecycle stage
Lifecycle stage events capture the decision journey of a customer. Refer to the Freshsales documentation to create lifecycle stages in Freshsales.
RudderStack lets you update the status of a contact in their lifecycle stage by using either the lifecycleStageId or lifecycleStageName.
lifecycleStageName is a case-sensitive field and throws an error if not used in the intended manner.
A sample track call for a lifecycle stage event is shown below:
The following table lists the property mappings betweeen RudderStack and Freshsales for lifecycle stage events:
RudderStack property
Freshsales property
email Required
email
lifecycleStageName Required, if lifecycleStageId is absent.
lifecycleStageName
lifecycleStageId Required, if lifecycleStageName is absent.
lifecycle_stage_id
Sales activities
Sales activities events can be used to track any activity related to a contact/deal/account. Refer to the Freshsales documentation to create sales activities in Freshsales.
RudderStack lets you create the status of a contact by using either the salesActivityTypeId or salesActivityName.
A sample track call for a sales activity event is shown below:
The targetable_type field denotes the entity for which the sales activity has been created and can take Contact/SalesAccount/Deal as its value. However, if its value is set to contact, then either the targetable_id or email is required.
Group
The group call lets you link an identified Freshsales contact with a company, organization, or an account. You can also record any custom group traits like the company name, number of employees, etc.
RudderStack passes the other relevant details associated with the Freshsales account.
Note that:
If name already exists, the Freshsales account details are updated. Otherwise, a new account is created.
RudderStack also checks if the contact’s email is present in the context.traits object. If yes, RudderStack links the contact to the Freshsales account.
A sample group call is shown below:
rudderanalytics.group("group01",{name:"Alex Keener",phone:"1234567890",numberOfEmployees:51,annualRevenue:10000,zipcode:90009,street:"6649 N Blue Gum Street",city:"New Orleans",state:"Louisiana",country:"USA"},{context:{traits:{email:"alex@example.com"}}});
Supported mappings
The following table lists the mappings between the RudderStack and Freshsales properties:
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.