ARMember
Overview
AFI captures membership events from the ARMember plugin and routes them to any receiver platform AFI supports — sync new members to your CRM, add them to a Mailchimp audience, drop them into a Slack channel, write them to a Google Sheet for accounting, etc.
Available triggers
AFI listens for the following events from ARMember. Each event runs as its own integration — you can have several integrations on the same plugin firing on different events.
- User Registered by ARForm
- User Updated by ARForm
- User Added by Admin
- User Cancelled Subscription
- User Plan Changed by Admin
- User Renewed Plan
Mappable fields
ARMember exposes every field on the member profile (first name, last name, email, phone, custom profile fields, and the plan/subscription metadata). The plan name, plan ID, and subscription status are all available so you can segment new members by tier on the receiver side.
Requirements
- ARMember (free or Premium) installed and activated.
- At least one ARMember plan/form configured.
Quick start
- In WordPress admin, go to AFI > New Integration.
- Trigger > Sender: pick ARMember.
- Event / Form: pick the specific event you want this integration to listen on (e.g. User Registered by ARForm).
- Pick a Receiver (e.g. Mailchimp, HubSpot, Google Sheets, Slack) and the desired task.
- Map ARMember fields onto the receiver’s fields. Use special tags (
{{_date}},{{_user_ip}}, etc.) for values not present in the form. - Optional: add Conditional Logic to control when the receiver is called.
- Save and run a test event to confirm the integration. Check AFI > Log if anything looks off.
Notes & caveats
- Cancellation events fire when a member cancels through the front-end account page; admin-side cancellations fire the Plan Changed by Admin event instead.
- Custom profile fields appear in the field-mapping dropdown only after at least one user has saved a value for them.
- Recurring renewals fire User Renewed Plan each cycle — useful for refreshing subscription status in your CRM.