Your AI Connector Docs

MemberPress

Who is this for? Businesses selling memberships, courses or paid communities through MemberPress on their own WordPress site. If you don’t use MemberPress, you can skip this page.

Use a different membership tool? Anything with an API can still be connected: see Connecting a Tool We Do Not List.

MemberPress is the WordPress plugin that sells and gates memberships: members, the memberships they hold, their subscriptions and their payments. Connecting it to Your AI Connector gives your automations steps that read a member’s standing and grant a membership, so your AI agent can answer “what am I signed up for” from the real record, and a new buyer can be let in without anyone opening WordPress.

Nothing is installed on your WordPress site beyond MemberPress’s own add-on, described below. You connect your own site with your own API key.

Availability: Automations is available on every account. It’s already in your sidebar, and there’s nothing to enable or request.

What You Need

  • MemberPress on a WordPress site reachable over https, with pretty permalinks switched on (Settings → Permalinks, anything other than “Plain”), which is what makes the /wp-json/ address work.
  • MemberPress’s Developer Tools add-on, which is what turns its API on. It comes with MemberPress’s higher plans, so if you cannot find it, that is the thing to check first.
  • The API key it gives you: in WordPress, MemberPress → Developer Tools → API key.

Connecting MemberPress

You connect from inside an automation, the first time you use a MemberPress step.

  1. Open Automations in the sidebar (under the AI Studio group) and open or create an automation.
  2. Add a step and search for MemberPress in the step picker.
  3. Pick the action you want. The step asks you to connect first.
  4. Fill in the two fields:
    • Site URL is the address of the WordPress site MemberPress runs on, starting with https://.
    • API key is the key from MemberPress → Developer Tools.
  5. Click connect.

We check the key against your site before saving anything. A wrong address, a wrong key, or Developer Tools not being active is refused on screen with the reason, so you never get a connection that looks fine and fails the first time the automation runs. Your API key is stored encrypted and never shown back to you. Lost it? Generate a new one in MemberPress and connect again.

The Actions

Each action is a step on the automation canvas, and every field accepts data from earlier steps with the usual insert-data buttons.

Get member

Fetches one member: their profile and the memberships they hold.

  • Member ID is which member. Required.

Find member by email

Looks a member up by email address, and returns their id.

  • Email is the address to look up. Required, and usually the contact’s email from the trigger.

This is the step that turns an email address into the member id the other steps need.

Create member

Creates a member account. It does not give them a membership on its own; Create transaction is what does that.

  • Email is their email address. Required.
  • Username is the name they will sign in with. Required.
  • First name and Last name are optional.
  • Password is optional, and best left empty: MemberPress generates one and the member can reset it from your login page. Anything you type here is saved with the automation. The field is masked.

List a member’s subscriptions

Every subscription belonging to one member, newest first.

  • Member ID is which member. Required.

List a member’s transactions

Every payment belonging to one member, newest first.

  • Member ID is which member. Required.

Create transaction

Records a payment, which is how MemberPress grants a membership.

  • Member ID is who gets it. Required.
  • Membership ID is what they get: the id of the membership from MemberPress → Memberships. Required.
  • Amount is what was paid. Optional.
  • Status decides whether it counts: complete is what grants access, and that is what it uses when you leave the field empty.
  • Expires at is when access ends, written as a date and time, for example 2027-01-31 23:59:59. Leave it empty for a grant that doesn’t expire.

An Example Automation

Answer a member’s own questions from the real record.

  1. Trigger: your AI agent calls this automation as a tool when someone asks about their membership. (Add the automation as an AI Agent Function and the agent can run it mid-conversation.)
  2. Find member by email, with the contact’s email.
  3. List a member’s subscriptions, using the id from step 2.
  4. The results go back to the agent, which answers in plain words: which membership, active or not, and when it renews.

And the other direction: let someone in after they pay.

  1. Trigger: a Webhook, pointed at by whatever took the payment.
  2. Find member by email. A Condition step branches on whether they exist.
  3. If not, Create member with their email and a username.
  4. Create transaction with their member id, the membership id you are granting, the amount, and an Expires at if the access is for a fixed period.
  5. A Send message step tells them on WhatsApp that they are in.

Good to Know

  • Steps that take a member ID come after a Find step. Find the member by email first, then hand the id to the next step.
  • Outputs travel forward. Everything an action returns is available to later steps as variables.
  • A membership is granted by recording a payment. That is how MemberPress itself works: Create member makes the account, Create transaction with a complete status is what opens the door.
  • There is no trigger that watches MemberPress. Nothing polls it for new members or new payments. To have MemberPress start an automation, add a Webhook trigger to the automation and point a MemberPress webhook at the address it gives you.
  • The API needs the Developer Tools add-on. Without it there is nothing on your site for us to talk to, however right the rest of your details are.
  • Anything not on the list above can still be done with the HTTP request step.

Next Steps