FlowRunner
PricingContact
Theme
Start Free

Memberstack

Web Platform

Manage Memberstack members and plans from AI agents: sync new sign-ups as members, update custom fields and metadata, attach or remove free plans to control access, and look up members to drive downstream automation.

9 actions API key available
A sign-up form submission arrives from the Webflow site
Get Member checks whether the email already exists in Memberstack
Create Member registers the visitor with their custom fields filled from the form
Add Free Plan grants the starter plan that unlocks gated content
A Slack message tells the team a new member landed, with plan and source
A scheduled sweep later finds members whose CRM record shows a cancelled subscription
An operator reviews the cancellation list and confirms which members lose access before Remove Free Plan runs

What This Integration Enables

Memberstack is the access-control layer for sites built on Webflow and similar platforms, which means the member record is not just a contact, it is a key. Every write against it either opens or closes a door to paid content. FlowRunner agents work that layer directly: they create members from inbound sign-ups, keep custom fields and metadata aligned with the CRM, attach and remove free plans to control what each member can see, and page through the full membership base for sync and reporting jobs. - Register members from any upstream source: forms, checkouts, imports, referral flows - Grant and revoke gated access by attaching or removing free plans - Shallow-merge custom fields and metadata on Update Member so enrichment never clobbers what is already there - Look up any member by ID or email to branch downstream logic - Off-board members completely, including the linked Stripe customer and subscriptions, in one reviewed operation Because plan changes and deletions change what real customers can access, the destructive half of this connector belongs behind FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gates. Agents prepare the batch; a person approves the door closing.

Without FlowRunner

Membership is glued together by hand Sign-ups from forms, CRM updates, and access changes each require someone to touch the Memberstack dashboard
Access drifts from reality People keep gated access weeks after cancelling because revocation is a manual chore nobody owns

With FlowRunner

Sign-up to access is one motion A form submission becomes a member with the right plan attached before the visitor finishes reading the welcome page
The CRM and the membership base agree Custom fields and metadata sync both directions on a schedule, keyed on email
Off-boarding is deliberate, not forgotten Revocations and deletions run as a reviewed batch, with the Stripe cleanup handled in the same step

Use Case Scenarios

The sign-up pipeline that provisions itself

A visitor submits the sign-up form on a [Webflow](/integrations/webflow) site. The agent calls Get Member with the email to rule out a duplicate, then Create Member with the form's custom fields mapped in, then Add Free Plan for the starter tier. A welcome sequence kicks off in the email platform and a row lands in [Google Sheets](/integrations/google-sheets) for the weekly growth review. No one opens the Memberstack dashboard, and the visitor is reading gated content within the same minute.

CRM and membership base, reconciled nightly

Each night the agent pages through List Members with the JSON blob included, compares each record against [HubSpot](/integrations/hubspot), and calls Update Member where the CRM has newer data. Because custom fields shallow-merge, the sync adds what changed without erasing fields the CRM does not know about. Mismatches the agent cannot resolve, like two members sharing one CRM contact, go to a reviewer instead of being guessed at.

Cancellation off-boarding without the loose ends

When a subscription is cancelled in [Stripe](/integrations/stripe), the agent looks up the member, drafts an off-boarding summary, and posts it for review: member, plan, tenure, and whether to delete the linked Stripe customer. Once approved, Remove Free Plan closes access, and where the policy calls for full removal, Delete Member runs with the Stripe cleanup flags set. The membership base stays honest, and nobody keeps paying for infrastructure to serve members who left.

Human-in-Loop Highlight

Delete Member is the sharpest edge in this connector: it permanently removes the member and can take their linked Stripe customer and active subscriptions down with it, and the action cannot be undone. A churned-member cleanup agent therefore never fires it on its own judgment. It assembles the evidence, the cancellation event, the member's plan history, the Stripe objects that would be deleted, and posts the batch to an operator: "12 members cancelled more than 30 days ago. Deleting them also deletes 12 Stripe customers. Approve, or hold any for win-back?" Remove Free Plan gets the same treatment on a lighter gate, because revoking a plan locks a real person out of content they may believe they still own. The agent does the finding and the batching; a person decides whose key stops working.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

9 actions

Members

5
  • List Members Retrieves a paginated list of members with cursor-based pagination, sort order, and up to 100 per page. Include the JSON blob when a sync job needs the full picture.
  • Get Member Retrieves a single member by Memberstack ID or email, including auth details, custom fields, metadata, verification status, and active plan connections. The lookup step behind almost every branch.
  • Create Member Creates a new member with email, password or passwordless setup, optional free plans, custom fields, metadata, and a JSON blob. The write that turns a form submission into an account.
  • Update Member Updates an existing member by ID. Custom fields and metadata shallow-merge with existing values; the JSON blob is fully replaced when provided. The default write for CRM sync.
  • Delete Member Permanently deletes a member, optionally deleting the linked Stripe customer and cancelling active subscriptions. Cannot be undone; the operation this page's human gate exists for.

Plans

4
  • List Plans Retrieves all plans configured in the application, free and paid, with ID, name, status, and pricing. Run it first so workflows reference real plan IDs.
  • Get Plan Retrieves a single plan by ID with its name, description, status, pricing, and redirect configuration.
  • Add Free Plan Attaches a free plan to a member, granting access to everything gated behind it. The provisioning step after Create Member.
  • Remove Free Plan Removes a free plan from a member, revoking access to content gated behind it. Runs as part of reviewed off-boarding, not on a hunch.

Frequently Asked Questions

What can FlowRunner do with Memberstack?

FlowRunner agents can run List Members, Get Member, and Create Member in Memberstack, plus 6 more actions.

Does connecting Memberstack to FlowRunner require OAuth?

No. Memberstack connects to FlowRunner with an API key, no OAuth flow required.

Can Memberstack trigger a FlowRunner workflow automatically?

Memberstack doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Memberstack

$100 in credits. No card required. Connect in minutes.