FormRelay
Prerequisites
What you need before connecting FormRelay.
A Webflow site with a form
- A Webflow site on a paid site plan, or published to a
.webflow.iostaging domain. Webflow only sends form submissions to apps from a published site. - At least one form on a published page. FormRelay reads your forms through Webflow's API — it does not add forms or scripts to your site.
- Give each form a distinct name in the Designer. Webflow names them all "Email Form" by default, which makes them hard to tell apart when mapping.
A Webflow account that can authorize apps
Authorizing FormRelay registers a form_submission webhook on every site in the Webflow workspace you authorize — there is no per-site selection step. If you only want a subset connected, authorize a workspace that contains only those sites.
A FormRelay subscription
Each site needs its own subscription before submissions are forwarded. Billing is handled by LemonSqueezy, who are the merchant of record. Until a site is subscribed, FormRelay records that a submission arrived but does not deliver it.
An account with the destination
Every destination needs an account you control, and most need one extra thing:
| Destination | What you need |
|---|---|
| Notion, Slack, Airtable, Discord | An account, plus permission to install apps. Discord additionally needs a server where you have Manage Server. |
| HubSpot | Super admin access, to create a private app access token. |
| Mailchimp, Klaviyo, Brevo, MailerLite, EmailOctopus, Moosend, Omnisend, Sender | An API key with write access, and at least one list or audience to send to. |
| Webhook, Zapier, Make | An endpoint URL that accepts a POST with a JSON body. |
Where a destination needs a specific scope or permission, its own page lists it.
Allowlisting FormRelay's IP addresses
Some destinations let you restrict API access to specific IP addresses. If you use that, add all three of the addresses FormRelay delivers from:
208.77.244.240
152.55.184.241
152.55.185.190
Outbound traffic is balanced across the three, so all three must be allowed — permitting one address will appear to work and then fail on the next delivery that uses another.
These addresses are fixed for the region FormRelay runs in (Amsterdam). If they ever change we will update this page and announce it before the change takes effect.
They are shared Railway addresses rather than dedicated to FormRelay, so allowing them permits traffic from other services hosted on the same infrastructure. If your security policy requires a dedicated address, tell us at contact@faizatech.com and we will look at options.
Costs outside your FormRelay subscription
Destinations bill you separately under their own plans. Some — HubSpot and Klaviyo in particular — meter API usage or contact counts on paid tiers. FormRelay does not resell or mark up any of them.