Freshsales

Freshsales ETL connector for data replication

Snapshot

Features	Details
Release Status	Released
Source API Version
Table Selection	Yes
Column Selection	Yes
Edit Integration	Yes
Replication Type Selection	No
Authentication Parameters	Freshsales Subdomain API Key
Replication Type	Full Replication Key Based Replication
Replication Key	Date
Suggested Replication Frequency	24 hrs

Tables/APIs Supported
Leads	Contacts
Accounts	Appointments
Deals	SalesActivities
Tasks

Pre-requisites

1. Generate Freshsales API Key for Daton

2. Read more on Where to find Freshsales API Keys here

Integrate FreshSales with Daton

1. Signin to Daton

2. Select FreshSales from Integrations page

3. Provide Integration Name, Replication Frequency, and History. Integration name would be used in creating tables for the integration and cannot be changed later

4. Provide FreshSales Subdomain and API Key to authorize Daton to periodically extract data from FreshSales

5. Post successful authentication, you will be prompted to choose from the list of available tables

6. Then select all required fields for each table

7. Submit the integration

Workflow

1. Integrations would be in Pending state initially and will be moved to Active state as soon as the first job loads data successfully on to the configured warehouse

2. Users would be able to edit/pause/re-activate/delete integration anytime

3. Users can view job status and process logs from the integration details page by clicking on the integration name from the active list

FreshSales Data

Leads

Purpose: A lead is a prospect who has expressed interest in your product by signing up for a trial or subscribing to your newsletter etc.

Source API Documentation https://www.freshsales.io/api/#leads

Replication: Key-Based Replication

Replication Key: created_at

Fields

Name	Target Datatype
id	INTEGER
first_name	STRING
last_name	STRING
job_title	STRING
department	STRING
email	STRING
work_number	STRING
mobile_number	STRING
address	STRING
city	STRING
state	STRING
zipcode	STRING
country	STRING
lead_stage_id	INTEGER
lead_reason_id	INTEGER
lead_source_id	INTEGER
owner_id	INTEGER
has_authority	BOOLEAN
do_not_disturb	BOOLEAN
medium	STRING
campaign_id	INTEGER
keyword	STRING
facebook	STRING
twitter	STRING
linkedin	STRING
territory_id	INTEGER
company	RECORD
links	RECORD

Contacts

Purpose: Contacts represent the companies (Accounts) that you do business with

Source API Documentation https://www.freshsales.io/api/#contacts

Replication: Key-Based Replication

Replication Key: created_at

Fields

Name	Target Datatype
work_number	STRING
mobile_number	STRING
address	STRING
last_seen	STRING
lead_score	INTEGER
lead_quality	STRING
last_contacted	STRING
open_deals_amount	STRING
won_deals_amount	STRING
links	RECORD
last_contacted_sales_activity_mode	STRING
created_at	STRING
updated_at	STRING
keyword	STRING
medium	STRING
email_status	STRING
last_contacted_mode	STRING
recent_note	STRING
last_contacted_via_chat	STRING
won_deals_count	INTEGER
last_contacted_via_sales_activity	STRING
completed_sales_sequences	STRING
active_sales_sequences	STRING
web_form_ids	STRING
open_deals_count	STRING
last_assigned_at	STRING
facebook	STRING
twitter	STRING
linkedin	STRING

Accounts

Purpose: Companies with whom you have an existing business relationship are saved as Accounts in Freshsales. Usually one or more individuals (contacts) are associated to the account with whom you pursue sales opportunities

Source API Documentation https://www.freshsales.io/api/#accounts

Replication: Key-Based Replication

Replication Key: created_at

Fields

Name	Target Datatype
id	INTEGER
name	STRING
address	STRING
city	STRING
state	STRING
zipcode	STRING
country	STRING
industry_type_id	INTEGER
business_type_id	INTEGER
number_of_employees	INTEGER
annual_revenue	NUMERIC
website	INTEGER
phone	STRING
owner_id	INTEGER
facebook	STRING
twitter	STRING
linkedin	STRING
territory_id	INTEGER
created_at	STRING
updated_at	STRING
parent_sales_account_id	INTEGER
custom_field	STRING

Appointments

Purpose: Appointments are great way to meet with your prospects as attendees of appointments get notified about the time, venue and purpose of the meeting automaticaly

Source API Documentation https://www.freshsales.io/api/#appointments

Replication: Key-Based Replication

Replication Key: created_at

Fields

Name	Target Datatype
id	INTEGER
from_date	STRING
end_date	STRING
time_zone	STRING
title	STRING
description	STRING
creater_id	STRING
targetable_id	INTEGER
targetable_type	STRING
location	STRING
created_at	STRING
updated_at	STRING
is_allday	BOOLEAN
owner_id	INTEGER
appointment_attendees_attributes	STRING
outcome_id	INTEGER

Deals

Purpose: Deals are the expected sales opportunities from an account

Source API Documentation https://www.freshsales.io/api/#deals

Replication: Key-Based Replication

Replication Key: created_at

Fields

Name	Target Datatype
id	INTEGER
name	STRING
amount	NUMERIC
sales_account_id	NUMERIC
deal_stage_id	INTEGER
deal_reason_id	INTEGER
deal_type_id	INTEGER
owner_id	INTEGER
expected_close	STRING
closed_date	STRING
lead_source_id	INTEGER
campaign_id	INTEGER
deal_product_id	INTEGER
deal_payment_status_id	INTEGER
probability	NUMERIC
created_at	STRING
updated_at	STRING
territory_id	INTEGER
deal_pipeline_id	INTEGER
custom_field	STRING

SalesActivities

Purpose: Sales activities are a great way to track activities related to a lead/contact/deal/account. This comes in handy to get to know an entity's lifecycle

Source API Documentation https://www.freshsales.io/api/#sales-activities

Replication: Key-Based Replication

Replication Key: created_at

Fields

Name	Target Datatype
id	INTEGER
title	STRING
sales_activity_type_id	INTEGER
sales_activity_outcome_id	INTEGER
start_date	STRING
end_date	STRING
notes	STRING
owner_id	INTEGER
targetable_id	INTEGER
targetable_type	INTEGER
creater_id	INTEGER
created_at	STRING
updated_at	INTEGER

Tasks

Purpose: Sales activities are a great way to track activities related to a lead/contact/deal/account. This comes in handy to get to know an entity's lifecycle

Source API Documentation https://www.freshsales.io/api/#tasks

Replication: Key-Based Replication

Replication Key: created_at

Fields

Name	Target Datatype
type	INTEGER
title	STRING
description	STRING
due_date	STRING
targetable_id	INTEGER
targetable_type	STRING
owner_id	INTEGER
status	BOOLEAN
creater_id	STRING
created_at	STRING
updated_at	STRING
outcome_id	INTEGER
task_type_id	INTEGER