Webhook recipe · Typeform

Typeform → Chromoly: forms become systems.

Q: Does Typeform support webhooks on all plans?

Typeform includes webhooks on its standard paid plans (and its free tier has supported them for basic use) - check the Connect panel of your form. If the option is there, this recipe works.

Q: What happens to the form fields in Chromoly?

Each Typeform answer arrives as a field in the webhook payload. Send one test submission and Chromoly shows the received fields for mapping to your entity - name to name, email to email, and any custom questions to your custom fields.

Q: Can AI process the submission on arrival?

Yes - that's usually the point. A lead-scoring step, a classification step, or an AI-drafted reply for approval can run as the next workflow step after intake. Low-confidence results route to a review queue instead of acting.

A Typeform collects the lead, the application, the request - and then it sits in Typeform. This recipe lands every submission in a system that acts on it: scored, routed, tracked, followed up. Ten minutes, no middleware subscription.

What people build with it

Lead intake - submissions become CRM leads, AI-scored against your profile, hot ones alerting Slack.
Request intake - internal request forms feed a service desk with triage and SLAs.
Applications - candidate forms flow into a recruiting pipeline with CV screening for human review.

The recipe

In Chromoly, describe (or add to) a workflow with a webhook trigger: "when a form submission arrives, create a lead". The trigger gets a unique URL and signing secret, shown in the workflow settings.

In Typeform, open your form → Connect → Webhooks, paste the Chromoly URL as the destination, and turn the webhook on.

Submit one test response. Chromoly shows the received payload - map Typeform’s answer fields to your entity’s fields once.

Add what happens next in plain language: score it, route it, alert someone, start the follow-up clock. Preview, then deploy.

Webhook triggers and their signing secrets are covered in the integrations documentation. Every received request - including rejected ones - appears in the workflow's run history, so the connection is debuggable from day one.

What the payload looks like

{
  "form_response": {
    "answers": [
      { "field": { "ref": "company_name" }, "text": "Nordic Supply AB" },
      { "field": { "ref": "work_email" },  "email": "anna@nordicsupply.se" },
      { "field": { "ref": "team_size" },   "choice": { "label": "11-50" } }
    ]
  }
}

Chromoly maps these to your entity's fields - after the one-time mapping, every submission lands structured.

Questions

Does Typeform support webhooks on all plans?

Typeform's webhook feature lives in each form's Connect panel and is available on standard plans - if the option is there, this recipe works.

What happens to the form fields in Chromoly?

Each answer arrives as a field in the payload. Send one test submission and Chromoly shows the received fields for one-time mapping to your entity.

Can AI process the submission on arrival?

Yes - a lead-scoring step, classification, or an AI-drafted reply for approval can run as the next workflow step, with low-confidence results routed to review.

Build the system this feeds

Describe it in plain language - the webhook trigger is part of the description. Preview free before anything deploys.

Start free