# Typeform + Krokul CRM

Yes. Krokul CRM integrates with Typeform. Every submitted typeform arrives in Krokul as a contact, a client company and a deal in the pipeline you pick, with the source, UTM tags and click IDs from hidden fields. Responses reach Krokul through the Krokul app in Zapier, Make, n8n or Albato, or through a handler you build on the Krokul API.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make, n8n, Albato.

## What your team gets

### A qualification typeform opens a deal

A buyer finishes a typeform with name, work email, company and budget. Typeform posts the form_response to the Krokul door, and Krokul reads each item of form_response.answers by its field.ref. The contact is matched by email or phone, the client company is linked by name, and a deal opens in the pipeline chosen for that form.

### Hidden fields carry the campaign

Typeform hidden fields can hold utm_source, utm_campaign, gclid or fbclid from the link that opened the form. Krokul reads the hidden block of the response and stores these values on the deal. The sources report then counts deals per campaign, and the click ID waits on the deal for the ad system.

### The budget answer sets the expected amount

A number answer about budget maps to the expected amount of the deal, and a choice answer about the product maps to a custom deal field. The manager opens a deal that already has a size and a subject.

### Free text lands in the deal feed

Long text answers, such as a description of the project, go into the first incoming message on the deal. The manager reads the whole response next to the tasks and the next steps, without opening Typeform.

## What moves between Typeform and Krokul

| Typeform | Krokul | Direction | When |
|---|---|---|---|
| form_response: name, email and phone answers | Contact, matched by email or phone | Typeform → Krokul | Each submitted response |
| form_response: company answer | Client company linked to the contact | Typeform → Krokul | Same response |
| Form (form_id) | Deal in the pipeline, source and owner set for that form | Typeform → Krokul | Each submitted response |
| hidden: utm tags, gclid, fbclid | UTM tags and click IDs on the deal | Typeform → Krokul | Same response |
| Number and choice answers | Expected amount and custom deal fields | Typeform → Krokul | Same response, by the field mapping |
| Text answers | First incoming message on the deal | Typeform → Krokul | Same response |

## How to connect today

### Krokul app in Zapier, Make, n8n or Albato

1. Add the Krokul app and connect it with an API key.
2. Start from the Typeform trigger New Entry and use the Krokul actions Find Contact and Create Deal for custom routing, for example a different pipeline per answer.
3. The Krokul triggers Deal Created and Contact Created can feed the next step, such as a welcome email or a team chat message.

### Custom flow through the Krokul API and webhooks

1. Make a Krokul API key with scopes for contacts, client companies and deals.
2. Register a Typeform webhook on the form that points at your handler, and check the Typeform-Signature header against the raw body.
3. Read form_response.answers by field.ref, look the person up with contact/api-find, and call contact/api-create, clientCompany/api-create and card/api-create for whatever is new.
4. Keep the Typeform response token on the deal with externalRef/api-upsert, so a replayed delivery finds the same deal.

**Triggers:** New Entry; Agent Conversation Finished; Automation Contact Action.

**Actions:** Create an Empty Form; Duplicates an Existing Form; Update Dropdown, Multiple Choice or Ranking Question Options.

### For integrators

For your own handler, the Typeform webhook body has event_type form_response, and the answers sit in form_response.answers with a field.ref per question. Typeform signs the body in the Typeform-Signature header with HMAC SHA-256 of the raw request. A forged request fails that check. On the Krokul side, contact/api-find and card/api-create take the result, and externalRef/api-set stores the Typeform response token. Signed Krokul webhooks with a delivery log and a sandbox company help you test before a client sees it.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul integrate with Typeform?

Yes. Krokul integrates with Typeform through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks.

### Do I need to rename my Typeform questions?

No. You map each question to a Krokul field once per form. Krokul keeps the mapping by the question ref, so renaming the question text in Typeform does not break it.

### Does a repeat response create a duplicate contact?

No. Krokul finds the contact by email or phone first and adds the new deal to that contact. The earlier deals stay in the contact history.

### What happens if Krokul is unreachable when Typeform sends a response?

Typeform retries webhook deliveries that fail, according to its webhook documentation. Krokul also records each received response in the connector journal, so a response that failed on the Krokul side can be replayed from there.

## Limits

Form design, logic jumps and response analytics stay in Typeform. Krokul keeps the person, the company and the deal that follow the answer.

## Related services

- [Jotform](https://krokul.com/en/integrations/jotform/index.md)
- [WordPress forms](https://krokul.com/en/integrations/wordpress-forms/index.md)
- [Webflow](https://krokul.com/en/integrations/webflow/index.md)
- [Google Ads](https://krokul.com/en/integrations/google-ads/index.md)
- [Meta Lead Ads](https://krokul.com/en/integrations/meta-lead-ads/index.md)
- [Zapier](https://krokul.com/en/integrations/zapier/index.md)

[Forms and ad inquiries](https://krokul.com/en/integrations/category/lead-capture/index.md)

Typeform is a trademark of TYPEFORM SL. Krokul is not affiliated with Typeform.

Updated: 2026-10-12

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs