Check for an existing account before following up
When Flowise spots signs that someone may already be a member, retrieve the matching account before you start a second signup conversation.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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".
Why this helps
Without a quick account check, returning members can be treated like new prospects and asked to repeat themselves.
- Check an identified account before continuing signup follow-up.
- Reduce duplicate conversations and repeated questions.
- Help returning members feel recognized sooner.
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 conversationally.
- 3Give Notis one instruction to retrieve the Memberstack account when Flowise flags a possible returning member and provides an ID or email.
- 4Choose a Notis webhook trigger and a channel for run reports.
- 5Test one real returning-member case and confirm the lookup identifies the expected account.
Questions about this workflow
Does this automatically prevent duplicate accounts?
No. It retrieves an identified account for review; decide the appropriate signup follow-up based on the result.
What does the lookup need?
Provide a member ID or email so Notis can retrieve the relevant Memberstack profile.
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.