Form Field Mapping

Mapping tells FormRelay which Webflow form field belongs in which field at the destination.

Creating a mapping

1. Open Sites, choose your site, and find the form.
2. Click + Add destination.
3. Pick a connection from Integration.
4. Pick a destination — the Notion database, Airtable table, Slack channel, Mailchimp audience, and so on. FormRelay reads these live from the destination, so if a list is missing there, create it first and reopen the dialog.
5. Match each Webflow field to a destination field.
6. Click Save.

A form can send to several destinations at once, one of each kind. Map it to Mailchimp and Slack and add a webhook, and every submission goes to all three, each with its own delivery record. Mailchimp and Slack each get their own field mapping; the webhook receives the whole submission.

Two destinations of the same kind on one form are not allowed, because every submission would arrive twice with nothing to tell the copies apart. To reach two places in the same tool, such as two Slack channels, send to a Webhook, Zapier or Make connection and branch from there.

What FormRelay receives, and what each destination gets

These are two different things, so it helps to keep them apart.

What FormRelay receives is the whole submission, exactly as the published page sent it to Webflow: every field, under the field names Webflow uses, including fields added since Webflow's field list was last synced. Fields whose names look like credentials (passwords, PINs, one-time codes, card verification numbers) are dropped on arrival and never stored or forwarded. See Where Does Your Collected Lead Data Go?.

What a destination gets depends on its kind:

• Mapped destinations (Notion, Slack, Discord, Airtable, HubSpot, Mailchimp, Klaviyo, Brevo, MailerLite, EmailOctopus, Moosend, Omnisend, Sender) receive only the fields you mapped, written into the destination fields you chose. Unmapped fields are not sent. Leave a row unset and that value is omitted rather than sent empty. A field FormRelay received but that is not in the mapping goes nowhere until you map it.
• Webhook, Zapier and Make receive the whole submission as JSON, every field FormRelay received, with no mapping table. The connection dialog shows the exact payload shape instead. Pick out the fields you need on the receiving side.

What the field list shows

The left column lists the fields Webflow reports for that form; the right column lists the fields available at the destination, fetched live.

• Field types are respected. Destination fields FormRelay cannot write to — a Notion people property, for example — are shown and marked not supported rather than hidden, so it is clear why they are unavailable.
• Credential-like fields never appear, because they are dropped before anything is stored, whatever the mapping says.

If the field list looks wrong

Webflow's reported field list can lag the published page — a form that submits three fields sometimes reports one. FormRelay still receives everything the page submits, and Webhook, Zapier and Make still get all of it. For a mapped destination, a field that is missing from the list cannot be mapped yet, so it is not forwarded there until the list is refreshed and you map it. Republish the site and click Sync on the Sites page to refresh it.

Changing a mapping

Use Edit on the form card. Changes apply to the next submission; they do not re-send anything already delivered. To re-send a past submission after fixing a mapping, use Replay on that entry in the Logs page.