# Re-enrollment workflow after Optin

**URL:** <https://community.hubspot.com/t/re-enrollment-workflow-after-optin/116404>\
**Category:** HubSpot Ideas\
**Tags:** workflows\
**Created:** [September 16, 2024, 1:59pm UTC](https://community.hubspot.com/t/re-enrollment-workflow-after-optin/116404 "2024-09-16T13:59:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MatteoP](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@MatteoP](https://community.hubspot.com/u/MatteoP)\
**Post date:** [September 16, 2024, 1:59pm UTC](https://community.hubspot.com/t/re-enrollment-workflow-after-optin/116404/1 "2024-09-16T13:59:52Z")

</div>

Currently, Hubspot does not allow the re-enrollment of a contact in a workflow that uses the optin to a privacy subscription as a trigger.

When a user completes over time this sequence of preferences: **optin → optout → reoptin** for a specific privacy item, there is no way to managing actions in a workflow that monitors the status of the subscriptions.

The same happens when a user accesses the manage preference page to confirm their subscriptions (_i.e. consent expiring after a certain amount of time_). After saving the subscriptions, there is no possibility of triggering a workflow.

**BENEFITS:**

It would be useful implementing this functionality to allow automation management in all cases in which a user chooses to re-subscribe or confirm their choices to a privacy option.

I share two screenshots where you can see:

**1-** Using subscription changes as a workflow trigger.

**2-** History of subscription’s changes where you can see that HS already tracks the transition between optin and optout, but does not allow you to use this information.

 ![Trigger WF.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/4/0/408edfca7cd87f323bb7063bdd8246160368be92.png)

 ![](https://d2qpr2jzcazej7.cloudfront.net/original/3X/d/3/d3ed35ddedb93d7bf325a6e31346082deb389d81.png)

---

<div class="post-metadata">

**Author:** ![acamposeorhei](https://avatars.discourse-cdn.com/v4/letter/a/f4b2a3/32.png) [@acamposeorhei](https://community.hubspot.com/u/acamposeorhei)\
**Post date:** [September 27, 2024, 4:03pm UTC](https://community.hubspot.com/t/re-enrollment-workflow-after-optin/116404/2 "2024-09-27T16:03:04Z")

</div>

Hey there, Let me introduce myself as well and try to explain the issue.

**Subject: Subscription Type Re-Enrollment Issue**  
We are encountering the same issue with the re-enrollment process related to **Subscription Types within our CRM**.

A contact in the CRM should be able to **subscribe, unsubscribe, and re-subscribe** to a Subscription Type. Specifically:

- **SCENARIO 1** : Subscription to a Subscription Type – the contact **opts in** to “OFFERTE COMMERCIALI” (The name “OFFERTE COMMERCIALI” is just an example; this applies to any Subscription Type.)
- **SCENARIO 2** : Unsubscription from a Subscription Type – the contact **opts out** of “OFFERTE COMMERCIALI”
- **SCENARIO 3** : Re-subscription to a Subscription Type – the contact **re-opts** in (after previously unsubscribing) to “OFFERTE COMMERCIALI”

**In workflows,** it is possible to use the Opt-In and Opt-Out **statuses as triggers** (see attached image).

 ![Trigger WF.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/3/9/39173e43ad0825698cddf90a000777914b9e3438.png)

However, outside of workflows, the Subscription Type status can still be updated according to the scenarios above (Scenario 1, Scenario 2, Scenario 3).

The issue arises because, at the moment, **these updates to Subscription Type status are not being recognized by the workflows**.  
While re-enrollment is available for other contact properties, **it does not seem to apply to Subscription Type Opt-In status**. (See example with another subscroptiin type “Marketing Email”)

 ![Screenshot 2024-09-27 alle 17.54.49.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/d/0/d078bd520d4a2338d3e115a95e8aa6cd588c0934.png)

**This limitation excludes contacts** from workflows when they change their subscription status, leading to inaccurate data and disruption in our processes.

When will HubSpot release this update? Is it planned?

Thank you for your support!