CRM Integrations
Planhat’s CRM integrations rely on the ability to directly map data up to the Company. For this reason, fetching Companies from the source is never optional, in .
The sourceId on the Planhat Company receives the id from the source (be it Salesforce, HubSpot, or Pipedrive), and this ID is later used to map records from other models, to the correct Companies in Planhat. For this reason, a “system” association in the source data is necessary, between the Company and whichever child model or record you wish to fetch into Planhat.
The main CRM integrations are Salesforce, HubSpot, and Pipedrive.
Planhat’s CRM integrations rely on the ability to directly map data up to the Company. For this reason, fetching Companies from the source is never optional, in .
The sourceId on the Planhat Company receives the id from the source (be it Salesforce, HubSpot, or Pipedrive), and this ID is later used to map records from other models, to the correct Companies in Planhat. For this reason, a “system” association in the source data is necessary, between the Company and whichever child model or record you wish to fetch into Planhat.
The main CRM integrations are Salesforce, HubSpot, and Pipedrive.
Planhat’s CRM integrations rely on the ability to directly map data up to the Company. For this reason, fetching Companies from the source is never optional, in .
The sourceId on the Planhat Company receives the id from the source (be it Salesforce, HubSpot, or Pipedrive), and this ID is later used to map records from other models, to the correct Companies in Planhat. For this reason, a “system” association in the source data is necessary, between the Company and whichever child model or record you wish to fetch into Planhat.
The main CRM integrations are Salesforce, HubSpot, and Pipedrive.
Salesforce
Authentication: Oauth2
Bidirectional
Supports custom sync sections and field mappings
SourceId must be used as key for all Planhat Models with this field, otherwise externalId is used
Single field filtering is available for fetching, per sync section, and null values can be optionally fetched and sent
Sending data is near-instant, while fetching happens at a frequency of approximately 10-30 minutes
Read more about the Salesforce integration here.
Salesforce
Authentication: Oauth2
Bidirectional
Supports custom sync sections and field mappings
SourceId must be used as key for all Planhat Models with this field, otherwise externalId is used
Single field filtering is available for fetching, per sync section, and null values can be optionally fetched and sent
Sending data is near-instant, while fetching happens at a frequency of approximately 10-30 minutes
Read more about the Salesforce integration here.
Salesforce
Authentication: Oauth2
Bidirectional
Supports custom sync sections and field mappings
SourceId must be used as key for all Planhat Models with this field, otherwise externalId is used
Single field filtering is available for fetching, per sync section, and null values can be optionally fetched and sent
Sending data is near-instant, while fetching happens at a frequency of approximately 10-30 minutes
Read more about the Salesforce integration here.
HubSpot
Authentication: Oauth2
Bidirectional
Supports custom sync sections and field mappings
SourceId or ExternalId can be used as the key for each sync section - which one to use is optional
Single field filtering is available for fetching, while complex rules can be set up for sending data, for each sync section. Null values are also optional to fetch and send
Sending and fetching data is near-instant
Read more about the HubSpot integration here.
HubSpot
Authentication: Oauth2
Bidirectional
Supports custom sync sections and field mappings
SourceId or ExternalId can be used as the key for each sync section - which one to use is optional
Single field filtering is available for fetching, while complex rules can be set up for sending data, for each sync section. Null values are also optional to fetch and send
Sending and fetching data is near-instant
Read more about the HubSpot integration here.
HubSpot
Authentication: Oauth2
Bidirectional
Supports custom sync sections and field mappings
SourceId or ExternalId can be used as the key for each sync section - which one to use is optional
Single field filtering is available for fetching, while complex rules can be set up for sending data, for each sync section. Null values are also optional to fetch and send
Sending and fetching data is near-instant
Read more about the HubSpot integration here.
Pipedrive
Authentication: API token
Only fetches from Pipedrive to Planhat (except for the bidirectional sync between Planhat Company and Pipedrive Organization)
Only syncs select models, but supports custom field mapping
SourceId must be used as key for all Planhat Models with this field, otherwise externalId is used
Toggle is available between fetching only Companies and other data relating to Closed Won Deals, or fetching all Companies, regardless of Deal stages
Sending and fetching data is near-instant
Read more about the Pipedrive integration here.
Pipedrive
Authentication: API token
Only fetches from Pipedrive to Planhat (except for the bidirectional sync between Planhat Company and Pipedrive Organization)
Only syncs select models, but supports custom field mapping
SourceId must be used as key for all Planhat Models with this field, otherwise externalId is used
Toggle is available between fetching only Companies and other data relating to Closed Won Deals, or fetching all Companies, regardless of Deal stages
Sending and fetching data is near-instant
Read more about the Pipedrive integration here.
Pipedrive
Authentication: API token
Only fetches from Pipedrive to Planhat (except for the bidirectional sync between Planhat Company and Pipedrive Organization)
Only syncs select models, but supports custom field mapping
SourceId must be used as key for all Planhat Models with this field, otherwise externalId is used
Toggle is available between fetching only Companies and other data relating to Closed Won Deals, or fetching all Companies, regardless of Deal stages
Sending and fetching data is near-instant
Read more about the Pipedrive integration here.