When a new subscription or deposit is processed in RegFox, add the subscriber to a specific Mailchimp audience

When RegFox processes a new subscription or deposit, FlowMattic adds the person to the Mailchimp audience you choose, so paying registrants are on the list you use to email them.

RegFox

Mailchimp

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.6k sites Free to import

What this workflow does

Registrants who pay a deposit or start a subscription in RegFox are the people you most need to keep informed: schedules, balance reminders, what to bring. Copying them into Mailchimp by hand is easy to fall behind on. This workflow adds each one to a Mailchimp audience as their payment is processed.

The RegFox trigger runs on the New Subscription/Deposit Processed event. FlowMattic passes the registrant's details to Mailchimp, where Add New Member puts them in the audience you select. The template has no fields mapped, so after import you connect both accounts, pick the audience, and map the email address and name from the RegFox data.

The trigger follows payments, not people. If RegFox reports more than one processed payment for the same person, each one starts a run, and Mailchimp updates that registrant's existing member record with the mapped details rather than adding them twice. Registrations without a subscription or deposit don't start this workflow.

Retreats paid in instalments

Guests pay a deposit to hold their place. Each one joins the Mailchimp audience you use for packing lists, travel details and balance reminders.

Club or league memberships

Members who start a recurring subscription in RegFox are added to your members' audience in Mailchimp for season news and fixtures.

Camps that take a deposit up front

Families who pay the deposit for a summer camp join the audience that receives the parent information pack and updates.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
RegFox New Subscription/Deposit Processed
Runs when RegFox processes a new subscription or deposit. The registrant's details are passed to the Mailchimp step. Make a test payment to see which values arrive.
Step 2Action
Mailchimp Add New Member
Adds the registrant to your chosen Mailchimp audience as a new member. Connect your Mailchimp account, pick the audience and map the email address and name from the RegFox trigger.

What you need

FlowMatticCore
RegFox AccountAccount
Mailchimp AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Use one audience and separate events by tag or group inside Mailchimp, rather than creating a new audience for every RegFox event.
Add a Filter after the trigger if only some RegFox forms should feed this audience, using a value from a test payment that identifies the form or event.
Import the template a second time and point the copy at a different audience if two events need separate lists.

Questions about this workflow

Do free RegFox registrations get added to Mailchimp?

No. The trigger is New Subscription/Deposit Processed, so only registrations with a subscription or deposit start the workflow.

What if a RegFox registrant pays more than one deposit?

If RegFox reports each payment as its own event, every one starts a run. The Add New Member step then updates the registrant who is already in the audience, so they stay one member and the mapped details are refreshed.

Which Mailchimp audience do RegFox registrants join?

You set it yourself after import. The template leaves the audience empty until you connect Mailchimp and select one.

Are past RegFox payments added when I import the workflow?

No. Only subscriptions and deposits processed after the workflow is turned on are sent to Mailchimp.