MemberPress
E-commerceConnect AI agents to MemberPress on your WordPress site. Agents onboard members, create transactions that grant plan access, and read membership, billing, and subscription data through the MemberPress REST API.
What This Integration Enables
For a content business on WordPress, access is the product. MemberPress holds the paywall, and its REST API, through the Developer Tools add-on, exposes the four objects that define the business: members, memberships, transactions, and subscriptions. FlowRunner agents work all four: they provision members with underlying WordPress accounts, read plan configuration and pricing, record transactions that grant access, and pull the billing and subscription data that answers revenue questions. - Onboarding: turn external payments, partner deals, and imports into provisioned accounts with access granted and verified - Reconciliation: every access grant recorded as a transaction, so the member list and the revenue ledger never disagree - Sync: members and billing activity flowing to [Google Sheets](/integrations/google-sheets), CRMs, and lifecycle email tools - Visibility: subscription status and transaction history read on demand for support and churn work Because Create Transaction with status complete literally opens the paywall, granting access is treated as what it is, giving away the product, and runs through a [human-in-the-loop](/concepts/human-in-the-loop) gate whenever it does not trace to a verified payment.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The funnel sale that ends with a working login
A buyer purchases through a [Stripe](/integrations/stripe) checkout on a landing page that never touches WordPress. The agent matches the email against List Members, runs Create Member for new buyers, and records the payment with Create Transaction against the right plan, status complete. Get Member confirms the membership is active, then [Klaviyo](/integrations/klaviyo) gets the profile and signup event so the welcome sequence starts with lifecycle context. The buyer's first email contains a login that already works, which is the entire difference between a membership site that feels professional and one that feels like a hobby.
A revenue picture that does not require wp-admin
Every night the agent pulls new records from List Transactions and List Subscriptions and appends them to the revenue workbook: amount, tax, gateway, status, member, and plan. Failed and refunded transactions land on their own tab with the member's history from Get Member attached. Active subscription counts by plan, from List Memberships and List Subscriptions, post to [Slack](/integrations/slack) each Monday. The founder answers "how did the membership do this month" from a sheet that was never stale, without logging into WordPress at all.
Support lookups and clean comps
A member writes in claiming they paid but lost access. The support agent asks the FlowRunner agent, which pulls Get Member for active memberships, recent transactions, and subscription state in one pass, and posts the full picture to the support thread. If the fix is a goodwill grant, the agent drafts the zero-dollar Create Transaction with an expiration matched to the request, and the owner approves it before access opens. The comp exists as a recorded transaction with a reason attached, so six months later nobody wonders why this account has free access.
Human-in-Loop Highlight
Create Transaction is the paywall key: a transaction with status complete grants the member access to the plan, immediately, whether or not money ever moved. That makes it the one action on this page that can give the product away at machine speed. A bug or a bad match list that enrolls a hundred people into the annual tier is revenue you do not get back, because access granted in error still gets consumed. So in FlowRunner workflows, transactions that trace to a verified external payment flow straight through, and everything else, comps, imports, partner bulk enrollments, price-mismatch cases, stops for the owner. The agent presents member, plan, amount paid versus plan price, and the reason, and a person decides who gets through the paywall. Update Member sits behind the same discipline when the field being changed is the email, because that field is the account's identity.
Agent Capabilities
11 actionsMembers
4- List Members Retrieves members with their profile, active memberships, transaction counts, and recent billing activity, searchable by email or username. The match step before any provisioning.
- Get Member Retrieves one member by WordPress user ID with full profile, active memberships, and recent transactions and subscriptions. The one-call answer to most support questions.
- Create Member Creates a member and provisions the underlying WordPress user account, generating a password when none is supplied.
- Update Member Updates a member's name, email, website, or password; only supplied fields change.
Memberships
2- List Memberships Retrieves the site's membership plans with pricing, billing period, trial settings, and access rules.
- Get Membership Retrieves one plan's full configuration: pricing, billing and trial periods, renewal and expiration rules. The price check before any enrollment.
Transactions
3- List Transactions Retrieves payment records filterable by member or membership, with amount, tax, status, gateway, and timestamps. The revenue feed.
- Get Transaction Retrieves one transaction's full payment record with its associated member and membership.
- Create Transaction Creates a payment record that grants a member access to a membership; status complete opens the paywall. The action this page's human gate exists for.
Subscriptions
2- List Subscriptions Retrieves recurring billing agreements filterable by member or membership, with status, gateway, period, and totals. The churn watchlist.
- Get Subscription Retrieves one subscription's status, gateway, price, billing period, and its member and plan.
Frequently Asked Questions
What can FlowRunner do with MemberPress?
FlowRunner agents can run List Members, Get Member, and Create Member in MemberPress, plus 8 more actions.
Does connecting MemberPress to FlowRunner require OAuth?
No. MemberPress connects to FlowRunner with an API key, no OAuth flow required.
Can MemberPress trigger a FlowRunner workflow automatically?
MemberPress doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with MemberPress
$100 in credits. No card required. Connect in minutes.