Getting started

Install the App

FormBridge is a no-code Webflow app by Digital Butlers LTD. It connects Webflow forms to Mailchimp, Airtable, and respond.io. Use this guide to install FormBridge, authorize a destination, configure field mapping, and disconnect or remove the app when needed.

Questions? Contact hello@digitalbutlers.team.

Installation

Install and configure FormBridge in this order:

  • Install FormBridge from the Webflow Marketplace.
  • Open FormBridge on your site in Webflow Designer.
  • Connect your Webflow project if FormBridge asks you to authorize.
  • Select an integration: Mailchimp, Airtable, or Respond.io.
  • Authorize or connect the destination (OAuth for Mailchimp or Airtable; access token for Respond.io).
  • Select the destination resource where applicable (a Mailchimp audience, an Airtable base and table, or a Respond.io workspace).
  • Select the Webflow form to connect.
  • Map Webflow form fields to destination fields.
  • Save the mapping.

Before you start

You need:

  • A Webflow account.
  • A Webflow site with at least one form.
  • Access to the Webflow site where FormBridge is installed.
  • An account with Mailchimp, Airtable, or Respond.io, plus the required permissions for the destination resource you will use.
  • Appropriate access to that resource: a Mailchimp audience, an Airtable base and table, or a Respond.io workspace.
  • An active FormBridge plan.

Plans

  • Free: One form for any service; Unlimited number of submissions; Support
  • FormBridge: $3.99/month. Unlimited number of forms; Unlimited number of services

The Free plan does not provide unlimited usage. If you need more than one connected form on a site, use a paid plan.

Supported integrations

FormBridge currently supports only these destinations:

  • Mailchimp — OAuth. Submissions add or update contacts in a selected audience.
  • Airtable — OAuth. Submissions create records in a selected table.
  • Respond.io — access token (not OAuth). Submissions create or update contacts in a selected workspace.

For each integration you authorize the destination, select the resource where applicable, select a Webflow form, map fields, save, and later disconnect from the same screen in FormBridge.

Mailchimp

Send Webflow form submissions to a selected Mailchimp audience.

Authorization

Mailchimp uses OAuth. You need a Mailchimp account with access to the audience you want to use.

  • Select Mailchimp in FormBridge.
  • Click Connect — OAuth opens in a new tab.
  • Sign in to Mailchimp and allow access for the current Webflow site.
  • Return to FormBridge.

Configuration

  • Select a Mailchimp audience.
  • Select the Webflow form to connect.
  • Email is required. Map a Webflow email field to Mailchimp Email.
  • Optionally map other Webflow fields to Mailchimp merge fields.
  • Save the mapping.

What happens on a successful submission

FormBridge processes the submission according to your mapping and adds or updates a contact in the selected Mailchimp audience.

Disconnect

In FormBridge, disconnect the form mapping or disconnect the Mailchimp account from the same screen. After you disconnect, FormBridge will not send new submissions from that mapping to Mailchimp.

Airtable

Send Webflow form submissions to Airtable as new records in a selected table.

Authorization

Airtable uses OAuth. You need an Airtable account with access to the base and table you want to use.

  • Select Airtable in FormBridge.
  • Click Connect — OAuth opens in a new tab.
  • Authorize Airtable for the current Webflow site.
  • Return to FormBridge.

Configuration

  • Select an Airtable base.
  • Select a table inside that base.
  • Select the Webflow form.
  • Map Webflow form fields to Airtable columns.
  • Save the mapping.

What happens on a successful submission

FormBridge processes the submission according to your mapping and creates a record in the selected Airtable table.

Disconnect

In FormBridge, disconnect the form mapping or disconnect the Airtable account. After you disconnect, FormBridge will not send new submissions from that mapping to Airtable.

Respond.io

Send Webflow form submissions to Respond.io as contacts in a selected workspace.

Authorization

Respond.io does not use OAuth in FormBridge. You provide an access token from your Respond.io workspace. The token must have sufficient permissions for the workspace you want to use.

  • Select Respond.io in FormBridge.
  • Paste your Respond.io access token.
  • Click Connect.

Get the token from your Respond.io workspace settings (API / access token).

Configuration

  • Select the Webflow form.
  • Identifier is required (usually email or phone). FormBridge uses it to match or create the contact.
  • Map additional Webflow fields to Respond.io custom fields as needed.
  • Save the mapping.

What happens on a successful submission

