How to Add People to Drip from Gravity Forms

Automatically send contacts from Gravity Forms straight to Drip and bring marketing automations to your forms.

  1. Step 1 — Install and Activate GC Drip
  2. Step 2 — Create a GC Drip Feed
  3. Step 3 — Set Up GC Drip Feed
  4. Step 4 – Test Connection
  5. Step 5 – Make Magic Happen with Drip

Drip is a powerful marketing automation tool—so much so, it’s our go-to. Pair it with Gravity Forms, and you’ve got a dynamic duo: smart automation meets flexible lead capture for everything ranging from simple newsletter signups to extensive lead nurture campaigns.

To link them up, we use Gravity Connect: Drip. It makes it easy to send data-rich leads from Gravity Forms into Drip, and lets you craft out automations that expand what Drip can do on its own. 💦

Let me show you how it’s done.

This article requires the Gravity Connect Drip plugin.

Buy Gravity Connect to get this plus other premium Gravity Forms plugins!

View Plugin Buy Now

Step 1 — Install and Activate GC Drip

GC Drip is available through Gravity Connect. You can easily install and activate it through Spellbook.

Step 2 — Create a GC Drip Feed

After connecting your Drip account to Gravity Forms, head to the form you want to use. In the Settings menu, click on Drip to get to the GC Drip Feeds screen. From there, click on Add.

Step 3 — Set Up GC Drip Feed

The default feed action is “Add Person”, so you can go straight to the Feed Action Settings to assign them to Drip workflows. You can also apply existing Drip tags, create new ones on the fly, and use form fields to do either—or both—at the same time.

Selecting Drip workflows and tags in a GC Drip feed.

Head to Personal Details where you can map to all of the following fields. Email is the only required field:

Mapping Drip Personal Details settings (email, name, address, and phone) to Gravity Forms fields in a GC Drip feed.

Next, use the Custom Fields section to map form fields, entry properties, or custom values to add specific details to the new person. You can select an existing identifier or create a new one.

Mapping Drip Custom Fields to Gravity Forms fields in a GC Drip feed.

Last, but certainly not least, you can use conditional logic to trigger specific feeds based on customer behavior.

For instance, imagine you have two workflows: a win-back campaign for casual buyers and a loyalty reward for high spenders. You can create two separate GC Drip feeds—one that runs when a customer’s total spend is below a certain threshold, and another that runs only when it’s above that threshold.

Setting up conditional logic to only run a GC Drip feed when a form's subtotal is greater than 100.

Want to apply conditional logic based on a form’s total price? With GP eCommerce Fields, you can use the {subtotal} merge tag in a Number field to mirror the form total and use it in your conditional logic rules. Check out this bite-sized explanation on how to implement it.

Step 4 – Test Connection

Once your feed is saved and ready to go, run a test entry to confirm everything is set up correctly.

Adding a person to Drip after filling out a form.

Step 5 – Make Magic Happen with Drip

Now that you’re sending people from Gravity Forms into Drip, you can put that data to work. For example, you can run a loyalty workflow that provides a discount on people’s birthdays! 🎂

15-day birthday Drip workflow.

Feeling inspired to keep your contact list clean and full of real-deal emails? Check out GP Email Validator. 📨

Leave a Reply

Your email address will not be published. Required fields are marked *

  • Trouble installing this snippet? See our troubleshooting tips.
  • Need to include code? Create a gist and link to it in your comment.
  • Reporting a bug? Provide a URL where this issue can be recreated.

By commenting, I understand that I may receive emails related to Gravity Wiz and can unsubscribe at any time.


Grab a bundle of free Gravity Forms plugins

Enter your email and receive our most popular free plugins and snippets, plus access to hundreds of others.

This field is for validation purposes and should be left unchanged.

OSZAR »