HubSpot workflow action
Next year’s deal already exists.
- G12026The deal your rep just closed won.
- G22027Opened by the workflow action, seconds later.
- G32028And again, every year the account renews.
When a deal closes won, Deal Renewals opens the renewal for the following year — line items, amount, owner and associations carried over, whichever of them you tick, into the pipeline you choose. Both deals keep a record of the link, so the chain is still readable three renewals later.
Free for 5 renewals a month · needs Professional workflows
The gap you already found
Renewable deals: asked since 2016, refused in writing.
The Ideas thread for renewable and recurring deals opened in December 2016 and passed 484 votes. People were still adding to it in July 2026. The companion request — copy line items from one deal to another — got an answer from a HubSpot product manager in June 2026, and the answer was no. It had been no in October 2025 too.
| What HubSpot offers instead | Why it doesn’t close the gap |
|---|---|
| The “add line item” workflow action | Adds products from your catalogue. It cannot read the line items sitting on the deal you just won. |
| Contracts | Lives in Revenue Hub Professional and Enterprise. It is not coming down to the plan you are on. |
| Two deals in two pipelines, by hand | The workaround the community documented. Someone has to remember, every time, for every account. |
Against a deal cloner
A copy is not a renewal.
Duplicating a deal is the easy half. The half that decides whether you can report on renewals is the link between the two deals — and a clone doesn’t have one. It lands in the pipeline as a deal with a similar name and no memory.
| A cloned deal | A Deal Renewals renewal | |
|---|---|---|
| Where it came from | Nothing on the record says. | dr_parent_deal_id and dr_root_deal_id, on the deal, filterable. |
| The workflow runs twice | Two live deals, both forecast. | One deal — the action hands back the one it already made. |
| Renewal rate | Counted by hand, or not at all. | A filter on the lineage. Numerator and denominator are both in the CRM. |
| Three years in | Four unrelated deals with similar names. | One chain you can open from either end. |
We are not arguing the cloners are badly built. We are arguing that an orphan copy answers a smaller question than the one you asked.
What lands on the renewal
Copied, computed, or left alone.
| Property | On the renewal | How it gets there |
|---|---|---|
| dealname | ACME — Renewal 2027 | Rendered from your name template |
| amount | 12,000 | Copied as-is |
| closedate | +12 months | Computed from the source close date |
| hubspot_owner_id | Unchanged | Copied |
| deal_currency_code | Unchanged | Copied |
| Line items | 7 of 7 | Recreated on the renewal, never moved |
| Associations | Contacts, companies | Re-associated without writing to either |
| Pipeline and stage | The ones you pick | Chosen in the action, not copied — the renewal can start in a renewal pipeline |
| Custom properties | Not copied | The fields above and nothing else, on purpose |
Line items, amount, owner and associations are four checkboxes on the action, and HubSpot adds it with all four clear — tick the ones you want. Every field, in full →
Written on both deals
Every renewal knows where it came from.
Six properties the app adds to your deal object at install, in their own group, and then keeps filled in. They record the parent-child deal lineage, and they are ordinary deal properties — filter, report and roll up on them like any other.
- dr_parent_deal_id
- The deal this renewal came from.
- dr_root_deal_id
- The first deal in the chain, carried unchanged through every generation — one filter returns an account’s whole history.
- dr_generation
- 1 on the original deal, 2 on its renewal, and up from there.
- dr_renewal_deal_id
- Written back on the source deal, pointing at the renewal it produced.
- dr_lineage_key
- The same value as the root id, kept as its own field because list views are easier to build on something that means one thing.
- dr_created_by_app
- True on deals this action created. Useful when you are reconciling a pipeline by hand.
Your renewal rate is a saved filter
Deals with a generation above 1, over the deals that had one. No spreadsheet.
No duplicate renewals
Idempotence is built on the lineage, not on a timestamp. Re-enrollment, retries and a colleague re-running the workflow all land on the same deal.
The history is navigable
Open any deal in the chain and jump to its parent or its renewal by id.
Timing
Scheduled renewal creation — powered by your existing HubSpot workflows.
The action creates the renewal the moment your workflow reaches it, with the close date set the number of months ahead you choose. Which means you decide when it happens, with the steps you already use.
| When you want it | What you build |
|---|---|
| At close | Trigger on Closed Won, then the action. The renewal appears now, dated a term ahead. |
| Three months before expiry | Trigger on Closed Won, a native Delay step of 9 months, then the action. It appears when someone should work it. |
Behaviour you can rely on
Boring on purpose.
Running it twice creates one renewal
The action locks on the source deal and hands back the renewal it already made. Re-runs, retries and duplicate enrollments all land on the same deal.
The source deal keeps its line items
The renewal gets fresh copies. Nothing moves, and nothing on the source changes beyond its four lineage properties.
A partial copy says so
If HubSpot rejects some line items, the action reports how many landed instead of failing quietly or leaving a half-built deal.
Your CRM content never reaches our database
We store portal ids, deal ids and the id of the workflow that ran. Names, amounts, line items, contacts and companies pass through memory to build the renewal and are never written down.
Before you install
Two things to check first.
Deal workflows, which start at Professional
A custom workflow action can only be added to a deal-based workflow, and deal-based workflows are a Sales Hub Professional and Enterprise feature. On Starter there is nothing for this action to be dropped into.
A portal admin
Authorizing is one HubSpot screen and it needs admin rights. Nothing is created in your CRM until a workflow runs the action.
Free covers 5 renewals a month, per portal. Past that the action stops and says so in the workflow history rather than half-creating anything. Unlimited will be $19 a month — it is not live yet, and portals installed during early access keep the free tier for life.
Install it, then close a deal.
Add “Create renewal deal” to any deal workflow, point it at a pipeline and a stage, and the next one opens itself.
Install on your portalQuestions first — support@dealrenewals.com