Installation
Connect your HubSpot portal.
Authorizing takes one screen on HubSpot’s side and needs a portal admin. Nothing is created in your CRM until a workflow runs the action.
Connect HubSpotThree steps
What happens when you click.
- 01
HubSpot asks you to approve
You land on HubSpot’s consent screen with the scopes below. Pick the portal, approve, and you come straight back here.
- 02
Six properties are added to your deals
dr_parent_deal_id, dr_root_deal_id, dr_renewal_deal_id, dr_generation, dr_lineage_key and dr_created_by_app, in their own “Deal Renewals” group — put back if they ever go missing. No other object is touched.
- 03
The action shows up in your workflows
“Create renewal deal” appears in the action list of any deal workflow. Point it at a pipeline and stage, and you are done.
Scopes requested
Read wide, write narrow.
The app writes to deals and line items only. Contacts and companies are read so the renewal can be associated with the same records.
| Scope | What it is for |
|---|---|
| oauth | Issue and refresh the portal’s access token |
| crm.objects.deals.read · write | Read the source deal, create the renewal |
| crm.objects.line_items.read · write | Copy line items onto the renewal |
| crm.objects.contacts.read | Re-associate the same contacts — read only |
| crm.objects.companies.read | Re-associate the same companies — read only |
| crm.schemas.deals.write | Add the six lineage properties to your Deal object, and put them back if they go missing |
| automation | Register the workflow action on the portal |
Uninstalling from HubSpot cuts our access on the spot. HubSpot notifies no app of an uninstall, so we delete our copy of the tokens the first time a renewal is refused. What we store is listed in the privacy policy.