HubSpot and Salesforce
Coming soon
What it does
Both need a plan with CRM apps (see the pricing page), and an admin to connect them under Settings → Integrations. HubSpot asks for these permissions: oauth, crm.objects.contacts.read, crm.objects.contacts.write, timeline. Salesforce asks for: api, refresh_token. A Salesforce test environment connects through test.salesforce.com. Tokens are stored encrypted, refreshed before they expire and never shown.
- HubSpot: a contact is created, or updated when the email address is already known.
- Salesforce: a lead, or a contact if you choose, is created with its lead source set to Dotwick and an owner if you name one.
What creates a record
Saving a card to contacts is not a lead. The visitor saves your colleague to their own phone, so nothing is known about the visitor. The lead form is how a visitor’s details reach your CRM.
- An answer to a form code, or to a form block on a landing page.
- A business card lead: someone filled in the lead form on a card and ticked the consent line.
Map the fields
Choose which Dotwick value fills which property or field, up to 30 pairs. The values you can send are: email, firstName, lastName, fullName, phone, company, title, note, codeName, codeShortUrl, cardHolderName, cardHolderEmail, country, submittedAt. A custom Salesforce field is written with its API name, such as Source_Code__c.
Scans on the timeline
A scan reaches a record only when its code is tied to that record, for example a personalised code in a mailing, or when the scan produced the lead. HubSpot shows it as a timeline event, and Salesforce as a completed task. Anonymous scans are never sent.
If something fails
Each call is tried up to 5 times, and every attempt is listed under Settings → Integrations for 30 days. If the CRM refuses a refresh, the connection shows an error and your admins get one email.