Tag customers who opt in when leaving feedback
Feedback submissions with the follow-up box ticked add the customer to Kit with a left-feedback tag.
New feedback form submitted with marketing opt-in checked
Add the subscriber and apply a "left-feedback" tag in Kit
One-directional. A submission triggers the action — nothing is written back into your form.
People who take the time to write a suggestion are already engaged, and they are the easiest group to lose track of. Tagging them at the moment they opt in keeps that group intact without anyone maintaining a spreadsheet of who said something useful.
The opt-in question is what makes the flow safe to run. Only submissions with permission ticked ever reach Kit, so the tag never quietly fills up with people who wrote in and did not want to hear back.
Setting it up
- 1
Publish the suggestions form and word May We Follow Up With You? so the answer is unmistakable consent to be emailed, not a vague maybe.
- 2
Use conditional logic to show Email Address (optional) only when that answer is yes, so you are not holding addresses you have no permission to use.
- 3
Create the left-feedback tag in Kit before building the Zap.
- 4
In Zapier, set the New Submission trigger to the suggestions form and load a sample submission.
- 5
Add a Zapier filter as the very next step: continue only when May We Follow Up With You? is yes and Email Address (optional) is not empty.
- 6
Add Kit's Add Tag to Subscriber action, choose left-feedback, and map Email Address (optional) to the subscriber email.
- 7
Map Your Name (optional) to first name, and send What Type of Suggestion Is This? and Your Suggestion or Idea into Kit custom fields so a later broadcast can tell a bug report from a feature idea.
- 8
Send one test submission with the box ticked and one without. Only the first should reach Kit; the second should show as skipped in the Zap history. Then turn the Zap on.
What maps where
Using the Suggestions & Feedback Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Kit (ConvertKit) |
|---|---|
| Your Name (optional) | Kit subscriber first name |
| Email Address (optional) | Kit subscriber email address |
| What Type of Suggestion Is This? | Kit custom field: feedback_type |
| Your Suggestion or Idea | Kit custom field: feedback_note |
| May We Follow Up With You? | Zapier filter that decides whether the Kit action runs at all |
Variations worth knowing
Branch on What Type of Suggestion Is This? and apply a different Kit tag for each: feature-idea, bug-report, pricing. When something ships, the announcement goes to the people who asked for that exact thing rather than to the whole list.
Add a second Zapier action that posts Your Suggestion or Idea into your help desk or a team channel next to the Kit step. Kit holds the subscriber and the tag; the team still reads the sentence the customer actually wrote.
If something isn't arriving
The email field is optional on this form, so blank values do reach Zapier. Give the filter two conditions — consent given and Email Address (optional) exists — and those runs will show as skipped rather than as errors.
Check that the filter tests the exact answer text. Re-wording the consent question on the form leaves the old value sitting in the filter, which then matches nothing and lets everything through. Pull a fresh sample after any change to that question.
Frequently asked questions
Is a ticked box enough consent to send marketing email?
That depends on your jurisdiction and on how the question is worded. A tickbox that states plainly what you will send is the minimum. EU hosting and GDPR compliance on our side do not make a vague or pre-ticked question valid.
Can I read the feedback itself inside Kit?
Only what you map across. Sending the suggestion text to a Kit custom field puts it on the subscriber record, which helps when replying by hand. Long answers can be truncated there, so treat the responses view as the full copy.
Does removing the tag in Kit delete the submission?
No. The two systems stay separate and the connection runs one way, from submission into Kit. Removing a tag or deleting a subscriber changes nothing on the form side, and the original response stays in the responses view.
Related automations
- 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.
- Deliver a lead magnet with a Kit sequence
An ebook request drops the reader into a Kit sequence that sends the download link and nurtures from there.
- Send webinar registrants into a Kit reminder sequence
Registrants land in a Kit sequence that confirms the booking and sends reminders before the session starts.
- Tag course waitlist signups in Kit
Waitlist signups arrive in Kit tagged course-waitlist, ready to email as one segment on launch day.
- Tag notify-me signups by the product they want
Notify-me requests create a Kit subscriber tagged with the product, ready for a single restock broadcast.
- Add buyers to a customers list after each order
Each order form submission adds the buyer to a Customers list in Constant Contact for updates and repeat-purchase emails.
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