A HubSpot workflow can run five MemberArea actions: grant course access, grant product or bundle access, revoke access, add someone to a group, or create a checkout link. A closed deal unlocks the course. A cancelled subscription takes it away again. This article explains what each action needs and what it gives back.
Before you start
The actions need the Automation permission, which HubSpot includes from Professional upwards. If the MemberArea steps do not appear in your workflow editor, that permission is the first thing to check: open Settings, then Integrations, and expand HubSpot. The panel says so plainly.
Add a step in any contact-based workflow and look for MemberArea.
The five actions
Grant course access
Gives the contact access to one course. Needs the course ID.
Open the course in your memberarea and look at the address bar: the long id after
/admin/courses/ is the course ID.
The course has to be published. A draft course is never handed out, not even through a workflow, and the step stops with a message saying so. Publish it first.
Grant product or bundle access
Gives the contact everything a product contains, and for a bundle everything all of its products contain: courses, hubs, groups, events, community areas. Needs the Product or bundle ID.
Open the product in Payments, then Catalog, then Products. The
address then reads /admin/payments/catalog/products/<product ID>/edit.
Revoke access
The mirror image: takes away what a product or bundle grants.
Access the member paid for is never removed. If someone bought the course and later runs through a revoke workflow, the purchase wins and the step reports that nothing was taken away.
Add to group
Puts the contact into one of your groups. Needs the group ID from the address bar in Audience, then Groups.
The automatic "All members" group cannot be used here. Every member is in it already, so the step would have nothing to do.
Create checkout link
Builds a checkout link for a product and hands it back as an output field, ready for the next email or task in the workflow. Optionally with a specific price, a coupon code and campaign parameters.
Unlike the four above, this one changes nothing. It only produces a link.
The product has to be active and have an active price, and the workspace needs its own web address, because the link has to live somewhere. The step says which of the three is missing.
Members are created when they are missing
The three "grant" and "add" actions look the contact up by email address. If there is no member account for that address yet, they create one and then do their work, so a workflow does not fall over on a contact who has never signed up.
Revoke access and Create checkout link never create anyone. Revoke simply reports that there was no member, and the checkout link works with or without an account.
What comes back
Every action answers with fields you can use later in the same workflow. All of them except Create checkout link return:
Member emailandMember IDMember was created, orMember account foundon Revoke access- The name of what the step touched:
Course name,Product nameorGroup name - Whether anything actually changed, for example
Access was grantedversusMember already had access
Create checkout link returns the link, the price and the currency instead.
Branch on Member was created to send a "set your password" email only to the
people who really are new.
When an action fails
A failed step never stops the workflow silently. It writes one plain sentence into the workflow history that says what went wrong and what to do about it, and the workflow carries on. The troubleshooting article lists the messages you are most likely to meet.