What makes Typeform easy or hard to automate
Typeform sends a webhook the moment someone submits, so automations react in seconds rather than on a polling schedule. The payload carries the form definition and the answers together, plus any hidden fields you passed in the form URL, such as UTM source, campaign or a CRM contact ID. That makes attribution and record matching straightforward.
The awkward part is shape. Answers arrive as a list, one object per answered question, and each answer has a type: text, email, choice, choices, number, date, boolean, file URL and so on. Skipped questions are simply missing from the list. Every workflow needs a small mapping step that turns this list into named fields, and that mapping should key on each field’s ref rather than its title.
Logic jumps add a second wrinkle. Two respondents to the same form can answer different questions, so downstream code must treat most fields as optional.
The AI layer
Typeform collects structured answers well. What it cannot do is judge them. The AI work sits after submission:
- Scoring and routing. A model weighs the combination of answers, such as company size, timeline and a free-text description of the problem, and returns a score, a reason and a suggested owner.
- Understanding open text. Long answers to “what are you trying to solve?” get summarized into one line for the CRM and tagged by theme for reporting.
- Writing back. A first reply that quotes the respondent’s own words gets far more engagement than a template, and a model can draft it in the brand’s voice for a rep to approve.
Scores and routing rules stay explicit. The model returns JSON with a fixed set of values, and code decides what happens with each value.
Limits to plan around
- Rate limits. The Create and Responses APIs allow two requests per second per account. Webhooks do not count against this limit, which is another reason to use them.
- Webhook security. Set a secret on each webhook and verify the
Typeform-Signatureheader, an HMAC SHA-256 of the raw body. Without it, anyone who learns your endpoint can post fake leads. - Token scopes. Personal access tokens only allow the scopes chosen when they were created. A token without
webhooks:writecannot register webhooks. - Data region. Accounts hosted in Typeform’s EU data center use a separate API base URL, and integrations pointed at the default URL return nothing.
- File uploads. File answers are URLs that require authentication to download. Fetch and store the file in your own storage if you need it later.
How Lumeor typically connects it
We start with the n8n Typeform Trigger, a mapping step keyed on field refs, and a validation step that rejects spam and malformed emails. An LLM step scores or summarizes, then n8n writes to the CRM and alerts the owner in Slack. The lead routing guide and the form-to-database guide cover the pattern in detail. For a simple contact form where a cheaper builder is enough, Tally works with the same approach, and booked calls usually hand off to Calendly.