Memberful

Manage your Memberful membership base from AI agents: list and look up members with their subscriptions and renewal state, create and update member records with custom metadata, discover plans, and run custom GraphQL for anything else.

7 actions API key available

Memberful website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

The weekly renewal review starts on schedule

List Members pages through the membership base with cursor pagination

List Subscriptions pulls each member's plan, renewal setting, and expiry

Members whose renewal is off and whose expiry falls inside the next 14 days are collected into the save list

The membership owner reviews the list with plan and tenure context and decides who gets a win-back offer versus a plain reminder

Update Member writes the campaign decision into each record's metadata

The reminder emails go out and the save list posts to the team channel with expected revenue at stake

What This Integration Enables

A membership business is a renewal business. The product, the content, the community all matter, but the number that decides the year is how many subscriptions renew, and the earliest signals live in Memberful: the renewal toggle, the expiry date, the plan. FlowRunner agents read those signals on a schedule instead of at the postmortem, sync the membership base into the systems the rest of the company works in, and write decisions back as metadata so the record itself carries the campaign history. - Sync members with their plans and renewal state into CRMs, spreadsheets, and warehouses - Gate access and trigger emails from a member's live subscription status - Create member records from external signups and stitch them to CRM identities via metadata - Discover plans and pricing before any workflow references them - Reach anything else in the API through Run GraphQL Query

Without FlowRunner

Churn discovered at expiry Members who switched renewal off surface in the numbers only after they are already gone

The member list lives in one tool The CRM, the email platform, and the spreadsheet each hold a different version of the truth

Metadata maintained by hand Tiers, CRM IDs, and campaign tags get applied manually, which means they mostly do not

With FlowRunner

Renewal risk surfaced in advance Expiring subscriptions are collected weekly with plan, price, and tenure attached, while there is still time to act

One membership base everywhere Members sync outward on cursors, not exports, so every system reads the same truth

Metadata as a working surface Agents keep up to 50 keys per member current, additively, without clobbering what other systems wrote

Use Case Scenarios

The renewal reminder that arrives while it still matters

A support reply, a community post, or a scheduled sweep raises a member's name. The agent calls Get Member, sees an annual subscription with auto-renew off and 12 days to expiry, and drafts a reminder through [Gmail](/integrations/gmail) that names their plan and what access lapses with it. Members with renewal on get nothing, because the fastest way to teach people to ignore your emails is to send ones that do not apply.

The membership base, everywhere it is needed

Nightly, the agent walks List Members with the cursor, pulling each member's subscriptions and plans, and updates the export in [Google Sheets](/integrations/google-sheets) and the contact records in [HubSpot](/integrations/hubspot). Finance reads subscription revenue by plan without asking anyone. Marketing segments by tier using metadata the agents keep current. The question "how many active members do we have" has one answer no matter who asks it.

Signups stitched across systems from day one

A signup lands through a partner funnel outside the normal checkout. The workflow calls Create Member with the email and name, then Update Member to store the originating CRM ID, the acquisition source, and the cohort tag in metadata. From that moment the member is one identity across Memberful, the CRM, and the analytics warehouse, instead of three records that someone reconciles at quarter end.

Human-in-Loop Highlight

Run GraphQL Query is the connector's open door: it executes arbitrary queries and mutations against the live Memberful account. Reads are routine. Mutations are not, because a mutation written by an agent can touch the thing this whole business runs on, real members' subscriptions and billing state, with no dedicated action's guardrails around it. So FlowRunner flows treat every mutation through this action as a proposal. The agent presents the exact GraphQL, the variables, and the members affected: "This mutation updates the renewal state on 3 subscriptions listed below. Execute?" The membership owner reads the operation, not a summary of it, and approves. The [human-in-the-loop](/concepts/human-in-the-loop) gate is what lets a team keep the escape hatch open without leaving it unattended.

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

7 actions

Members

List Members Retrieves the membership base a page at a time with email, name, username, and metadata, using cursor pagination for bases of any size. The backbone of every sync and audit.
Get Member Retrieves one member by ID with profile details and all subscriptions, including each plan's name, price, and billing interval. The lookup behind access gates and renewal checks.
Create Member Creates a member record with email and full name, returning the new ID. It does not start a paid subscription, which makes it the right first step for external signups.
Update Member Updates a member's metadata additively: omitted keys are preserved, and a key is deleted by setting it to an empty string. Up to 50 keys per member. The write that turns the member record into a cross-system identity.

Subscriptions and Plans

List Subscriptions Retrieves a member's subscriptions with active status, renewal setting, expiry, and plan detail. The renewal-risk signal source.
List Plans Retrieves every configured plan with name, price in cents, and billing interval. The reference step before any workflow points at a plan ID.

Escape Hatch

Run GraphQL Query Executes an arbitrary GraphQL query or mutation and returns the raw response. Covers custom field selections and operations the dedicated actions do not. The operation this page's human gate exists for.

Frequently Asked Questions

What can FlowRunner do with Memberful?

FlowRunner agents can run List Members, Get Member, and List Subscriptions in Memberful, plus 4 more actions.

Does connecting Memberful to FlowRunner require OAuth?

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

Can Memberful trigger a FlowRunner workflow automatically?

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

Start building with Memberful

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

Start Building Free Talk to us