# Route Typeform leads into the right GetResponse campaign

> When someone fills out your Typeform, we read the answers, pick the best-fit GetResponse list, add them with the right tags, and post the handoff in Slack.

- Workflow type: agent
- Services: Typeform, GetResponse, Slack
- Categories: Marketing, Sales
- Published: 2026-07-11

## What it does

- Reads every new Typeform submission and pulls the full set of answers, including branching logic and hidden fields.
- Looks at your live GetResponse campaigns, tags, and segments before deciding where the person belongs, so you never have to hardcode a mapping.
- Adds the contact to the best-fit campaign with tags and custom fields that reflect what they actually said.
- Posts a short qualified-lead note to Slack that names the respondent, the list they landed in, and the two or three answers that drove the call.
- Tags obvious low-intent responses as cold and quietly skips the Slack ping so your team only sees leads worth looking at.

## What you'll need

- A Typeform account and a form that is already collecting responses.
- A GetResponse account with a few campaigns you nurture separately, plus any tags you use to segment contacts.
- A Slack workspace and a channel your sales or marketing team watches (for example #new-leads).

## Prompt

Build me an agent workflow that runs every time someone submits my Typeform, and routes them into the right GetResponse campaign automatically.

Trigger: a Typeform webhook on my form. When it fires, the payload includes the form id and the response id for the new submission.

Steps for the agent:

1. Call Typeform Retrieve Responses using the response id from the webhook so you have the full set of answers, including any hidden fields.

2. Call GetResponse List Campaigns, List Tags, and List Segments so you know what buckets already exist in this account. Do this on every run so newly added campaigns and tags get picked up.

3. Read the answers (industry, intent, use case, plan interest, whatever this form asks) and decide which existing GetResponse campaign is the best fit. Prefer campaigns that already exist. Never create a new campaign.

4. Add the person to that campaign using GetResponse Create Contact. Use the name and email from the Typeform answers, apply the tags from List Tags that match the answers (for example the industry tag and the use case tag), and set custom fields for anything structured you can pull out. Only use tags that already exist on the account.

5. If the responses look obviously low intent (no real use case, throwaway or role email, tire-kicker language, or an explicit not-interested answer), tag the contact cold instead of the normal tags and stop. Do not send the Slack ping in that case.

6. Otherwise post a short qualified-lead note to Slack using Slack Send a Message. Name the respondent, say which GetResponse campaign you routed them into, and quote the two or three answers that drove that decision. Post to the channel #new-leads (I will edit the channel name later). Keep the message under six lines.

Rules of thumb: one Typeform can feed many different nurture flows, so never hardcode a single campaign. Pick per response. Never invent a campaign or a tag that is not already on the account. If you cannot confidently pick a campaign from the answers, fall back to the most generic list on the account and note that in the Slack message.

## How to customize

- Change which answers drive the routing decision (industry, use case, plan interest, seniority, region).
- Tell the agent what a low-intent response looks like so those contacts get tagged cold and skip the Slack ping.
- Swap the Slack channel, use a private group DM, or add a second Slack message so different form types route to different teams.

## FAQ

### What if my Typeform has logic jumps or hidden fields?

We read the full response payload, so branching answers and hidden fields all flow into the routing decision.

### Do I have to hardcode which campaign each form goes to?

No. That is the whole point. The agent reads your live GetResponse setup on every run and picks the best-fit campaign for the answers on that submission.

### What happens if the same person fills the form twice?

GetResponse handles duplicates on its side. If the contact already exists in the target list, we note it and move on without creating a duplicate.

### How does the low-intent skip work?

You describe what counts as a cold lead in plain language. Those contacts still get added to GetResponse with a cold tag so you can nurture them later, but we skip the Slack notification.

### Can I route to more than one Slack channel?

Yes. Add a second Slack step and split by form type, campaign, or a specific answer so different leads land in different channels.

Use this prompt in General Input: https://www.generalinput.com/prompts/route-typeform-leads-into-the-right-getresponse-campaign