Slack is where a team notices things. A Foundation CMS form can post each enquiry straight into a Slack channel through an incoming webhook, and for the sites we run, the platform's health alerts arrive in Slack in Slack's own message format.
Overview
This integration connects Foundation CMS with Slack. Foundation CMS is Swarm Labs' multi-tenant content management system on Cloudflare Workers. It holds a site's content and hands it to the site as whole, typed records, and every site runs as its own Worker with its own database and media bucket. Form delivery in Foundation CMS includes a REST call: a method, an HTTPS address, one authentication header, and a JSON body whose keys you name and fill from the form's questions or from fixed values. A Slack incoming webhook takes exactly that kind of body.
Business Context and Core Use Case
An enquiry that waits in an inbox goes cold. Many small teams want new enquiries to appear where they already talk, so somebody picks them up in minutes. Separately, the people running the platform want alerts somewhere they will see them, not on a screen nobody is watching.
The Applications Involved
Foundation CMS (Foundation CMS) delivers form submissions and raises health alerts.
Slack (Slack) receives them in a channel through an incoming webhook.
How the Integration Works
Create an incoming webhook in Slack for the channel. In the form's delivery settings, add a REST call: POST to the webhook's address with a body key of text, filled from the form's message question or from a fixed line such as "New enquiry from the website". For richer messages that combine several answers, send the form's signed webhook to n8n or Zapier and build the Slack message there. Platform alerts use a webhook whose format is set to Slack, so they arrive as Slack messages.
Immediate Operational Value
Enquiries reach the team in seconds, and the email delivery can stay on alongside it as the record. Alerts about the sites arrive where someone will act on them.
Security, Access, and Governance
Delivery only goes to HTTPS addresses; plain http is refused. Every attempt is logged with the host it reached and the result, so a Slack webhook that has been revoked shows up as failed deliveries.
Summary
A Slack incoming webhook and a REST call in the form's settings put every enquiry in front of the team, while platform alerts land in Slack in its own format.
Frequently asked questions
Can each enquiry post to Slack without an automation tool?
Yes. A REST call delivery can post to a Slack incoming webhook with a text field taken from the form.
Can the Slack message include every answer, nicely formatted?
For that, send the form's signed webhook to n8n or Zapier and compose the message there; the direct call sends one text field.
Will email delivery still work?
Yes. A form can deliver by email and to Slack at the same time.
