Pipedrive is where many small sales teams keep their pipeline, and the website is where most new people first appear. A Foundation CMS form can create the person in Pipedrive directly, with a REST call, and a short automation can go on to open the deal.
Overview
This integration connects Foundation CMS with Pipedrive. 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. Pipedrive's API accepts an API token in an x-api-token header, which fits that shape.
Business Context and Core Use Case
Copying enquiries from email into a CRM is a daily chore that loses leads on busy days. Creating the person in Pipedrive the moment the form is submitted means the salesperson starts from the CRM, with the name and email already there.
The Applications Involved
Foundation CMS (Foundation CMS) defines the form and delivers each accepted submission.
Pipedrive (Pipedrive) receives the person and holds the pipeline.
How the Integration Works
In the form's delivery settings, add a REST call: POST to Pipedrive's persons endpoint, with an x-api-token header carrying the API token. Map the body keys Pipedrive expects, such as name and email, to the form's questions. Every accepted submission creates the person. Creating a deal or lead as well needs the new person's id from the first call, so that second step belongs in n8n or Zapier, fed by the form's signed webhook.
Immediate Operational Value
No enquiry waits to be retyped, and nothing is lost when a question is renamed: mappings are tied to the question, not its label. If a mapped question is later removed, the field is sent empty and flagged rather than silently dropped.
Security, Access, and Governance
The token is held in the delivery settings and sent only to the HTTPS address configured. Every attempt is logged with the host reached and the result, and a channel can be paused, keeping its settings, while Pipedrive is unavailable.
Summary
A REST call puts every website enquiry into Pipedrive as a person; an automation can take it on to a deal.
Frequently asked questions
Can a Foundation CMS form create a deal in Pipedrive directly?
It creates the person directly. A deal needs the new person's id, so that step runs in n8n or Zapier from the form's signed webhook.
What if we rename a form question?
Mappings follow the question, not its label, so a rename changes nothing.
What if a mapped question is deleted?
The field is sent empty and the delivery is flagged, so the gap is noticed rather than hidden.
Applications in this integration
More integrations to explore
Airtable, Kling, PayPal and Pipedrive AI Video, CRM, Payment Processing, Tools
BigCommerce, Mailchimp and Pipedrive CRM, E-commerce, Marketing
Claude, Pipedrive and tawk.to AI LLM, CRM, Customer Support
ClickUp, Cloudflare, Pipedrive and Wordpress CMS, CRM, Infrastructure, Project Management
Pipedrive, EasyPost, n8n and Help Scout Automation, CRM, Customer Support, Logistics
Apiary and Foundation CMS CMS, Infrastructure