Workshop signups reach Drip
already tagged for follow-up.

For teams who run their email in Drip and take workshop registrations with a Gravity Form. The form asks for the person’s role and which session they picked; an Add Person feed writes those onto the person in Drip as a tag and a custom field and enrolls them in the pre-workshop workflow. A second feed records the signup as a named custom event with the session as a property.

See the plugins See how it works

Workshop signups Feed processed

One submission. Tag, field, event.

Marta Vinson marta@example.com

Tagged designer

Dev Okafor dev@example.com

Workflow joined

Priya Raman priya@example.com

Event recorded

Entry submitted → Person added in Drip

Illustrative experience

Add or update a person per feed
Tags mapped straight from form fields
Named events with their own properties

The finished experience

Nobody sorts the registration list by hand.

The role tag, the session custom field and the workflow enrollment are applied as the entry is saved, so the pre-workshop email goes to the right people before anyone opens Drip. The custom event carries the session name as a property, so Drip can segment and trigger on it.

A good fit for
Teams who run their email in Drip and take registrations, signups or leads through Gravity Forms.

1

Ask for the two things the segment needs.

The registration form collects name and email, the role the person works in, and which session they picked. Those last two answers are what the tag, the custom field and the event property are all built from.

GC Drip
2

Add the registrant with the role as a tag.

In Form Settings > Drip, add a feed with the Add Person action and map the Email field first — the docs call it the only required field to identify a person — then the name fields, and role and session as custom fields. In the same feed, map the role field under Tags, where a Checkbox or Multiple Choice field maps each value as its own tag, and pick the pre-workshop workflow under Workflows.

GC Drip
3

Record the signup as a custom event.

Add a second feed with the Record Custom Event action, name the event “Workshop registered”, and map the same Email field so Drip knows whose event it is. Under Drip Event Property Mappings, create a property for the session and map the session field to it.

GC Drip

Written up, step by step

How to Record Drip Custom Events in Gravity Forms How To · August 2025 Record custom events in Drip directly from Gravity Forms and magically expand your email marketing automations. Read the tutorial

How to Update People in Drip from Gravity Forms How To · June 2025 Update Drip people right from Gravity Forms—add them to workflows, update their personal info, and manage tags without lifting your wand. 🪄 Read the tutorial

How to Add People to Drip from Gravity Forms How To · May 2025 Automatically send contacts from Gravity Forms straight to Drip and bring marketing automations to your forms. Read the tutorial

What you’ll need.

Start with Gravity Forms. Add the capabilities this solution needs, then make the experience your own.

GC Drip

Maps each signup onto a person in Drip — details, custom fields, tags, workflow enrolment — and records the custom event, one feed per action.

Explore GC Drip

Taking it further

Add these optional plugins when your project calls for more.

Optional · Free

Feed Forge

Processes the feeds in bulk for signups collected before the feed existed.

Explore Feed Forge

Optional

GP Email Validator

Checks the address before it becomes a subscriber, so the list is not carrying typos and dead domains.

Explore GP Email Validator

Before you start

A Drip account at least 30 days old with API access, plus GC Drip. Connect the account in the Drip Connection settings with its Account ID and API token.
This is a one-way push: the form writes to Drip, and nothing from Drip is written back into a form field. Drip’s Time Zone property and Notes cannot be mapped, and an entry that was missed is reprocessed one at a time from its entry detail screen unless you add Feed Forge.

Get this built.

A plan covers how many of our plugins you run at once, and on how many sites. Here is what this one needs.

Required

GC DripConnect

Optional

Feed ForgeFree
GP Email ValidatorPerks

Gravity Connect Basic $59 /year

Covers this on one site. More sites need Advanced or Pro.

Gravity Perks Basic $59 /year

Only if you add GP Email Validator.

See plans for this solution

Every plan renews at the same price, and you can upgrade any time for the difference.

Make it fit
your project.

Can it update someone who is already in Drip?

Yes, that is the Update Person action, and it can add and remove tags and add and remove workflow enrollment in the same feed. It finds the person by the mapped Email field, which the docs call the only required field to identify a person.

Can I send registrations I collected before the feed existed?

Not from the Drip feed alone. A form with an active Drip feed gets an entry detail meta box that shows when the entry was processed and lets you process one that was not, an entry at a time; Feed Forge, free through Spellbook, adds a Process Feeds bulk action on the Entries page for doing it in batches.

The feed looks right and nothing reaches Drip. Where do I look?

Start with the entry notes, which report problems with the feed, then the Feed Logs button. Feeds run through Action Scheduler, which retries after temporary failures, so a stalled queue is the next place to check — and confirm the Drip account is more than 30 days old, since the API is closed before then.

Can we do this with MailPoet instead?

The tagging half, yes: a MailPoet feed can subscribe someone to a list and add tags on submission, behind the same conditional logic. What does not carry across is the custom event — that is Drip’s, and it is what lets Drip trigger on the fact someone signed up rather than on which tag they hold.