Copper CRM

A Webflow form stores its submissions in site settings and emails a notification. It does not create a CRM record, assign an owner, or start a follow-up sequence, so someone on the sales side still retypes every inquiry into the pipeline by hand.

Copper closes that gap. Submissions become CRM records as they arrive, Copper's own automations handle the first reply and the task that follows, and records can travel the other way to keep pages on your site current. Copper has no app in the Webflow Marketplace, so this connection is something you assemble rather than install.

The pairing fits sales teams that already run on Google Workspace. Reps at agencies and consultancies who work out of Gmail see new Webflow leads inside the inbox through Copper's Chrome extension, and marketing managers shipping lead-gen landing pages get campaign-to-pipeline visibility without CSV exports.

How to integrate Copper with Webflow

What is Copper? Copper is a CRM built around Google Workspace. A Chrome extension puts it inside Gmail and Google Calendar, and it syncs email, contacts, files, calendar events, and Drive documents against CRM records. Layered on top are visual sales and project pipelines, native contact forms, contact enrichment, task and workflow automation, and reporting, spread across Basic, Professional, and Business plans.

Teams pair Copper with Webflow to wire the marketing site into the sales pipeline. The common setup captures contact form submissions as Copper leads, sends a follow-up email, and opens an opportunity once someone replies. With no app to install, every connection runs one of three ways.

Pick the path by how much control the build needs. Copper form embeds drop Copper's own form onto a Webflow page with a pasted snippet and nothing in between. Zapier, Make, and n8n map Webflow form submissions and orders onto Copper records without code. The Webflow Data API paired with Copper's Developer API buys you deduplication logic, field mapping, and two-way Webflow CMS sync in exchange for server-side work. Most builds end up combining two of them.

Add Copper forms with the Code Embed element

Copper's native forms create or update the contact behind a submission, and they can open companies and pipeline records at the same time. Copper offers three placements: a widget that overlays every page, an embed scoped to one page, and a shareable link. The embed is an <iframe> snippet carrying your form ID, per Copper's install guide, and it goes into a Code Embed element on the page where the form belongs.

To set up the integration:

1. Build the form in Copper, following the Creating a Lead form guide. Only admins and account owners can create forms.
2. Copy the embed snippet for the page the form should live on.
3. In Webflow, drag a Code Embed element onto that page and paste the snippet.
4. Publish the site and submit a test entry to confirm it reaches Copper.

What happens after a submission depends on the Copper plan:

• Contact creation and tagging: Every plan creates or updates the contact behind a submission and can tag them automatically, which covers a plain contact form.
• Task and pipeline records: Basic, Professional, and Business can create a task tied to the contact and open a pipeline record when someone submits.
• Auto-response email: Professional and Business can fire an automated reply through a Copper email automation, so the lead hears back before a rep opens the record.
• Branding removal: The "Powered by Copper" line comes off the form on the Business plan only, which matters on a client-facing page.

Copper's forms overview lists these tiers, so confirm the plan before you promise a client an auto-responder. If a script has to load on every page instead, put it in Site settings > Custom code, and custom code in head and body tags covers where each block belongs. Code Embed and site-wide custom code both need a paid Workspace or an active Site plan, and a single Code Embed caps at 50,000 characters.

Connect with Zapier, Make, or n8n

Automation platforms are the practical no-code route, and Zapier is the best documented of the three. Copper puts the Zapier integration on every plan, and Zapier ships ready-made Copper and Webflow templates, so most setups are configuration rather than building.

The pairings teams actually reach for break down like this:

• Form submission to lead: Webflow's New Form Submission trigger feeds Copper's Create/Update Lead action, the standard contact-form path, and it deduplicates on match criteria.
• Form submission to person or opportunity: The same trigger can create a Person, a Company, or an Opportunity instead, which suits qualification forms that should land mid-pipeline.
• New order to opportunity: Webflow's New Order and Updated Order triggers push ecommerce activity into Copper as opportunities you can report revenue against.
• Copper record to Collection item: A new or changed Copper record can create or update a Collection item, which is how a client roster on the site stays current without an engineer.

Zapier also exposes Webflow's comment triggers, useful when review activity on a page should show up in the CRM. One catch to plan around: our Zapier setup guide notes that a form must have received at least one submission before Zapier can connect it, so send a test entry first.

Make covers the same ground with smaller pieces. Its Copper app, listed under ProsperWorks, carries create, get, list, update, and delete modules for leads, people, companies, opportunities, projects, tasks, and activities, plus event listeners that receive Copper webhooks directly. On the other side, Make's Webflow connection reaches forms, comments, ecommerce items, pages, and assets. The n8n Copper node supports create, delete, get, get all, and update on companies, leads, people, opportunities, projects, and tasks, which suits branching workflows you would rather self-host.

Build with the Webflow and Copper APIs

