HubSpot
Your customers' deals, contacts, and companies live in HubSpot. Askel connects to each customer's portal once, then keeps your product and their CRM in sync without any per-customer integration work on your end.
What you can do
Sync contacts, companies, and deals
Read and write HubSpot's core CRM objects. Askel resolves duplicates by email or domain and handles association between objects.
Map custom properties automatically
Askel fetches the customer's full property schema at connect time, marks high-confidence mappings, and flags any that need a human decision.
Trigger on deal stage changes
Run a workflow step whenever a deal moves to a specific pipeline stage, such as Closed Won or Contract Sent, across any of the customer's pipelines.
Write back activity and engagement records
Log calls, emails, and notes as HubSpot engagements tied to the right contact or deal, so the customer's team sees activity from your product inline.
Read list memberships
Check which HubSpot lists a contact belongs to and use that as a condition in onboarding rules, without pulling the full contact database.
Audit every read and write
Every API call Askel makes is logged with the object type, record ID, payload, and response. Your team can replay or inspect any operation.
Provisioning accounts when a deal closes in HubSpot
You sell project management software to agencies. A new customer, Brightside Creative, signs up after their sales team closes the deal in HubSpot. Their ops lead wants accounts, users, and billing details provisioned in your product the moment the deal reaches Closed Won, without any manual handoff between sales and onboarding.
- 1
Connect once
Brightside's HubSpot admin clicks Connect HubSpot inside your product. The OAuth consent screen opens on HubSpot, the admin approves the requested scopes, and Askel stores the refresh token.
- 2
Schema discovery
Askel reads Brightside's deal and contact properties, including custom ones like Contract Value (deal__contract_value) and Agency Tier (contact__agency_tier). A mapping draft appears in minutes.
- 3
Review the mapping
Two custom deal properties do not auto-map to your product's fields. Your CS rep opens the mapping editor, selects the correct targets, and saves with Brightside on a call.
- 4
Dry-run against recent deals
Askel pulls the last 20 Closed Won deals, runs the full mapping in read-only mode, and shows exactly which accounts would be created and which contacts would be invited.
- 5
Go live
Activate the workflow. Every new Closed Won deal now creates an account in your product, invites the primary contact, and writes a HubSpot note on the deal confirming provisioning.
OAuth 2.0
Customer's admin clicks Connect inside Askel and approves scopes on HubSpot's consent screen. Askel stores the refresh token. No tokens or client credentials are exposed to your codebase, and token refresh happens automatically in the background.
How Askel sits between your product and the customer's system
FAQ for HubSpot
Which HubSpot plans are supported?+
What scopes does Askel request during OAuth?+
Does this work with HubSpot sandbox portals?+
What happens if the customer renames or deletes a custom property?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.