Once the app is connected, MemberArea shows up as its own category in the step catalogue of the flow builder. Every step is an action step: it runs, it answers, and the flow carries on with whatever it sent back.
How a step finds the right person
You never have to pass an id around. Each step receives the subscriber from ManyChat and looks the person up by the email address, first as a member, then as a contact. If the call carries no email address, or nobody in your memberarea has that address, the step falls back to the link an earlier step created for this subscriber.
Events run the other way round. They start from a person in your memberarea and search for the matching subscriber, so they follow their own order: the link first, then the email address, then the phone number.
The first step that touches a person also remembers the connection, so everything after it lands on the same member without asking again. That is why Save contact in MemberArea or Find person in MemberArea makes a good first step in a flow: after it, the rest of the flow knows who it is talking to.
The steps
Finding and saving people
- Save contact in MemberArea: creates the contact or updates the existing one, and remembers which subscriber it belongs to.
- Find person in MemberArea: answers whether this subscriber is a member, a contact or unknown, so your flow can branch.
- Create member: creates the account and hands back a login link that works without a password.
Tags, groups and fields
- Add tag and Remove tag: a tag can start an email sequence in your memberarea, so this is often the only step a simple flow needs.
- Add to group and Remove from group: automatic system groups cannot be changed.
- Set member field: writes a value into one of your member fields, for example a birthday or a goal.
Access and courses
- Grant access and Revoke access: gives or takes back everything that belongs to a product or a bundle. Revoking leaves the account in place.
- Enroll in course and Remove from course: only published courses can be picked, so the member always lands on real content. Removing keeps progress.
- Get course progress: reads how far the member got, so you can nudge exactly the people who stalled.
Selling and events
- Send checkout link: builds a personal checkout link with the email address already filled in.
- Get order status: reads the last order and the current subscription, ready to use in a message.
- Register for event: registers the person and answers with the local start time and the event link.
Everything else
- Start automation: starts one of your published automations for this person.
- Send member summary: answers with a finished message instead of single values. Membership state, course progress, last order and a login button, plus quick replies the subscriber can tap.
Dropdowns show your real data
Where a step needs one of your products, bundles, courses, groups, tags, fields, events or automations, the dialog offers a dropdown rather than a text field. ManyChat loads that list from your memberarea while the dialog is open, so you pick the real thing and cannot mistype an id.
Only items that are live are offered. A draft course or an inactive product does not appear.
Using what a step sends back
Every step answers with named values, and ManyChat lets you map each one into a custom field. Get order status hands back the order number, the amount as a number and the same amount already formatted with its currency, so a message can say "Your order ORD-1042 over 49,00 EUR is paid" without any string juggling.
The same pattern holds everywhere: where money or a date is involved you get both the raw value and a ready-to-read version. The raw date is there to compare against, the readable one is already written out in the language and the time zone of your memberarea, so it belongs in the message.
When a step cannot do the job
Steps answer in plain sentences, never in error codes, because whatever comes back can end up in the conversation. "This course is not published yet, so nobody can be enrolled. Please publish it in your MemberArea first." is a sentence you could put in front of a person as it is.
That also makes branching easy. Find person in MemberArea answers member,
contact or none in its Found value, and a condition step on that value is
usually the whole logic a sales flow needs.