Skip to content
Tutorials Center
My learning

Topics

Lesson 28 of 37 ยท Forms, Ecommerce and Apps

Integrations, Webhooks and Automation

Connect Wix and Webflow to other tools: webhooks, REST APIs, Zapier-style automation, payloads and signatures, retries and idempotency, with runnable receiver stand-ins.

A website rarely works alone. A form submission should reach your CRM, a new order should notify the warehouse, a blog post should be shared to social media. Moving data between tools is integration, and doing it without a human is automation. This lesson explains the mechanisms both Wix and Webflow share (webhooks and APIs), the no-code automation services built on them, and the design habits that keep automations reliable.

Wix and Webflow are hosted products and cannot run here, so no live webhooks are sent. The runnable examples are stand-ins that show how a payload is parsed, verified and processed. Event names and fields in real products differ; use their documentation for exact formats.

Three ways to connect tools

  1. Native integrations. Built-in connections: Webflow can send form data to some services, Wix connects to Google Analytics, mailing tools, Facebook pixel, and so on. Easiest, but limited to what is offered.
  2. Automation platforms (Zapier, Make, n8n and similar). You define "when this happens, do that" as a workflow: trigger plus actions, using ready-made connectors for hundreds of apps. No code needed.
  3. Webhooks and APIs. Direct, custom, and the most flexible. Needs a small server or serverless function that you control.

What a webhook is

A webhook is an HTTP request that a service sends to a URL you provide when an event occurs. Instead of you repeatedly asking "any new orders?", the service tells you the moment one exists. In Webflow, you can add webhooks in site settings (Integrations area) for events such as form submissions, ecommerce orders, CMS item changes and site publishing, subject to the plan. Wix offers automations and webhooks through its automation tools and, for developers, through Velo and the Wix APIs for events like new orders or form submissions.

A typical payload (JSON) describes the event:

JSON
{
  "triggerType": "form_submission",
  "payload": {
    "name": "Contact form",
    "siteId": "abc123",
    "data": { "email": "[email protected]", "message": "Hi" },
    "submittedAt": "2026-01-15T10:30:00Z"
  }
}

The exact field names depend on the platform and event, so check the docs and log a sample before you write code that depends on it.

An API in one paragraph

An API lets your code call the platform: read CMS items, create products, update an order. Webflow has a Data API (REST, JSON, authenticated with tokens). Wix provides REST APIs and SDK modules. Calls use HTTP methods: GET reads, POST creates, PATCH or PUT updates, DELETE removes. Responses carry status codes: 200 ok, 201 created, 400 invalid request, 401 not authenticated, 403 not allowed, 404 not found, 429 too many requests, 500 server error. Respect rate limits: when you get 429, wait and retry later.

Receiving a webhook: parse and route

Your receiver should do three things quickly: confirm it is genuine, understand the event, and respond with 200 so the sender stops retrying. Slow work goes to a queue.

JS Stand-in: route webhook events

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Verifying that a webhook is genuine

Anyone who learns your receiver URL can send it fake events. Platforms often sign requests: they compute a signature (an HMAC of the body with a shared secret) and send it in a header; you recompute and compare. Webflow signs its webhooks, and many other services do the same; the header name and algorithm are in each platform's docs. The stand-in below uses a simple checksum to show the structure; real systems use HMAC-SHA256.

JS Stand-in: signature check (toy hash)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Retries and idempotency

Networks fail. If your receiver is down or slow, the sender retries, so the same event can arrive twice. A handler must be idempotent: processing the same event again must not create a duplicate order email or a second CRM contact. The usual technique is to store the event or order id and skip ids you have seen.

JS Stand-in: idempotent handler

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Designing no-code automations

With Zapier or Make, a workflow might be: Trigger: new Webflow form submission. Action 1: create a contact in the CRM. Action 2: send an email to sales. Action 3: append a row to a spreadsheet. Good habits:

  • Name each automation clearly and keep a list of them.
  • Add a filter step so tests and spam do not trigger actions.
  • Handle errors: turn on notifications for failed runs.
  • Watch costs: many tools bill per task or run.
  • Avoid loops, such as an action that edits the same item that triggers the automation.
  • Treat the automation account as a credential: use a dedicated login, strong password and the minimum permissions.

Security checklist

  • Keep tokens and secrets out of frontend code and public repos.
  • Use HTTPS endpoints only.
  • Verify signatures where offered.
  • Grant API tokens only the scopes they need, and rotate them when staff leave.
  • Log events without storing unneeded personal data.

Common mistakes

  • Assuming events arrive exactly once and in order.
  • Doing slow work inside the receiver, causing timeouts and retries.
  • Hard-coding field names without checking real sample payloads.
  • Forgetting to turn off test automations.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a webhook?

    Webhooks push event data to your endpoint, so you do not have to poll.
  2. 2. Why should webhook handlers be idempotent?

    Retries mean duplicates are possible; handlers should not create duplicate effects.
  3. 3. A 429 response means

    429 is the rate-limit status; wait before retrying.
  4. 4. What is the purpose of a webhook signature?

    The receiver recomputes the signature with a shared secret and compares.

Summary

  • Connect tools with native integrations, automation platforms, or webhooks and APIs.
  • Webhooks push events to your URL; respond fast, verify signatures and process asynchronously.
  • Make handlers idempotent because duplicates happen.
  • Use filters, clear names, error alerts and least-privilege tokens in automations.

Next: SEO Fundamentals and Site Settings