Create a HubSpot CRM contact for each new RedPodium registration

Each new registration in RedPodium creates a contact in HubSpot CRM with the registrant’s details, so your team can follow up with event participants from the CRM they already use.

RedPodium

HubSpot CRM

Download this workflow Browse more workflows

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

The Create a HubSpot CRM contact for each new RedPodium registration workflow on the FlowMattic canvas, with 2 steps across RedPodium, HubSpot CRM — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Event registrations land in RedPodium, but follow-up often happens in HubSpot. Exporting registrant lists and importing them into the CRM is slow and easy to put off. This workflow creates the HubSpot contact for you as each registration comes in.

A fresh sign-up in RedPodium starts the run. The registration data is passed to HubSpot CRM, where the Create Contact action adds a contact with the email, name and other details you map.

Create Contact only creates contacts. If the same email address is already in HubSpot, for example a participant registering for a second event, HubSpot may refuse the duplicate, and Task History shows its response for that run. The RedPodium registration itself is not affected.

Race organisers building a participant list

Each runner who registers for your race in RedPodium appears in HubSpot, ready for pre-race emails and post-race surveys.

Sponsors and partner reporting

With registrants in HubSpot, you can build lists and reports on who signed up without exporting from RedPodium.

Clubs running a season of events

First-time registrants become HubSpot contacts you can invite to the next event in your series.

How this workflow runs

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

Step 1Trigger
RedPodium New Registrations
Runs when a new registration is created in RedPodium. The registrant's details from the event are passed on for mapping into HubSpot.
Step 2Action
HubSpot CRM Create Contact
Adds the registrant to HubSpot CRM as a new contact. Map the registrant's email address and name. HubSpot may refuse an email that already exists, which shows in Task History.

What you need

FlowMatticCore
RedPodium AccountAccount
HubSpot CRM 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.

Map the event or race name from the registration into a HubSpot contact property, so you can tell which event each contact came from.
Add a Filter after the trigger that continues only when the email field is not empty, so HubSpot is not sent a contact without an address.
Register a test participant in RedPodium after import so FlowMattic captures the registration fields, then map them in the HubSpot step.
If repeat participants are common, check Task History for refused duplicates and update those contacts in HubSpot yourself.

Questions about this workflow

What happens if the RedPodium registrant is already a HubSpot contact?

This template's HubSpot step only adds new contacts and never edits ones already there. HubSpot may refuse the duplicate email, and Task History shows the response. The existing contact is left as it is.

Are past RedPodium registrations copied to HubSpot?

No. Only registrations created after you turn the workflow on trigger it.

Which registration details can go into the HubSpot contact?

Any data the New Registrations event includes. Run a test registration to see the fields, then map them to HubSpot contact properties.

Does this send anything to the registrant?

No. It only creates the HubSpot contact. Any emails come from your own HubSpot setup.