Trigger an n8n workflow from a landing-page form

Use a webhook to start the workflow

Pageree can deliver an accepted form submission to an HTTP endpoint. An n8n Webhook node can receive that request and start a workflow that maps fields, writes a CRM record, or alerts your team. This is a configured HTTP workflow, not a native Pageree n8n app.

You need an n8n instance reachable over HTTPS, permission to create and publish workflows, and credentials for the eventual destination. The recipe below is based on documentation reviewed September 15, 2026. The example JSON is an illustrative import scaffold; it has not been executed in an n8n account or connected to a live customer form.

Keep test and production URLs separate

n8n gives a Webhook node separate test and production URLs. The test URL listens during a test session; the production URL is registered when the workflow is published. Production runs are inspected in Executions. Response mode also matters: responding immediately acknowledges the start, while responding after the workflow finishes can reflect later work. See the official Webhook node documentation.

Keep the page’s form posting to its Pageree endpoint. Configure delivery server-side to call n8n; do not replace the public form action with a secret webhook URL. Use Header Auth in n8n and configure the matching header through the approved Pageree delivery settings. Credentials belong in those settings, not in public HTML.

Import an inspection scaffold

Save the following as pageree-webhook-inspection.json and import it into a new workflow using your n8n version’s JSON import control. It receives a POST, extracts the default Pageree payload, and returns a small acknowledgement. It intentionally contains no credential and no CRM write. Configure authentication before exposing it, and add your destination before treating it as a production lead workflow.

{
  "name": "Pageree enquiry inspection - configure before use",
  "active": false,
  "nodes": [
    {
      "id": "pageree-receive",
      "name": "Receive enquiry",
      "type": "n8n-nodes-base.webhook",
      "typeVersion": 2,
      "position": [0, 0],
      "parameters": {
        "httpMethod": "POST",
        "path": "pageree-enquiry-inspection",
        "responseMode": "responseNode",
        "options": {}
      }
    },
    {
      "id": "pageree-map",
      "name": "Inspect fields",
      "type": "n8n-nodes-base.code",
      "typeVersion": 2,
      "position": [240, 0],
      "parameters": {
        "jsCode": "const body = $input.first().json.body; if (!body || typeof body.data !== 'object' || !body.data || Array.isArray(body.data)) throw new Error('Expected Pageree data object'); const data = body.data; return [{ json: { email: String(data.email || '').trim(), name: String(data.name || '').trim(), message: String(data.message || ''), sourcePage: String(body.page || ''), form: String(body.form || '') } }];"
      }
    },
    {
      "id": "pageree-response",
      "name": "Acknowledge inspection",
      "type": "n8n-nodes-base.respondToWebhook",
      "typeVersion": 1.4,
      "position": [480, 0],
      "parameters": {
        "respondWith": "json",
        "responseBody": "{\"received\":true,\"destinationConfigured\":false}",
        "options": {"responseCode": 200}
      }
    }
  ],
  "connections": {
    "Receive enquiry": {"main": [[{"node":"Inspect fields","type":"main","index":0}]]},
    "Inspect fields": {"main": [[{"node":"Acknowledge inspection","type":"main","index":0}]]}
  },
  "settings": {"executionOrder":"v1"}
}

Use fictional data for the first test. Inspect body.data in the actual received request before trusting the field names. A custom Pageree delivery mapping can change the payload shape. Rename the example fields to match the published form, and validate required values before a destination action.

Add the business destination

Insert your authenticated CRM or table action between inspection and acknowledgement. For HubSpot, decide how an existing email is updated and where the new enquiry is stored. For Airtable, map into the actual table’s typed columns. Do not assume each delivery should create another person record.

Plan duplicate handling using an appropriate durable identifier for your own workflow. Pageree’s default payload should not be assumed to contain a stable submission ID; its delivery timestamp is not a dependable deduplication key. A repeated enquiry can also be legitimate, so preserve the new message while avoiding unwanted duplicate contacts.

Verify failure behavior before switching the URL

Test a normal enquiry, a missing required value, a repeated email, and a destination failure. Inspect both the n8n execution and the final record. If you return success before the destination writes, n8n must own alerting and recovery for a later failure. If you wait for the destination, keep execution within the caller’s timeout and handle partial writes before retries.

After configuration is verified, publish the workflow and put the exact production URL into Pageree’s delivery settings. Send a controlled test through the public page. Draft form tests use email and do not establish production webhook behavior.

Failed Pageree HTTP delivery can fall back to owner email; successful fallback does not mean n8n completed. Accepted enquiries have a 30-day recovery backup. Use the email-delivery guide to understand that fallback, and monitor n8n separately after any successful webhook acknowledgement.