Outcome sync
Use Change beside Sync mode, choose Leadpoet CRM Sync, and reconnect. Leadpoet then reads outcomes only for records linked to Leadpoet.
HubSpot integration
Connect Leadpoet with OAuth, choose how results are synced, and send new Leadpoet-generated leads to HubSpot safely.
What it does
The Marketplace connection automatically queues newly delivered Leadpoet-generated leads for HubSpot. Leadpoet checks the email before it creates a contact. Manually entered and imported leads are not sent automatically. You can optionally match or create a company, create a Leadpoet-managed deal, and read outcomes for Leadpoet-linked records.
Leadpoet does not update, overwrite, merge, archive, reassign, or delete your existing HubSpot records. Disconnecting starts token revocation. After Leadpoet confirms it, new scheduled work stops. Records already in HubSpot stay in place.
Setup
Configure
Use Change beside Sync mode, choose Leadpoet CRM Sync, and reconnect. Leadpoet then reads outcomes only for records linked to Leadpoet.
Select a default owner for new contacts. Company mode checks an exact domain to avoid duplicate companies. A customer-owned company stays read-only: Leadpoet does not attach contacts to it. New associations are allowed only between records Leadpoet created. If a needed permission is unavailable, reconnect to grant it before enabling the feature.
Turn on deal creation, select a pipeline and an open initial stage, and save. Leadpoet creates at most one managed deal for each eligible company opportunity.
Permissions
The required permissions support contact delivery and Leadpoet-owned contact properties. Optional permissions support owner selection and company creation. Company reads and deal scopes are conditional: a later reconnect requests them only when you select a mode that needs them.
oauthcrm.objects.contacts.readcrm.objects.contacts.writecrm.schemas.contacts.writecrm.objects.owners.readcrm.objects.companies.writecrm.objects.companies.readcrm.objects.deals.readcrm.objects.deals.writeLeadpoet currently supports HubSpot portals hosted in the United States only. A portal in another HubSpot region is rejected during installation before CRM data is pulled. This compatibility limit is not a promise that all service processing stays in one country; see the Privacy Policy for processing locations.
New eligible lead delivery is queued automatically. Background processing and HubSpot rate limits can delay delivery; check the connection and lead sync status before retrying. Disconnecting does not erase retained service or audit data. See the Privacy Policy for retention and access requests.
Disconnect
Open Account → Integrations → HubSpot, select Disconnect HubSpot, and confirm. Leadpoet starts token revocation through the integration workflow. After it confirms revocation, new scheduled work stops. Existing HubSpot records remain unchanged.
Uninstall
In HubSpot, open Settings → Integrations → Connected Apps. Open Leadpoet, choose Actions, and choose Uninstall. HubSpot revokes the refresh token. An access token issued before uninstall may remain usable until it expires. Leadpoet stops new scheduled work and shows reconnect required after a confirmed token check. Records already created in HubSpot remain in HubSpot.
Support
Email hello@leadpoet.com. Include your Leadpoet account email, HubSpot portal ID, time of the failed action, and any visible error reference. Do not send OAuth tokens, client secrets, or raw CRM exports.
Leadpoet keeps limited connection, consent, audit, and synchronized service data as described in the Privacy Policy. Contact support to request access, export, correction, or deletion.