Faizatech Support
← All products

Getting Started

Using FormRelay

Destinations

FormRelay

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 a webhook, and every submission goes to all three, each with its own field mapping and its own delivery record.

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

  • Unmapped fields are not sent. Leave a row unset and that value is omitted rather than sent empty.
  • 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 are dropped before delivery regardless of mapping. See Where Does Your Collected Lead Data Go?.

Webhook, Zapier and Make need no mapping

These receive the whole submission as JSON, so there is nothing to match up. The connection dialog shows the exact payload shape instead of a mapping table. Pick out the fields you need on the receiving side.

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. Whatever the published page actually submits is what gets sent, including fields added since the list was last synced. 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.