WF02 · Continuation (Renewal) — Technical Reference
Triggers, properties, automations and integrations for the Continuation (Renewal) workflow.
Audience: HubSpot admins and workflow builders. This article covers the triggers, timing, branching, and properties behind the Continuation (Renewal) workflow. For a plain-language version, see WF02 · Continuation (Renewal) — Team Guide.
Version 1.0 · Last reviewed 2026-10-12 · Content owner: Aalishan Jami, Selina Genaro · Source: PGN HubSpot Workflow 2 spec
Workflow shape
Day -45 (notice) → Day -20 (decision form) → [Not Continuing | Continuing-Auto | Continuing-Personalized | No Response] → Day 0 (effective) → Day +1 (status finalized)
Trigger property: pinn_contract_end_date (Member End Date). All timing is relative to this date.
Step-by-step specification
| # | Step | Type | Timing | Logic |
|---|---|---|---|---|
| 1 | Notification #1 | Automation | End date − 45 days | Email to Mentor, cc Accounting. Sets pinn_continuation_status from Blank to Pending. |
| 2 | Notification #2 | Automation | End date − 20 days | Email to Mentor with a link to the HS decision form: Continuing or Not Continuing. Not Continuing requires a Reason Code (mandatory) and a Wrap-up date (mandatory). |
| 3 | Notifications #3–#12 | Automation | Daily, end date − 10 to − 1 days | Repeats Notification #2's content until a decision is submitted. |
| 4 | Notification #13 | Automation | On end date, no response | No-response offboarding notice. |
| 5 | Not Continuing branch | Automation | On decision | Adds the client to the Ending list; sets the Continuation Card status; sends an internal email to Accounting, Payroll, Mentor Team, and Support Team (cc Mentor). Feeds into Offboarding (Workflow 3). |
| 6 | Thank You Call | Manual · in HS | Due end date + 7 days | Owner: Luz Sellers / Support. |
| 7 | 12-Month Nurture Sequence | Automation | Enrollment-based | Owner: Marketing. A re-engagement/retargeting sequence, not a single email. |
| 8 | Continuing (auto-send) branch | Automation | Celebration Email at decision + 24 hrs | Adds the client to the Current list with the new end date. Celebration Email: From "[Mentor Name]" <support@pinnaclegn.com> (personalization token); cc Accounting/Payroll/Mentor Team/Support Team; bcc Mentor. |
| 9 | Continuing (personalized) branch | Automation | Decision + 24 hrs | Same list and date update. Instead of a client email, sends a reminder and template to the Mentor. |
| 10 | Ended status auto-set | Automation | End date + 1 day | If outcome = Not Continuing: set Membership Status = Ended and copy the reason code into the Membership Status Events log. |
Continuation Status state machine (pinn_continuation_status)
| From | To | When |
|---|---|---|
| Blank | Pending | Notification #1 sends |
| Pending | Continuing / Not Continuing | Mentor submits a decision (Not Continuing requires a reason code) |
| Pending | Not Continuing, reason = MIA | Auto-set the day after the end date if no response was received (Notification #13) |
| Continuing | Blank | Resets 1 day after the end date on either Continuing sub-path, clearing the field for next year's cycle |
| Not Continuing | (unchanged) | Stays as-is and feeds into Offboarding |
Reason codes
pinn_quit_code (labeled "Ended Code"): Achieved Goals, Bankruptcy, Business Change (Structure/Partnership), Cost (Membership), Cash Flow, Exit (Business), Fit (Program/Content), Personal Circumstances, Value, MIA (Offboarded).
Email sending mechanism
All mentor-facing client emails send from one verified address, support@pinnaclegn.com. The From Name is personalized with a token that pulls the mentor's name from the Contact/Mentor association, so no per-mentor mailbox is required
Related workflows
- Workflow 3: Offboarding & Dropping (entry point for Not Continuing)
- Workflow 5: Mentor Pay Review (pay stop when Membership Status changes to Ended)
Related: WF02 · Continuation (Renewal) — Team Guide. Questions or corrections? Contact the content owner listed above.