# Send landing-page form submissions to Zapier

> Configure a Zapier Catch Hook for Pageree submissions, map the real payload, and verify the destination action. Learn plan requirements and recovery limits.

- Canonical: https://pageree.com/integrations/zapier/
- Published: 2026-09-15. Updated: 2026-09-15.
- Collection: Integrations (https://pageree.com/integrations.md)
- Site index for agents: https://pageree.com/llms.txt

**The short answer.** Use a Catch Hook to receive Pageree's JSON payload, then connect a destination action. Current Zapier webhook triggers require an eligible paid plan. Check the enabled workflow and final record: a successful webhook response does not prove the later action ran.

## Use Zapier as the workflow between a form and its destination

Pageree can send a form submission to a Zapier Catch Hook, then Zapier can create the row, contact, or other record your business needs. The complete workflow has two checkpoints: Zapier receives the payload, and the destination action succeeds. A green webhook receipt only establishes the first.

This recipe describes setup and verification in your own accounts. It is not a native Pageree Zapier app or a claim that a live destination has been tested. Zapier's current [webhook-trigger documentation](https://help.zapier.com/hc/en-us/articles/8496288690317-Trigger-Zap-workflows-from-webhooks) lists this feature on paid plans, so confirm access before building a process around it.

## Create the trigger and choose the destination

Create a Zap with Webhooks by Zapier as the trigger and Catch Hook as its event. For Pageree's ordinary JSON payload, that parsed trigger is the useful starting point. Catch Raw Hook serves a different need when you want unparsed content and headers.

Copy the unique trigger URL generated in your Zap. Use the exact URL rather than assembling one from an example. Configure it as Pageree's server-side HTTP delivery destination with method POST. No universal Zapier API key belongs in a standard Catch Hook request; the generated URL must be handled as sensitive connection information and kept out of your public HTML.

Leave the optional child-key extraction unset initially so the received sample includes page, form, delivery time, and submitted values. Then connect the destination app using Zapier's supported account connection. Select the actual table, spreadsheet, CRM object, or list rather than relying on an account default.

## Map the real payload

Without a custom mapping, Pageree sends an object with `form`, `page`, `submittedAt`, `data`, and `meta`. The values inside `data` use the names from your published form. Do not configure the Zap around guessed labels from a screenshot.

| Received field | Example use in a destination action |
| --- | --- |
| `data.name` | Contact or enquiry name |
| `data.email` | Reply address or contact lookup |
| `data.message` | Enquiry body |
| `form` | Identify which page form was used |
| `page` | Page URL for context |
| `submittedAt` | Delivery timestamp for reporting |

The timestamp is generated when Pageree builds the delivery payload; it is not a stable submission identifier for replay deduplication. If you need exactly one destination write per accepted workflow event, design and persist an appropriate workflow identifier. Do not merge distinct enquiries just because the same person submitted them.

## Copy this setup prompt

```text
Configure HTTP delivery for existing Pageree page [page ID]
to the exact Zapier Catch Hook URL I provide privately.
Destination: [app, account, and object/table/list].

Read the published form schema and use the default JSON payload.
Keep the webhook URL and app credentials out of the page source.
Explain the mapping from data fields to the destination action.
Include lookup/duplicate handling only where it matches the business
process. Show the configuration for review before changing delivery.
Help me test a public submission through the final destination,
including optional blanks, repeat enquiries, and action failure.
Never equate webhook acceptance with a completed destination write.
```

## Verify the published-page journey

Use a controlled test address and a distinctive test message. Preview forms do not send to the configured HTTP destination, so a private preview email cannot test this Zap. After the form is published, send the test, select its sample in the trigger, and inspect the mapped destination action.

Verify the final record in the destination app. Turn on the finished Zap and repeat from the public page; an editor test is not proof that the enabled workflow behaves identically. Check a missing optional value, a long message, and a repeat enquiry. Record what each test should create before running it.

## Monitor what can fail after a successful trigger

The trigger response cannot confirm a later app action. Zapier also documents a delay before a disabled or deleted webhook starts returning an error, so a success response alone does not establish that a Zap is enabled. Check Zap history and the actual destination when diagnosing a missing lead.

If Pageree's HTTP request fails, owner-email fallback can preserve the message. When fallback succeeds, that delivery is not automatically retried to Zapier. Accepted leads remain available for 30 days, allowing a controlled recovery after repairing the workflow. Reconcile partial writes before replaying to avoid duplicates.

For complete destination planning, read the [Google Sheets recipe](https://pageree.com/integrations/google-sheets/) or [HubSpot guide](https://pageree.com/integrations/hubspot/). If no destination action is needed yet, [email delivery](https://pageree.com/guides/landing-page-form-to-email/) is a shorter path to a usable enquiry.

## Related
- [Send landing-page leads into a Make scenario](https://pageree.com/integrations/make.md): Build a Make webhook workflow for Pageree leads. Define the data structure, secure authentication, destination mapping, error handling, and verification.
- [Trigger an n8n workflow from a landing-page form](https://pageree.com/integrations/n8n.md): Connect Pageree HTTP delivery to n8n. Use an illustrative JSON scaffold, distinguish test and production webhooks, map fields, and verify destination failures.
- [Send landing-page leads to Google Sheets](https://pageree.com/integrations/google-sheets.md): Plan a Pageree-to-Google-Sheets workflow using an automation webhook. Map fields, protect credentials, verify the created row, and handle delivery failures.

## Build it with your agent

Pageree is an MCP server. Add https://mcp.pageree.com/ to an MCP client that supports Streamable HTTP and OAuth, sign in, and the agent can build, publish and measure the page. Setup for every supported client: https://pageree.com/docs.md. Sign up: https://console.pageree.com/signup.