# Webflow + Krokul CRM

Yes. Krokul CRM integrates with Webflow. Each form submission on your Webflow site becomes a contact, a client company and a deal, with the pipeline, source and owner you set per form. Submissions travel through the Krokul app in Zapier, Make, n8n or Albato, or through your own handler on the Krokul API, and the design and thank-you messages on the Webflow side stay as they are.

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

## What your team gets

### A Webflow contact form opens a deal

A visitor sends the contact form on your Webflow site. Webflow delivers a signed form_submission event, Krokul reads payload.data with name, email, phone, company and message, and opens a deal in the pipeline set for that form. The owner gets a notification with the request.

### One Webflow site, several forms, several teams

Webflow names the form that sent each submission. In Krokul, demo requests go to the sales pipeline, partner applications go to the partner manager, and support questions open a ticket, all through one Webflow site connection.

### The page and campaign stay on the deal

Hidden inputs on the Webflow form can carry utm tags, gclid and the page path. Krokul keeps them on the deal, so the sources report shows which Webflow page and which campaign brought it, and the click ID is ready for an ad conversion later.

### The Krokul widget as a second route

On pages where you do not need a Webflow form, an Embed element can hold the Krokul form widget. Its submissions reach Krokul directly, with a hidden trap field for bots, a minimum fill time and a list of allowed sites.

## What moves between Webflow and Krokul

| Webflow | Krokul | Direction | When |
|---|---|---|---|
| form_submission: payload.data name, email, phone | Contact, matched by phone or email | Webflow → Krokul | Each submission on a connected site |
| form_submission: company field | Client company on the contact | Webflow → Krokul | Same submission |
| Form name | Pipeline, source and owner of the deal, or a ticket | Webflow → Krokul | By the rule set per form |
| Hidden inputs: utm tags, gclid, page path | UTM tags, click ID and page on the deal | Webflow → Krokul | Same submission |
| Message field | First incoming message on the deal | Webflow → Krokul | Same submission |
| Embed element with the Krokul widget | Contact and deal | Webflow page → Krokul | Each submit from the widget |

## How to connect today

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

1. Connect the Krokul app with an API key.
2. Start from the Webflow trigger New Form Submission and use Krokul actions such as Find Contact, Create Deal or Create Ticket when a rule needs data from another system.
3. The Webflow trigger New Order can create a deal through the Krokul action Create Deal if you sell through Webflow Ecommerce.

### Custom flow through the Krokul API and webhooks

1. Create a Krokul API key that can write contacts, client companies, deals and tickets.
2. Register the form_submission webhook through the Webflow Data API so that each delivery to your handler is signed, and check x-webflow-signature with x-webflow-timestamp.
3. Read payload.data, find the person with contact/api-find, and open the record with card/api-create, or with ticket/api-create for support forms.
4. Store the Webflow submission reference on the deal through externalRef/api-upsert, so a retried delivery never opens a second deal.

**Triggers:** New Form Submission; New Order; Updated Order; New Comment; New Resolved Comment Thread.

**Actions:** Create Item; Create Live Item; Update Item; Update Live Item; Fulfill Order; Update Order.

### For integrators

Webflow sends the form_submission webhook to any handler you register through the Webflow Data API. Webhooks created that way carry the x-webflow-signature and x-webflow-timestamp headers, while webhooks added in site settings do not. A custom handler reads payload.data and calls contact/api-find, card/api-create or ticket/api-create in the Krokul API with a bearer key. Krokul answers with signed webhooks of its own. A sandbox company keeps tests separate.

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

## Questions and answers

### Does Krokul integrate with Webflow?

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

### Do I have to rebuild my Webflow forms?

No. Krokul subscribes to submissions of the forms you already have. The form design and the success message stay in Webflow.

### Does Krokul sync Webflow CMS collections?

No. CMS content belongs to the site. Krokul takes form submissions, and orders only when you route them through the Krokul app.

### What happens if Krokul does not answer a Webflow webhook?

Webflow retries a webhook that does not get HTTP 200 up to three more times, ten minutes apart. After repeated failures Webflow deactivates the webhook and emails the site owner, and the Krokul connector journal shows the failed deliveries.

## Limits

CMS collections, Webflow Ecommerce orders and the site itself stay in Webflow. Krokul receives form submissions and runs the sale that starts with them.

## Related services

- [Typeform](https://krokul.com/en/integrations/typeform/index.md)
- [Jotform](https://krokul.com/en/integrations/jotform/index.md)
- [WordPress forms](https://krokul.com/en/integrations/wordpress-forms/index.md)
- [Google Analytics 4](https://krokul.com/en/integrations/google-analytics-4/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)

Webflow is a trademark of Webflow, Inc. Krokul is not affiliated with Webflow.

Updated: 2026-10-12

---

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