Make's visual scenarios suit the branching jobs that follow a website enquiry: route by service, enrich, notify, file. A Foundation CMS form hands each submission to a Make custom webhook, signed by the site, and Make's HTTP module can publish back to the site through the content API.
Overview
This integration connects Foundation CMS with Make. 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. The connection uses two standard doors: a form's webhook channel pointed at a Make custom webhook, and the content API called from Make's HTTP module with a site key as a Bearer token.
Business Context and Core Use Case
An enquiry is rarely one action. A quote request might need routing by region, a record in the CRM, a calendar hold and a message to the right person. Make draws that as one scenario with routers and filters. The CMS's part is to deliver the enquiry completely and verifiably, and to accept content back when a scenario needs to update the site.
The Applications Involved
Foundation CMS (Foundation CMS) sends the signed submission and exposes the content API.
Make (Make) receives, branches and acts, and can write back to the site.
How the Integration Works
Add a custom webhook in Make and set its address as the form's webhook destination. Each accepted submission arrives as the Foundation CMS envelope with its signature. To write back, use the HTTP module to call /api/v1/content/{type} with a key scoped to that site and type.
Immediate Operational Value
Complex routing lives in a scenario the team can see and change, while the website stays simple: the form is defined once in the CMS and its answers arrive in Make whole.
Security, Access, and Governance
Form webhooks are signed over their timestamp as well as their body, with a secret shown once when it is made, so the receiver can reject anything that did not come from the site and a captured request cannot be replayed. Paused is a real state for a delivery channel, so if a scenario is being rebuilt the channel can be paused without losing its settings. API keys reach one site only.
Summary
Make takes a Foundation CMS enquiry wherever it needs to go, and can write to the site in return, through a signed webhook and a scoped key.
Frequently asked questions
Does Make need a special connector for Foundation CMS?
No. A custom webhook receives form submissions, and the HTTP module calls the content API.
What happens if the scenario is switched off?
Pause the form's webhook channel; paused keeps its configuration, and every attempt is logged.
Can Make update the website?
Yes, with a site key scoped to the content types it needs to write.
Applications in this integration
More integrations to explore
ChatGPT, Asana, Make and tawk.to AI LLM, Automation, Customer Support, Project Management
Help Scout, Zapier, Mid Journey and Make AI Image, Automation, Customer Support
Make and Surecart Automation, E-commerce
Plesk, Webhook, Make and Eleven Labs AI Audio, Automation, Infrastructure
Make and Time Hive Analytics, Automation
Apiary and Foundation CMS CMS, Infrastructure