Keep confirmed member preferences with the account
A preference shared during a Flowise conversation can be recorded on the member profile, making it easier to honor without keeping another side note.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Member
Tool to update an existing member's information. use when you have a member id and need to modify their email, customfields, metadata, json data, or loginredirect.
Why this helps
Preferences are hard to carry forward when they remain buried in separate conversations.
- Store confirmed preferences alongside the membership record.
- Reduce reliance on personal notes and conversation history.
- Make future member interactions easier to personalize.
Setup
Build it in a few focused steps.
- 1Connect Flowiseai and Memberstack to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it.
- 3Give Notis one plain-language instruction to update the identified member's relevant custom field or metadata when Flowise confirms a preference.
- 4Select a Notis webhook trigger and a channel for run reports.
- 5Test with one real preference and confirm it is saved on the intended member.
Questions about this workflow
Which preferences are appropriate to store?
Choose preferences that your members expect you to use and that fit your existing Memberstack custom fields or metadata.
Does this need an existing member?
Yes. The workflow updates an existing account, so Flowise must provide enough information to identify it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Flowiseai to Memberstack. A trigger fires from one place; an action lands in another.
Flowiseai triggers
Memberstack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Member
Tool to create a new member in your application. use after gathering email, password, optional plans, custom fields, metadata, and redirect.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Member
Tool to permanently delete a member from your application. use after confirming you no longer need the member's data and have the member id.
Get Member
Tool to retrieve a specific member by id or email. use when you need to fetch member profile details for a given identifier (id or email). example: "get member mem sb 12345".
List Members
Tool to retrieve a paginated list of all members in your application. use when you need to iterate through members with cursor-based pagination.
List Plans
Tool to list all available membership plans. use when you need to retrieve plan ids and details before assigning or comparing plans.
Remove Free Plan
Tool to remove a free plan from an existing member. use after confirming the member's subscription status. example: "remove free plan pln sb 67890 from member mem sb 12345".
Update Member
Tool to update an existing member's information. use when you have a member id and need to modify their email, customfields, metadata, json data, or loginredirect.
Connect any two apps with Notis in the middle.
Flowiseai and Memberstack, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Memberstack.