Kit (ConvertKit) logo

Add newsletter signups as tagged Kit subscribers

A signup on your site lands in the Kit form you chose, carrying a newsletter tag and the topics the reader picked.

When this happens

New newsletter signup submitted

Do this

Add the email and name to a Kit form and apply a "newsletter" tag

One-directional. A submission triggers the action — nothing is written back into your form.

A signup box on a blog or a homepage collects two or three things and nothing more. The work happens after: getting that reader into the right Kit form so the incentive email fires, and tagging them so a broadcast six months from now can still tell where they came from.

Creators and small publishers reach for this first. It ends the export-and-import habit — nobody downloads a CSV on Friday to paste into Kit on Monday, and the tag is applied at the moment of signup rather than remembered later.

Setting it up

  1. 1

    Publish the newsletter signup form and keep it to First Name, Email Address and Topics You're Interested In. Every extra question on a signup box costs you subscribers.

  2. 2

    In Kit, create the form the subscriber should land in. Its own settings control the incentive email and whether double opt-in applies, so set those before you build the Zap.

  3. 3

    Create the newsletter tag in Kit as well — Zapier's dropdown only lists tags that already exist.

  4. 4

    In Zapier, point the New Submission trigger at this signup form and pull a sample submission so the three field names appear in the mapping dropdowns.

  5. 5

    Choose Kit's Add Subscriber to Form action and select the Kit form you just made.

  6. 6

    Map Email Address to the Kit subscriber email and First Name to first name. Kit stores a single name field, so there is nowhere for a surname to go here.

  7. 7

    Map Topics You're Interested In to a Kit custom field called topics — that is what a later segment filters on.

  8. 8

    Set the tag on the same action to newsletter, submit the live form yourself, confirm the subscriber, tag and topics all appear in Kit, then switch the Zap on.

What maps where

Using the Newsletter Signup Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.

Form fieldKit (ConvertKit)
First NameKit subscriber first name
Email AddressKit subscriber email address
Topics You're Interested InKit custom field: topics

Variations worth knowing

One tag per topic

Rather than a single newsletter tag, branch in Zapier on Topics You're Interested In and apply a matching Kit tag for each answer. Readers who ticked one interest never receive the broadcasts about the others, and the segment sizes tell you which topic to write more of.

Same form, popup and inline

One published form can be shared as an inline block, a popup and a slide-in at once. Duplicate the Zap and change only the tag name for each placement, and Kit will show you which one actually earns subscribers instead of which one gets seen.

If something isn't arriving

Subscribers appear in Kit but never receive the welcome email.

Adding a subscriber to a Kit form triggers that form's incentive email, not an account-wide welcome. Check the Zap uses Add Subscriber to Form rather than a bare Add Tag action, and that the incentive email on that Kit form is switched on.

The tag is missing on some subscribers.

Kit only applies the tag when the action completes. Open the Zap history and look at the failed runs — an empty Email Address is the usual cause. Make Email Address required on the form so blank submissions cannot reach Zapier at all.

Frequently asked questions

Do these subscribers still go through Kit's double opt-in?

Yes. The Zap adds them to a Kit form, and that form's confirmation settings apply exactly as they would for a signup on Kit's own hosted page. With double opt-in switched on, the subscriber stays unconfirmed until they click the link in the confirmation email.

What happens if the same person signs up twice?

Kit matches on email address, so it updates the existing subscriber instead of creating a duplicate. The tag is applied again with no effect. The first name is overwritten with whatever the newer submission held, which means the most recent spelling wins.

If someone unsubscribes in Kit, does the form know?

No. The connection runs one way — a submission triggers an action in Kit, and nothing is written back into the form. Unsubscribes, bounces and tag changes live in Kit alone, and the responses view keeps the original submission either way.

Related automations

Build the form first

The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.

Start free