Copying a new inquiry from a form into a spreadsheet, then into an email tool, creates repeated work and opportunities for mistakes. A small lead-capture workflow can move the right information between those systems while keeping a human responsible for the actual conversation.
This guide uses a consultant’s intake form as an example. Someone submits an inquiry, Make checks and maps the response, and people who explicitly opt in can enter Kit for relevant email follow-up. An inquiry alone should not automatically become a newsletter subscription.
Research basis: This is a documentation-based setup guide, not a report of a workflow Harzel has personally tested. The examples and acceptance checks below are a proposed configuration. Run them in your own accounts before opening the workflow to real leads.
The workflow at a glance
- 01 / IntakeFilloutCollect the response
- 02 / ProcessMakeCheck, clean, route
- 03 / Follow upKitOrganize opted-in subscribers
Fillout → Make → Kit. Keep the first version small: one form, one consent filter, one Kit destination form, and one source tag. Add branches only when a real requirement calls for them.
Successful capture and successful email delivery are different outcomes. A completed automation does not prove that a subscriber confirmed their address, received a message, or wants every future campaign.
What each tool does
- Fillout: lead intake
- Collect the email address, name, and structured inquiry details. Make’s Fillout integration includes an instant Watch New Responses trigger for form submissions. Source: Make’s Fillout module directory.
- Make: automation and routing
- Map answers to destination fields, filter records, and branch when different inquiry types need different handling. This is the coordination layer, not your customer database.
- Kit: subscriber organization and email follow-up
- Use subscriber fields for a few attributes and tags for groups. Kit supports email sequences, but a tag by itself does not send an email: you must separately configure the follow-up. Source: Kit’s tags and segments guide.
Check plan access before building
Do not assume this entire workflow is free. Make’s Kit connector documentation lists a paid Kit account requirement. Kit’s Free plan guide lists API access, but places sequences and visual automations on paid plans. API access alone does not establish that this connector or follow-up sequence is available on your account.
Check your current connector access and each service’s usage limits before committing. This guide makes no fixed-price or all-free claim. You do not need to buy all three tools to collect a lead.
Step-by-step setup
1. Create a short Fillout intake form
Start with a required email field, first name, optional company, and an inquiry-type dropdown. Use a small set of answers such as “Consulting,” “Workshop,” and “General question.” Ask only what you will use to respond.
If you also offer educational emails, add a separate, unchecked opt-in with clear wording, such as: “Send me occasional workflow guides by email. I can unsubscribe at any time.” Keep it optional for someone making an inquiry. Include a link to your privacy notice. Do not put API secrets or private information in hidden fields.
2. Create the Make scenario
Create a new scenario and add Fillout Forms → Watch New Responses. In its webhook setup, create a connection, authorize the intended Fillout account, and select your intake form. Save the connection and webhook. Follow the connector’s current prompts if its labels differ. Source: Fillout connection instructions in Make.
Use a private test form or an unshared form URL initially. Run the scenario once and submit a sample response so you can inspect the actual output. Map from the captured answer fields rather than guessing field names or assuming question order will stay fixed.
3. Clean the fields and set the consent filter
Trim surrounding whitespace from email and name values. Preserve the submitted name’s capitalization. Do not silently “correct” a questionable email address into a different address. Reject an empty required email and keep unrecognized inquiry types out of automated follow-up.
Add a filter before the Kit module: the email must be present and the optional email opt-in must equal the checked value seen in your test response. A checkbox may arrive as a boolean, text, or a selected-answer collection; check the sample instead of assuming the string “yes.”
In Make, click the connection between modules to define the filter. A record that fails it stops on that route. Keep inquiry-only responses available in Fillout for a personal reply; do not lose those inquiries because they declined marketing. Source: Make filters.
4. Prepare the Kit destination
Create a dedicated Kit form for the intended subscription and decide how its confirmation email should work. Prepare a source tag such as source:lead-intake. If needed, create short custom fields named company, inquiry_type, and lead_source before mapping them. Kit’s custom-field guide explains their creation and plain-text storage.
Keep long inquiry messages and sensitive details out of subscriber fields. Store the minimum useful context, not a copy of every answer.
5. Send the eligible contact to Kit
Add Kit’s Add a Subscriber to Form module after the filter. Create the connection using the credentials requested by that connector; Make’s current guide describes a Kit API secret. Keep it inside the connection settings, never in a shared form or article. Select the destination form and map email and first name. Source: Make’s Kit connector.
Map the optional custom fields if the selected module exposes them. If it does not, start with email, first name, and a source tag; do not guess unsupported field inputs. Extra fields are useful only when they change what happens next.
6. Apply a tag and configure follow-up deliberately
Add Add a Tag to a Subscriber, choose source:lead-intake, and map the subscriber identifier or email required by that module from the preceding result. This records the workflow source; it is not advertising attribution. Source: available Kit actions in Make.
If you need automated messages, create the relevant Kit sequence and connect its entry condition separately. Keep it inactive or restricted to test subscribers until the checks below pass. Your first message should match what the person signed up for; a generic sales sequence is not a substitute for replying to a specific inquiry.
Do not assume an API-added subscriber has confirmed a subscription. Inspect the subscriber’s form status and confirmation behavior in your account. Never force an unsubscribed or complained contact back into active marketing. Source: Kit subscriber status.
A practical field-mapping example
These are example field names and destination choices, not an exported blueprint. Match them to the fields in your actual response.
| Fillout field | Make action | Kit destination |
|---|---|---|
| Trim whitespace; require a nonempty value | ||
| First name | Trim whitespace; retain entered spelling | First name |
| Company | Map only a nonempty, short answer | Optional company custom field |
| Inquiry type | Allow only the form’s defined options | Optional inquiry_type field; later, an interest tag |
| Source | Set a fixed value such as website-intake | Optional lead_source field plus source tag |
| Email opt-in | Filter: explicitly checked | Gate entry; a tag is not proof of consent |
For example, a fictional response from “Alex,” company “Example Studio,” inquiry “Consulting,” with opt-in checked would enter the chosen Kit form and receive the source tag. Use an inbox you control when executing the test. Keep the submitted consent answer and timestamp with the intake record.
For returning subscribers, decide whether source means first source or latest inquiry. Avoid overwriting a useful existing company value with a blank answer. A new form response is an event; it is not necessarily a new person.
Test before opening the workflow to real leads
Use dummy names and an email inbox you control. Test one case at a time, then inspect both the Make run and the Kit subscriber—not only the green completion indicator.
- Valid opt-in: one response reaches the right Kit form, with the intended fields and source tag. Check confirmation and follow-up in the test inbox.
- No opt-in: the inquiry stays available in Fillout, and the Kit route does not run.
- Missing or malformed email: form validation or the scenario stops the record. No unrelated subscriber is created.
- Existing subscriber: confirm a second submission does not restart a welcome sequence unexpectedly or erase nonempty profile fields.
- Unsubscribed test contact: confirm the flow does not reactivate marketing without the appropriate renewed permission.
- Unrecognized inquiry type: send it for manual review, not to an arbitrary interest tag.
- Failed Kit action: in a test copy, confirm that an error is visible and the original response remains recoverable. Do not deliberately disrupt a working production connection.
Before replaying a failed run, check whether Kit already received the earlier steps. Use the response ID as a processing key if you later add a log, and record separate outcomes for adding the subscriber and applying the tag. Retrying the whole workflow blindly can repeat downstream actions.
Review Make’s error-handling options and choose a recovery approach you can maintain. Once all relevant cases pass, activate the scenario and follow-up, share the Fillout form, and submit one controlled live test. Monitor early runs and respond to failures; this is not a set-and-forget system.
When Make is actually worth using
If all you need is one signup form feeding one email system, start by checking the destination’s own form or a supported native integration. Kit’s own form may remove the need for both Fillout and Make. We have not verified a direct native Fillout-to-Kit connector, so this guide does not promise one. Check the current Fillout integration directory for your destination.
Make becomes more useful when the workflow needs a decision or a second destination:
- Branch consulting and workshop inquiries differently.
- Clean inconsistent fields before sending them onward.
- Notify an existing team inbox about a qualifying lead.
- Write a minimal processing log or spreadsheet backup.
- Add a CRM route later without replacing the original form.
The trade-off is another account, usage limits, credentials to maintain, and more places for a failure to occur. Multiple modules and branches also consume more of your automation allowance. For a few inquiries that you prefer to answer personally, a form and manual reply may be the better starting point.
Useful next upgrades
Add only the upgrade that addresses a real gap in the first version.
- Minimal spreadsheet log: store response ID, received time, and processing status. Avoid a second full copy of every personal detail.
- High-value inquiry alert: use an explicit answer such as requested service to trigger a notification. Do not infer private characteristics.
- Different interest tags: route known dropdown answers to a small, documented tag list.
- CRM routing: add a CRM when you need deal stages, ownership, or a durable sales history. Kit’s subscriber record is not a full sales pipeline.
Make’s router documentation describes branching and fallback routes. Use mutually exclusive conditions when only one branch should run; use multiple matching branches only when you intend multiple actions. Keep an explicit fallback for answers you did not anticipate.
Who this stack is best for
This is a plausible fit for freelancers, creators, consultants, and teams of roughly 2–10 people who need structured intake plus permission-based educational follow-up, but do not yet need a heavy CRM. It is especially relevant when you already use Kit and need more control over form handling.
It is a weaker fit for a simple newsletter signup, a business that only needs personal replies, or a sales team requiring deal ownership and activity history. For sensitive or regulated intake, evaluate the tools and data handling separately before adapting this example.
Common questions
Do I need all three tools?
No. Use Kit’s own form for a simple subscription, or a form with manual replies for occasional inquiries. Add Make when routing or transformation justifies it.
Does tagging a subscriber start an email sequence?
Not by itself. The tag must be connected to an appropriate automation or rule, with sending and subscription status checked. Test the actual entry condition before launch.
Can I call this a free lead-capture stack?
Not reliably. This connector and automated follow-up have plan requirements. For a detailed breakdown of free-tier boundaries and minimal-cost tooling, read our guide on The $0-to-Low-Cost Lead Intake Stack for a One-Person Business.
Choose the tools your workflow needs
These are affiliate links. Compare the current capabilities and plan limits with your requirements before signing up. Start with the smallest workable setup.
Editorial note
Pricing, product features, connector requirements, and affiliate terms can change. Harzel Orbit Labs records verification dates; the official documentation cited in this guide was checked on October 3, 2026. That date records documentation review, not hands-on workflow testing or a guarantee that every account has identical features.
Read how we evaluate sources, review our commercial disclosures, or send a correction.