To get started:
Create a copy of this sheet and send it to the customer. They will provide their Hubspot URL and their field names.
Set up the integration.
Setting up a Hubspot Integration via a Webform integration for leads:
HubSpot Integration through Integrate
We need the client to provide us with their Portal ID, Form ID, and list of their internal form names.
Once we have this information, we can create the Post URL: https://forms.hubspot.com/uploads/form/v2/yourPortalID/yourFormID
When creating the integration on the PeerSpot website, all is needed is the Post URL. The Portal ID and Form ID are 2 components that make up the Post URL.
Use this Google Sheet to collect the necessary field names and information.
Below are the exact CRM permissions (scopes) that we are requesting to be approved from the customer:
crm.schemas.contacts.read:
Purpose: To fetch API property names from the CRM.
Why: This is needed so that the system can understand the structure of the CRM's data and map its fields to the appropriate properties in the CRM.
Important Note: Despite the term "view CRM data," this permission only grants access to the structure/schema of the CRM, not the actual contact data.
crm.objects.contacts.write:Â
Purpose: To create contacts in the CRM.
Why: This permission is necessary for delivering leads, as the system needs the ability to add new contacts to the user's CRM account.
Important Note: HubSpot doesn't have separate scopes for creating, updating, or deleting contacts. Anyone with this permission can perform any of these actions. However, even though the permission implies the ability to create, delete, or update contacts, the explanation clarifies that the system only creates contacts and does not perform deletion or updates.
In summary, the first permission is about understanding the structure of the CRM data (no access to actual data), while the second permission is about creating contacts in the CRM (no updates or deletions are performed despite the implied scope).