Skip to content
English
More support
Contact us
  • There are no suggestions because the search field is empty.

API integration with SubDNA

Project highlights

Paper Doc in progress:
https://paper.dropbox.com/doc/API-Hubspot-SubDNA--CA1u1XjDuhez_bJxqWu4QAXhAg-ZEOQyHdrZPOFLv7ELU9uL

 

Excel doc for field mapping. Include column for Use cases.

Ex: Billing routine amount: Used to generate $ amount for subscription renewal deals workflow.

 

Goal: Integrate SubDNA client information into HubSpot via API.

Timeframe: TBD – Kickoff May 19th.


To discuss:

GET function vs. Bi-directional sync.

Resources for building API – Internal (data team?), external (Kevin C., Upwork?)


Framework:

Utilize Client Service object in HubSpot. Associate Account Owner and Users. Associate Company.

Pull in subscription details into Client Service properties.

Update contact records for Owners and Users with primary details (name, job title, email, phone, etc.).

 

Kevin Coleman suggests that we build out exactly what we want from our end, and then he will work to make sure the information is accessible.

 

Issues:

  • If user gets deleted in SubDNA? Then no connection to update HubSpot.
  • If email address gets overwritten in SubDNA? Will it create new contact? Or linked via ID? So overwrites email of previous user?
  • Company changes are an issue. Need new company created and re-associated with SubDNA.

 

Things to think about:

  • Email domain changes. Shouldn’t be an issue, as change will overwrite current email. Or, will it create a new contact record?
  • Can we pull in SubDNA invoices? Can we associate them with Client Service object?

 

Via Kevin Coleman

We have done HubSpot integrations for several clients, but we pass all the subscriber information into Contacts, and any additional subscription related information was passed into custom contact properties.

Currently DNA does not have any GET end points.  We use a REST api, all default api end points support POST data, and api's support login, subscription details, registration, etc.

 

Please provide api details that you need and we can create custom end points for you.  For example:

GET- /group-owner 

this api may return json containing group owners like

first_name,last_name,email,subscription_star, expiry,status,lifetime payments,

etc

GET- /group-members

 group_owner_email,first_name,last_name,email