How to connect Base44 to Zapier, Make and n8n

Base44 talks to Zapier, Make and n8n through webhooks. To send data out, your app posts to a webhook URL from a backend function or automation. To receive data, the outside tool calls a backend function’s HTTP endpoint. Base44 has a dedicated Zapier integration that sets up the sending side for you. Everything here needs the Builder plan, because it runs through backend functions.

This is part of the Base44 integrations guide.

Base44 to Zapier#

From Base44’s Zapier guide:

1. In Zapier, click Create Zap and choose Webhooks by Zapier → Catch Hook as the trigger. Copy the webhook URL.
2. In Base44, find Zapier in the integrations catalog and click Use this integration.
3. Paste the URL into the ZAPIER_WEBHOOK_URL field.
4. Ask the chat what to send and when, for example When a new Booking is created, send its customer name, email, start time and duration to Zapier.
5. Trigger a test so Zapier loads real fields, add your action (such as Google Calendar → Create Detailed Event), and publish the Zap.

Two requirements: the Builder plan on Base44, and a paid Zapier plan, since Zapier’s webhooks are a premium feature.

Base44 to n8n or Make#

The same pattern works without a dedicated integration:

1. In n8n, add a Webhook trigger node (or in Make, a Custom webhook) and copy its URL.
2. In Base44, store the URL as a secret and ask the chat:

Create a backend function that posts new Order records to the webhook URL in the
N8N_WEBHOOK_URL secret, with the order ID, customer email, total and created date as
JSON. Run it from a data event automation whenever an Order is created.

3. Place a test order and check that n8n received it.

Data event automations run when records are created, updated or deleted. Each run uses 1 integration credit.

Receiving webhooks in Base44#

Every backend function “gets its own HTTP endpoint,” which is how Base44 receives callbacks from Stripe, GitHub, n8n or anything else. A minimal receiver:

// base44/functions/incomingLead/entry.ts
import { createClientFromRequest } from "npm:@base44/sdk";
import { secrets } from "base44:runtime";

export default async function (req: Request): Promise<Response> {
  if (req.headers.get("x-webhook-secret") !== secrets.get("WEBHOOK_SECRET")) {
    return new Response("unauthorized", { status: 401 });
  }
  const body = await req.json();
  const base44 = createClientFromRequest(req);
  await base44.asServiceRole.entities.Lead.create({ email: body.email, source: body.source });
  return Response.json({ ok: true });
}

Two things to get right: check a shared secret or the sender’s signature before trusting the payload, and read secrets inside the handler, since Base44 resolves them per request. Functions time out after five minutes.

Automations, connectors or an outside tool?#

For the last row, a hosted form backend such as LinkyCal sends submissions to Slack, Google Sheets, WhatsApp or a webhook without any backend function, which also works on Base44’s Free plan. See the contact form guide.

What to do next#

1. Decide whether Base44’s own automations and connectors already cover the workflow.
2. If not, set up the Zapier integration or a webhook to n8n or Make.
3. Protect any incoming webhook with a shared secret.