FormBridge processes the submission according to your mapping and creates or updates a contact in Respond.io based on the identifier.

Disconnect

In FormBridge, disconnect the form mapping or clear the Respond.io access token connection. After you disconnect, FormBridge will not send new submissions from that mapping to Respond.io.

Data handling

FormBridge receives Webflow form submission data and processes it according to the configured integration and field mapping. FormBridge stores delivery statistics and the integration credentials or access tokens required to connect to supported services. Mapped submission data is transmitted to the destination you selected. Submission data is not used for purposes unrelated to providing the configured integration.

Data retention and deletion follow the Privacy Policy. FormBridge does not use submission data for advertising, analytics, profiling, or AI training.

Limitations

  • Delivery depends on the destination service being available.
  • Valid authorization or credentials are required. For Respond.io, the access token must be valid and have sufficient permissions.
  • You must have sufficient permissions on the destination resource.
  • Incorrect field mappings can prevent successful delivery.
  • Required destination fields must be mapped where applicable (Mailchimp Email; Respond.io identifier).
  • FormBridge does not guarantee delivery when a destination is unavailable or misconfigured.
  • Free: One form for any service; Unlimited number of submissions; Support
  • FormBridge: $3.99/month. Unlimited number of forms; Unlimited number of services

Troubleshooting

FormBridge cannot connect to the destination

  • Confirm you selected a currently supported integration: Mailchimp, Airtable, or Respond.io.
  • Check that you are signed in to the destination account with access to the resource you need.
  • For Mailchimp or Airtable, try Connect again and complete OAuth.
  • For Respond.io, paste a current access token with sufficient permissions, then click Connect.

OAuth authorization fails

  • Allow pop-ups so the OAuth tab can open.
  • Sign in to the correct Mailchimp or Airtable account.
  • Grant the requested access for the current Webflow site.
  • Return to FormBridge and confirm the connection, or click Connect again.

Respond.io access token is invalid or expired

  • Create or copy a new access token from your Respond.io workspace settings.
  • Confirm the token has sufficient permissions for that workspace.
  • Clear the existing token connection in FormBridge if needed, paste the new token, and click Connect.

Insufficient permissions

  • Use a destination account that can access the selected base, table, audience, or workspace.
  • Ask an admin of that account to grant access, then reconnect in FormBridge.

Base, table, or audience cannot be selected

  • Finish authorization first.
  • Confirm the resource exists in the connected account.
  • Reconnect if you authorized a different account than the one that owns the resource.

A required field is not mapped

  • Mailchimp: map a Webflow email field to Mailchimp Email, then save.
  • Airtable: map the Webflow fields you need to the table columns, then save.
  • Respond.io: map an identifier (usually email or phone), then save.

A submission is not delivered

  • Confirm the mapping is saved for the same Webflow form that was submitted.
  • Confirm the destination is available and your authorization is still valid.
  • Check that required fields are mapped and that destination permissions are sufficient.
  • On the Free plan, confirm you have not exceeded one Webflow form connected to one integration per site.
  • Submit a test entry and check the selected a Mailchimp audience, an Airtable base and table, or a Respond.io workspace.

Field mapping is incorrect

  • Open the mapping in FormBridge and match each Webflow field to the intended destination field.
  • Save the mapping.
  • Submit a test entry and verify the values in the destination.
  • Use Disconnect on the form mapping if you need to reconnect under another account or rematch fields.

If you still need help, email hello@digitalbutlers.team.

Disconnecting and removing FormBridge

Disconnect Mailchimp

In FormBridge, disconnect the form mapping or disconnect the Mailchimp account from the same screen.

Disconnect Airtable

In FormBridge, disconnect the form mapping or disconnect the Airtable account.

Disconnect Respond.io

In FormBridge, disconnect the form mapping or clear the Respond.io access token connection.

Remove a form mapping

Open the connected form in FormBridge and use Disconnect to remove that form mapping.

After you disconnect

FormBridge will not send new submissions for a disconnected form or integration. Data already delivered to Mailchimp, Airtable, or Respond.io remains in that destination.

Remove FormBridge from the Webflow project

Remove FormBridge from the Webflow project using Webflow's app management for that site. After FormBridge is removed, it will no longer receive or process form submissions from that site.

Verification

After you save a mapping, submit a test entry through the selected Webflow form. Then check the selected a Mailchimp audience, an Airtable base and table, or a Respond.io workspace and confirm the mapped values appear as expected.