HubSpot
Account authorization
Publisher activation and client authorization are required. Match the Attrival Lead ID and map deal stages and values before syncing.
Bring original lead sources and recorded results together in the client’s workspace. Choose the connection method that fits their account and your delivery workflow.
Illustrative workflow · Setup required
Connecting a CRM does not create its records or deliver leads by itself. Configure and check delivery separately.
Implementation status is shown below. A working connection also needs provider activation, your client’s account access and verified field mappings.
12 connections shown
Account authorization
Publisher activation and client authorization are required. Match the Attrival Lead ID and map deal stages and values before syncing.
Client API key
Connect the client’s account, match the Attrival Lead ID and map stages and values before syncing.
Client API key
Connect the client’s account, match the Attrival Lead ID and map stages and values before syncing.
Client API key
Connect the client’s account, match the Attrival Lead ID and map stages and values before syncing.
Client API key
Connect the client’s account, match the Attrival Lead ID and map stages and values before syncing.
Direct connection
Direct setup is pending provider access. A separately configured workflow bridge may be used where supported.
Direct connection
Direct setup is pending provider access. A separately configured workflow bridge may be used where supported.
Direct connection
Account setup and outcome sync are not available for this provider yet.
Direct connection
Account setup and outcome sync are not available for this provider yet.
Direct connection
Account setup and outcome sync are not available for this provider yet.
Direct connection
Account setup and outcome sync are not available for this provider yet.
Direct connection
Account setup and outcome sync are not available for this provider yet.
Lead delivery and outcome sync answer different questions. First confirm that the client received the lead. Then confirm that its result matches the original record.
Use a supported adapter with the client’s account, a stable Attrival Lead ID and configured stage/value mappings. Check sync health and matching before relying on the report.
An agency-owned integration can return an outcome from a supported webhook or automation workflow. This needs separate configuration and is not a native provider connection.
Authorized owners and editors can update manually managed leads. CRM-managed outcome fields remain protected; notes and follow-ups follow workspace permissions.
CRM connections are attached to a customer workspace. Each agency manages its own integrations and delivery destinations.
A workspace owner or authorized agency administrator sets up the client’s connection. Choose that client’s account and confirm the field mappings.
Carry the Attrival Lead ID into the client’s CRM record. Names and email addresses do not replace the matching identifier.
A report refresh reads recorded data; it does not certify that CRM sync succeeded. Review the connection’s health, failures and last successful sync separately. Reauthorize when the account requires it.
Google identity sign-in is separate from granting access to an agency’s library sources. Library authorization is restricted while public verification and review remain pending.
Restricted library flows read selected source documents and spreadsheets. They do not open general access to a client’s Drive or activate a CRM connection.
Restricted library flows read file metadata and source links. Rendered creative import is not included. General library signup awaits provider review.
Your library source and its permissions belong to your agency. Creating an agency does not grant access to another agency’s files or library.
No. Connection setup does not create CRM records or import every historical contact. Lead intake, delivery, matching and any guided import are separate steps.
Direct access is pending. A configured workflow bridge is a separate method; it does not make either provider a native connector.
General library signup remains restricted pending verification and review. Google sign-in for your identity is separate from library authorization.
CRM authorization belongs to the customer workspace. Configure each client’s account and matching fields within its own workspace.
Creating a workspace does not start a paid subscription.