A broken form doesn't look broken. The page loads, the visitor presses "Send", the success message appears, and the enquiry never reaches the spreadsheet your client checks every morning.

Usually the client is the one who notices, weeks later, when it has been "very quiet lately". By then the leads have gone cold, and the first call is to you.

Forms Bridge already checks every client's connection each morning. With Slack alerts switched on, the result comes to you instead of waiting on a dashboard: one message when a connection breaks, saying what is wrong and what to do, and one when it works again.

This guide shows how to set it up. It takes about five minutes, works on Slack's free plan, and you only do it once for all your clients.

What you'll get

Each alert is a short Slack message in a channel you choose:

  • The project and client, for example Northwind website (Emma): needs attention.
  • What is wrong, in a sentence, such as "The script's Google access was removed, so submissions can't be saved."
  • What to do about it, such as "Your client needs to approve the script again: the project page has the link."
  • A link straight to the project in Forms Bridge.

When the problem is fixed, a second message follows: Northwind website (Emma): working again.

You get one message per change, not one every morning. A connection that stays broken for a week doesn't send seven alerts, and a slow answer from Google is never reported as a problem.

The messages name the project and the problem. They never contain anything your client's visitors submitted: Forms Bridge doesn't have that data, because submissions go straight from Webflow to your client's own sheet.

What sends an alert

Forms Bridge checks each finished connection every morning, and again whenever you press "Check now" on a project. You get an alert when:

  • Your client's Google access to their script was removed, often during a security clean-up of their Google account. Submissions stop until they approve the script again.
  • The script no longer answers at its address, because it was deleted, or deployed again in the Apps Script editor.
  • A tab or column was renamed or deleted in the client's sheet.
  • Something changed on the Webflow side of a connected site: the API token was deleted, a form was removed, or the site was never published.
  • A form has been quiet for 30 days, which usually means the webhook was removed in Webflow or the site was unpublished.

Step 1: create an incoming webhook in Slack

An "incoming webhook" is a private address that posts messages into one Slack channel. Slack lets you create one through a small app of your own. You don't need any code.

  1. Open api.slack.com/apps in your browser and sign in with your Slack account.
  2. Click Create New App, then choose Blank app (in older versions of the page this option is called "From scratch").
  3. Name it, for example Forms Bridge alerts, pick your workspace, and click Create App.
  4. In the left-hand menu, click Incoming Webhooks and switch it on.
  5. Scroll down and click Add New Webhook.
  6. Pick the channel the alerts should go to, for example a new #client-alerts channel, and click Allow.
  7. Back on the same page, under Webhook URL, click Copy. The address starts with https://hooks.slack.com/services/.

Two things that sometimes get in the way:

  • If you're not an admin of the workspace, Slack may ask an admin to approve the app first.
  • To post into a private channel, you need to be a member of it before it appears in the list.

Step 2: add it to Forms Bridge

  1. In Forms Bridge, open My account.
  2. In the Alerts card, paste the Slack address into the field.
  3. Click Add channel.

Forms Bridge recognises it as a Slack address and sends a test message straight away: "Forms Bridge alerts are set up". If it arrives in your channel, you're done.

If it doesn't, the Alerts card shows what Slack answered next to the channel. The most common cause is a webhook that was deleted or belongs to an app that was removed; create a new one and add it again.

Good to know

  • One channel covers every client. Alerts for all your projects go to every channel you add. You set this up once, not per client.
  • Add more than one channel if you need to, up to ten. For example a team channel, and a webhook into your own tools.
  • Not on Slack? The same field takes any https webhook address. Forms Bridge then sends the alert as JSON (event, project, status, issues), so you can route it through Zapier, Make, n8n or your own server into email, a ticket system or a status page.
  • The address is a secret. Anyone who has it can post into your channel, so Forms Bridge stores it encrypted and only ever shows its last four characters. Treat it like a password.
  • To stop the alerts, click Remove next to the channel in My account, or delete the webhook in Slack.

What to do when an alert arrives

Open the project from the link in the message. Its Connection health card says what happened and what to do, step by step. The two most common cases:

  • "Your client needs to approve the script again." Copy the link from the card and send it to your client. They open it, choose their Google account and click Allow. One click for them, and nothing has to be set up again.
  • "A tab or column is missing." Put the tab or column heading back exactly as it was in the client's sheet, then press Check now.

Submissions aren't lost while a connection is broken: Webflow keeps every one in the site's Forms inbox, so missed entries can be exported and added to the sheet afterwards.

The short version

  • Create an incoming webhook in Slack: api.slack.com/apps → Create New App → Blank app → Incoming Webhooks → Add New Webhook → copy the address.
  • Paste it into My account → Alerts in Forms Bridge and click Add channel. A test message confirms it works.
  • From then on you hear about a broken connection the morning it breaks, and again when it's fixed, for every client, in one channel.