The API route is for teams with server-side resources and a reason to own the logic: custom deduplication, field mapping, activity logging, or two-way sync with conflict handling. Copper's API is v1 and lives at https://api.copper.com/developer_api/v1.

Authentication is header-based, and getting the header names wrong is the most common first failure. Every Copper request carries X-PW-AccessToken holding your API key, X-PW-Application set to developer_api, X-PW-UserEmail holding the email of the user who generated that key, and Content-Type: application/json. Generate the key under System settings > API Keys. Copper rate limits at 180 requests per minute and answers 429 past that, with bulk endpoints capped at 3 requests per second. For anything you plan to distribute, Copper names OAuth 2.0 as its preferred approach for partner integrations.

Each API owns a different part of the flow:

• Copper Developer API: Handles leads, people, companies, opportunities, activities, and custom field definitions, and it is where deduplication actually happens.
• Webflow form submissions: The submissions endpoints read what your forms have already collected, which is how you backfill leads captured before the integration existed.
• Webflow CMS items: The collection item endpoints write CRM data onto the site, either as a staged draft or straight to live.
• Webflow webhooks: Webhook registration pushes events to you in real time, covering form submissions, new orders, and CMS item changes.

Build against v2 only, because Webflow deprecated the v1 API on March 31, 2025 and it no longer receives maintenance or support. The two flows below cover each direction.

Send Webflow form submissions to Copper

This flow replaces the automation platform with your own endpoint. Webflow fires a webhook on each submission, your server verifies it, and a Copper call creates or updates the record.

To implement it:

1. Register a webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks using the sites:write scope. The filter field is supported only on the form_submission trigger, so use it to target one form:

{
  "triggerType": "form_submission",
  "url": "https://your-middleware-url.com/webhook",
  "filter": { "name": "Contact Form" }
}

2. Verify each request with the x-webflow-timestamp and x-webflow-signature headers, a SHA-256 HMAC, as described in working with webhooks. Return 200 immediately and process asynchronously, since Webflow otherwise retries up to three more times at 10 minute intervals.
3. Look for an existing contact with POST https://api.copper.com/developer_api/v1/people/search, passing an emails array. Email is a unique key for People, so two records can never share one.
4. Create or update the lead with PUT https://api.copper.com/developer_api/v1/leads/upsert, matching on Name, Email, or a custom field definition ID.
5. Log the submission as CRM activity with POST https://api.copper.com/developer_api/v1/activities, which requires parent, type, and details.

Before mapping fields, call GET https://api.copper.com/developer_api/v1/custom_field_definitions once and cache the result, since Webflow sends field names while Copper expects custom field definition IDs. Check each definition's is_filterable flag before you rely on it for matching, because a field you cannot filter on is a field you cannot deduplicate against.

Sync Copper records to the Webflow CMS

This flow pushes CRM changes onto the live site, for example a client roster or a deal-stage tracker rendered from Collection data. Copper webhooks fire on new, update, and delete for leads, people, companies, opportunities, projects, and tasks.

To implement it:

1. Create a subscription with POST https://api.copper.com/developer_api/v1/webhooks, supplying type, event, and an HTTPS target per the subscription reference. Set custom_field_computed_values to true so dropdown fields arrive as option names instead of option_ids.
2. Fetch the full record after each notification. The notification payload carries only ids, type, event, and updated_attributes, never the entity itself.
3. Write to Webflow with POST https://api.webflow.com/v2/collections/{collection_id}/items for a staged draft, or the /items/live variant to publish immediately. The fieldData object needs name and slug, and the token needs the CMS:write scope.

Copper's webhook limits shape how defensively you write this. Notifications fire at most once per event with no retries, Copper accepts only https:// endpoints, an account holds up to 100 active subscriptions, and delivery caps at 600 notifications per minute. With no retries to fall back on, log every notification and reconcile on a schedule rather than trusting the stream. Render the synced records with a Collection List.

What you can build with the Copper Webflow integration

Once the two are connected, lead capture and pipeline updates run off the website itself, and follow-up happens in Copper without anyone exporting a CSV.

• Lead capture with automatic follow-up: A Webflow contact form creates a Copper lead, an email automation sends the first reply, and an opportunity opens at the right pipeline stage.
• Qualification forms that feed the pipeline: An intake page routes demo requests into Copper for scoring, the way Moonstone Marketing rebuilt its contact form on Copper and closed $20,000 with $90,000 in pipeline inside four weeks.
• A CRM-driven page that maintains itself: Copper webhooks update Collection items as records change, which is how Weave Agency used Copper's API to build a client catalog that updates the moment a lead converts.
• Order tracking inside the pipeline: A Webflow New Order trigger opens a Copper opportunity, so a store selling services or products reports revenue where sales already works.

See the Zapier form-to-CRM walkthrough for a step-by-step version of the same pattern. If you would rather have an AI client do the wiring, connect the Webflow MCP server and it can read form submissions and create Collection items straight from a prompt.