Skip to main content

CRM & automation

Drip in Core Forms

Create or update a Drip subscriber and optionally assign a tag.

Bundled with Core Forms, the WordPress forms plugin with every premium feature in the box. No add-on tax.

Bundled, no add-on tax Unlimited sites

The Drip WordPress form integration creates or updates a subscriber in your Drip account each time a form is submitted, stores the submitted name in a name custom field, and can apply one tag. You need a Drip API token and your numeric account ID. Workflow selection and wider custom-field mapping aren't part of it.

Core Forms sends a subscriber’s email, a name custom field, and an optional tag to Drip. Direct workflow selection, event creation, and arbitrary custom-field mapping are not included.

Drip at a glance

Requires
Drip API token and numeric account ID
Creates
Subscriber, created or updated
Tag
One tag, entered by name
Name
Saved to a custom field called name
Missing tags
Created in Drip automatically
Timeout
15 seconds per request

Full reference: Drip action reference

What you get

How Drip works in Core Forms

Subscriber upsert

Create or update a subscriber in the configured account.

Optional tag

Apply a tag that your Drip account can use for segmentation.

Name field

Choose the form field used for the subscriber’s name.

Use cases

What people build with Drip and Core Forms

Label subscribers by source

Tag contact form signups with website-contact and webinar registrations with webinar, so every Drip subscriber shows where they joined.

Split tags by answer

Add two Drip actions with different tags and a condition on a field like interest. Each subscriber gets the tag that matches what they picked.

Footer newsletter signup

A two-field form (name and email) feeds Drip directly, with no embed code from Drip on the page.

Set it up

Connect Drip in 3 minutes

  1. 1

    Get API credentials

    Copy your Drip API token and account ID.

  2. 2

    Configure the action

    Enter the token, account ID, and optional tag.

  3. 3

    Select fields

    Choose the email and name fields.

Every setting, filter, and error message is documented in the Drip action reference.

Good to know

Requirements and limits

  • Drip has no first and last name fields in this action; the full name is stored as-is in a custom field called name.
  • Each action applies one tag, written as a text name like form-submission, not a numeric ID.
  • Regenerating the API token in Drip invalidates the old one, so update the action afterward.
  • Drip may reject disposable email addresses depending on your account settings, which looks like a missing subscriber.
FAQ

Drip integration questions

Do I need to create the tag in Drip first?
No. Enter the tag as plain text, like form-submission. If it doesn't exist in Drip yet, Drip creates it when the subscriber is added.
Where do I find my Drip account ID?
It's the numeric ID in your Drip dashboard URL when you're logged in. The action rejects non-numeric values, which is the usual cause of an "account not found" error.
Can Core Forms add subscribers to a specific Drip workflow?
No. The action creates or updates the subscriber and applies an optional tag; direct workflow selection and events aren't included. Use the tag on the Drip side to decide what happens next.
Can I send first and last names as separate fields?
No. Drip has no built-in first and last name fields here, so the whole name goes into a custom field called name. Pick the form field that holds the full name in the Name Field setting.
Why isn't my subscriber showing up in Drip?
Check that the email is valid and that your Drip account doesn't reject disposable addresses. If the token was regenerated, paste the new one. The Drip troubleshooting section lists each error.

Bundled with every Core Forms license.

Drip and every Core Forms-built integration on this site are included with your license.