# Save landing-page enquiries in Airtable

> Map Pageree form submissions into a useful Airtable table through a webhook workflow. Check field types, permissions, repeated enquiries, and the final record.

- Canonical: https://pageree.com/integrations/airtable/
- 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.** Design the Airtable table first, then use an automation webhook to map actual submitted fields. Keep enquiries distinct from people, handle types and blanks deliberately, and verify the final record. Webhook acceptance alone is not a successful Airtable write.

## Give each enquiry a useful record

Route Pageree enquiries to an Airtable table through an automation webhook, then map the incoming fields to a deliberately designed record. A table with clear types and ownership is more useful than a generic JSON dump. Decide whether it stores people, enquiries, or both before deciding how to handle duplicates.

The recipe below is based on current Airtable documentation and Pageree's delivery implementation. It needs configuration and testing in your own accounts; no live base or customer record was used to verify it. If you need a simple grid without Airtable-specific field types, the [Google Sheets recipe](https://pageree.com/integrations/google-sheets/) is another starting point.

## Prepare a small enquiry table

For a project-request table, use one record per enquiry and connect it to a person table later if needed. Repeated email addresses can represent different projects. Avoid replacing an earlier enquiry just because a prospect returns with another request.

| Airtable field | Suggested type | Incoming value |
| --- | --- | --- |
| Name | Single line text | `data.name` |
| Email | Email | `data.email` |
| Project | Long text | `data.message` or the actual scope field |
| Page | URL | `page` |
| Delivery time | Date with time | `submittedAt` |
| Status | Single select | An existing option such as New |

Optional empty values, numeric fields, linked records, and single-select choices need explicit handling. Do not feed a budget string such as “under five thousand” into a number field and expect automatic interpretation. Preserve it as text or convert a controlled option in the automation.

## Connect a webhook and a record action

Create a [Make scenario](https://pageree.com/integrations/make/) or [Zapier workflow](https://pageree.com/integrations/zapier/) with a webhook trigger and an Airtable create-record action. Authorize access to the intended base and table. Send Pageree's default JSON payload to the generated webhook URL and map the actual received sample.

For a custom integration, the record collection is `https://api.airtable.com/v0/{baseId}/{tableIdOrName}`; do not append `/records`. Use `POST` with JSON shaped as a record's `fields`, or a `records` array of objects containing `fields` for the batch form. Airtable's [official client implementation](https://github.com/Airtable/airtable.js/blob/master/src/table.ts) shows those create shapes; its [API troubleshooting guide](https://support.airtable.com/articles/2111090641-airtable-api-common-troubleshooting) covers path and type errors.

Authenticate with `Authorization: Bearer <personal-access-token>` in secure server-side settings. The token needs record-write scope and access to the target resource, and the associated user needs permission to write. Airtable explains scope and resource selection in its [personal access token guide](https://support.airtable.com/articles/9934989703-creating-personal-access-tokens). Never put the token into the landing page or ask a visitor to provide it.

## Copy this configuration prompt

```text
Send enquiries from Pageree page [page ID] to Airtable using
[approved automation webhook]. Target: [base and table IDs].
Read the actual form schema. Design one record per enquiry,
with Name, Email, Project, Page, Delivery time, and Status.
Confirm the existing Airtable field names, types, and select options.

Use the default Pageree JSON payload. Convert values only in the
automation where the conversion is explicit. Keep optional blanks
safe and preserve repeated projects from the same email address.
Store authentication securely. Show mappings for review, then
provide tests for the final record, duplicates, and action failure.
Do not say the record exists until the destination is checked.
```

## Verify the record, not only the webhook

Use the published page for the integration test: preview submissions go to email rather than the HTTP destination. Submit a clearly marked test, inspect the automation run, and open the resulting Airtable record. Check the date, punctuation, multiline text, and any optional blanks. Airtable notes that empty fields can be absent from fetched records in its [Web API introduction](https://support.airtable.com/articles/6292134965-getting-started-with-airtable-s-web-api).

Then test a second project from the same person. If you choose deduplication, document a workflow identifier you can actually preserve. Pageree's delivery timestamp is not a stable submission ID. Ensure a retry after a partial write will not silently overwrite a separate enquiry.

A successful webhook response can precede a failed Airtable action. Review automation errors and destination permissions, including field restrictions. Pageree's owner-email fallback and 30-day accepted-lead backup help with recovery, but they do not prove the Airtable record was created. Recheck mappings when you rename a form field or change a table type.

## Related
- [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.
- [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.

## 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.