How fast does the reply actually go out?

Typeform sends us the response the moment someone hits submit, and the email goes out as soon as the agent finishes drafting it. In practice that is well under a minute, which is what makes it feel like a real SDR rather than an autoresponder.

Will it really reference what the prospect wrote, or just plug their name in?

It reads the full answer set and pulls in the specifics that matter, like the team size they reported, the use case they picked, or the urgency they indicated. The email reads like someone actually skimmed the form before replying.

What happens with low-fit leads, like wrong industry or wrong team size?

You describe what a no-fit looks like in plain English, and those leads get a short, polite note that acknowledges what they need, says you are probably not the right fit, and points them at a helpful alternative.

Do I need a separate email-sending tool like SendGrid or Postmark?

No. The email is sent through General Input's built-in Send Email, so you do not have to wire up another provider. It is a no-reply send, so include your calendar link or reply-to address inside the email body.

Can I change which form this listens to or run it for multiple forms?

Yes. The workflow is tied to one Typeform at a time, and you can clone it per form. Each form can have its own fit rules, tone, and calendar link.

Personalized Typeform lead response email, sent in minutes

Build me an agent workflow that replies to every new Typeform submission with a personalized, SDR-tone follow-up email.

Trigger: an incoming webhook from Typeform on a new form response. Configure the workflow so I can paste the webhook URL into Typeform's Connect > Webhooks panel for the specific form I want to automate. The trigger payload from Typeform includes the form_response object with answers, hidden fields, and the respondent's submitted email.

Steps the agent should run on each new response:

1) Parse the webhook payload to extract the response ID, the respondent's email, and every answer (question text plus the chosen value). If the webhook payload is missing or partial, call Typeform Retrieve Responses for that form_id, filter by the response_id from the webhook, and use that answer set instead. Always prefer the Retrieve Responses copy of the answers if both are available, since the webhook can omit calculated or hidden-field values.

2) Decide fit. I will give you a short description of what counts as a good fit (e.g. team size, industry, use case, urgency) and what counts as a clear no-fit. Classify the response as good-fit or no-fit. If you are not sure, default to good-fit so we don't accidentally decline a real prospect.

3a) If good-fit, draft a short HTML email (roughly 80 to 140 words) that: addresses the prospect by first name if available, references at least two specific things they actually answered (e.g. "saw your team is around 25 people and you're focused on outbound"), proposes a quick intro call, and includes my calendar link as a clickable inline link. Tone: a real SDR replying within minutes, warm but not overfamiliar, no marketing fluff, no emojis, no em dashes. Sign off with my name and role.

3b) If no-fit, draft a short HTML email (roughly 60 to 100 words) that: thanks them for filling out the form, acknowledges what they were looking for using their own words from the answers, explains briefly and politely that we are probably not the right fit right now, and points them at a helpful alternative (a doc, a partner tool, or a relevant resource I will give you). Same tone rules: warm, human, no marketing language.

4) Use Send Email to deliver the drafted HTML to the email address the respondent submitted on the form. Subject line should also be personalized and human, not templated (e.g. "Quick follow-up on your General Input demo request" with the company or use case worked in when possible). Keep the email under 150 words total so it reads like a person, not a sequence.

Things to make easy for me to edit at the top of the workflow: my from-name and signoff, my calendar link, the good-fit rules, the no-fit rules, the no-fit "here's something else" suggestion, and the subject-line style. Do not hard-code these inside the agent prompt; surface them as clearly labeled inputs.

Guardrails: never send more than one email per response_id (dedupe on response_id). If the submitted email field is missing or obviously invalid, skip the send and log why. Never invent facts about the prospect or their company; only reference what they actually wrote on the form.

What it does

Watches your Typeform for new responses and reacts within seconds, not hours.
Reads the answers the prospect actually gave, like team size, use case, and urgency, and weaves them into a short follow-up email.
Sends a warm SDR-tone reply with your calendar link when the prospect looks like a good fit.
Sends a polite, helpful decline with a suggested alternative when the answers point to a clear no-fit.

What you’ll need

A Typeform account with the form you want to follow up on, plus permission to add a webhook to it.
A few sentences describing what a good-fit prospect looks like and what an obvious no-fit looks like.
Your team's calendar link and the from-name you want the email signed with.

How to customize it

Adjust your fit rules. Swap in the team-size bands, industries, or use cases you care about and change what counts as a polite decline.
Tune the voice. Make it sound like a specific teammate, more formal, more casual, or shorter.
Change the call to action. Use a different calendar link, an intake form, or a Loom video depending on the segment.

Use cases

Email Automation
Lead Enrichment
Notifications & Alerts

Reply to Typeform leads with a personalized SDR-tone email

Integrations

Type

Categories

What it does

What you’ll need

How to customize it

Use cases

FAQs

Related prompts