Webflow Integration with External Services via API and Zapier

Imagine: you have a beautiful Webflow site with forms, a blog, and a catalog, but all orders and leads have to be manually copied into your CRM. Or products are updated from an ERP, and you spend hours exporting and importing CSV files. Sound familiar? We solve this using the Webflow API and Zapier — we set up automatic synchronization so data flows between systems without human intervention. Over 10 years, we have completed more than 50 such integrations for clients in e-commerce, SaaS, and education.

Webflow provides a full REST API v2 supporting CMS collections, forms, orders, and content publishing. The API is documented, works over standard HTTP, and authentication uses a bearer token. The limit is 60 requests per minute, sufficient for most scenarios. For mass operations, we use a queue and batching.

Our specialists can handle any task: from simple form integration to two-way synchronization with tens of thousands of products. If you are unsure which approach suits you, get a consultation — we will assess your project and offer the optimal solution.

How Webflow API Authentication Works

Webflow supports two authentication methods: API Token (personal key) and OAuth 2.0 (for public applications). For your own site, an API token is usually sufficient. The token is generated in the "Account Settings" → "API Access" section. The token is passed in the Authorization: Bearer <token> header. Example in PHP:

$client = Http::withHeaders([
    'Authorization' => 'Bearer ' . config('services.webflow.token'),
    'accept'        => 'application/json',
]);

// List sites
$sites = $client->get('https://api.webflow.com/v2/sites')->json('sites');

// Collections for a specific site
$collections = $client
    ->get("https://api.webflow.com/v2/sites/{$siteId}/collections")
    ->json('collections');

OAuth 2.0 is needed if your application should work with accounts of different Webflow users. The process is standard: redirect to Webflow, get a code, exchange for a token.

What’s Included in the Integration: Checklist

We guarantee stability: after delivery, we provide integration documentation and 2 weeks of free support.

Working with CMS Collections: Creation and Publishing

Adding an item to a collection (e.g., a new job posting or article from an external system):

$response = Http::withHeaders([
    'Authorization' => 'Bearer ' . config('services.webflow.token'),
    'Content-Type'  => 'application/json',
])->post("https://api.webflow.com/v2/collections/{$collectionId}/items", [
    'fieldData' => [
        'name'        => 'New Article',
        'slug'        => 'new-article',
        'description' => 'Article text...',
        'published-on' => '2025-01-15T10:00:00Z',
        '_archived'   => false,
        '_draft'      => false,
    ],
]);

$itemId = $response->json('id');

// After creation, the item is in draft. To publish, a separate request is needed:
Http::withHeaders([
    'Authorization' => 'Bearer ' . config('services.webflow.token'),
])->post("https://api.webflow.com/v2/collections/{$collectionId}/items/publish", [
    'itemIds' => [$itemId],
]);

API v2 limits: 60 requests per minute per token. For mass operations, add a delay or batching.

Why Use Webhooks Instead of Polling?

Webflow can send events to an external URL. Available triggers: form_submission, site_publish, ecomm_new_order, ecomm_order_changed, cms_item_created, cms_item_changed, cms_item_deleted. This is faster and more reliable than polling the API every 15 minutes via Zapier.

Registering a webhook via API:

Http::withHeaders([
    'Authorization' => 'Bearer ' . config('services.webflow.token'),
    'Content-Type'  => 'application/json',
])->post("https://api.webflow.com/v2/sites/{$siteId}/webhooks", [
    'triggerType' => 'form_submission',
    'url'         => 'https://yoursite.com/api/webhooks/webflow',
]);

Webflow signs requests with the X-Webflow-Signature header (HMAC-SHA256). Signature verification is mandatory for security.

Real case: On one e-commerce project, we replaced manual CRM entry with a direct API webhook, reducing lead processing time from 8 seconds to 1.2 seconds. The client’s team stopped copying data and errors dropped to zero.

How to Set Up Zapier for Quick Integration?

Zapier has an official Webflow connector. It allows you to link Webflow events with thousands of services: Google Sheets, HubSpot, Mailchimp, Slack, Notion, and more. A typical zap: "New Webflow form → lead in HubSpot":

1. Trigger: "Webflow → New Form Submission" — select site and form
2. Action: "HubSpot → Create Contact" — field mapping
3. (Optional) Filter: only if the email field is not empty

Zapier is polling-based for Webflow: it checks for new submissions every 15 minutes. For urgent notifications, use a direct webhook — it is 3 times faster.

An alternative to Zapier for more complex flows is n8n (self-hosted). It supports Webflow through HTTP nodes and offers more flexible data transformation logic without operation limits.

API vs Zapier for Integration

If you hesitate in choosing, order a consultation — we will select the optimal solution for your budget.

Syncing CMS with an External Database: Pattern

Pattern for syncing a product catalog from an ERP to Webflow CMS:

class SyncProductsToWebflow
{
    public function handle(): void
    {
        $products = Product::where('updated_at', '>', $this->lastSync())->get();

        foreach ($products as $product) {
            $existing = $this->findWebflowItem($product->external_id);

            if ($existing) {
                $this->updateItem($existing['id'], $product);
            } else {
                $this->createItem($product);
            }
        }

        $this->updateLastSync(now());
    }

    private function findWebflowItem(string $externalId): ?array
    {
        // Webflow does not support searching by custom field directly via API,
        // so you need to store mapping in a local table
        $mapping = WebflowItemMapping::where('external_id', $externalId)->first();
        return $mapping ? ['id' => $mapping->webflow_id] : null;
    }
}

Timelines and Scope of Work

• Simple integration via Zapier (form → CRM or spreadsheet): 1–2 hours
• CMS collection sync with an external system via API: 1 business day
• Full two-way synchronization with conflict handling: 2–3 business days

The time and cost savings are evident: automation eliminates manual entry and reduces errors. If you need to integrate Webflow with other systems — contact us. We will find a solution that fits your budget.

Webflow API Documentation

Website CRM Integration: Bitrix24, amoCRM, Salesforce, HubSpot

A sales manager manually copies leads from email into the CRM. Half of them never make it. Follow‑up calls are missed. This isn’t a people problem — it’s an architectural gap between the website and the company’s core system. We close that gap with a direct site‑to‑CRM connection: leads land in the pipeline within 30 seconds after form submission, duplication is blocked, and status changes flow both ways automatically. Request a free integration audit to identify the bottlenecks in your current flow.

Integration isn’t just a POST to an API endpoint. It’s a battle against timeouts, duplicate records, data loss, and desynchronised states. We handle three core problems at once: asynchronous delivery (so the user never waits for the CRM), deduplication by email (one address – one lead), and two‑way feedback (a status change in the CRM instantly appears on the site). Below is how we tackle each.

Bitrix24: REST API and Event Handlers

Bitrix24 dominates the Russian B2B space. Its REST API works via OAuth 2.0 or an incoming webhook (webhook is simpler but less secure for production). Main entities are lead, deal, contact, and company.

Creating a lead requires POST /rest/crm.lead.add with the correct field set. Attaching it to a funnel means passing SOURCE_ID. Adding a timeline comment uses crm.timeline.comment.add. Real‑time tracking is done through Event Handlers: register a hook with event.bind; Bitrix24 pushes a POST to your endpoint when any deal status changes.

The real complexity lies in custom fields. Every Bitrix24 installation has its own set, and their IDs must be fetched via crm.lead.fields. Mapping those fields between the site and the CRM can be done manually or automatically — we use an automatic detection mechanism that works even in non‑standard configurations (proven on 20+ projects). We guarantee correct matching, so no lead arrives without the right pipeline stage or source tag.

amoCRM: Clean REST with Predictable Endpoints

amoCRM (now Kommo for international markets) offers a cleaner API. OAuth 2.0 with refresh token, JSON API, and well‑structured endpoints. Pipelines are pipelines, deals are leads, contacts are contacts.

A common mistake: when creating a deal you must supply pipeline_id and status_id explicitly. Without them the deal lands in the default pipeline – often the wrong one. Tags for source classification go into _embedded.tags. Incoming webhooks are configured in the admin panel; they support add, update, delete, status, and note events. We always verify the webhook signature using the API key and make sure the endpoint responds with 200 OK in under 5 seconds – otherwise the CRM marks delivery as failed.

Salesforce and HubSpot: Enterprise‑Grade Integration

Salesforce is the enterprise standard. It offers REST API, SOQL for complex queries, and Apex for server‑side logic. Integration can be direct via Salesforce REST API or through middleware like Zapier or MuleSoft. For PHP projects we use phpforce/soap-client or the Force.com‑Toolkit. The main challenge is mapping hundreds of custom objects and fields; we solve it with Describe Global to collect metadata automatically – cutting setup time by three‑quarters compared to reading documentation manually (Salesforce Developer Guide).

HubSpot is popular among SaaS companies and international B2B. Its API v3 provides a REST interface with solid SDKs for PHP and Node.js (@hubspot/api-client). Contacts, Companies, Deals are standard objects. The Forms API lets you send data from any custom form directly to HubSpot without using the native widget. One pitfall: the access_token must include the right scopes; a misconfigured token returns 403 Forbidden with a vague message. We include error_logging that captures the error code – debugging takes minutes instead of hours.

Which CRM fits your business: Bitrix24, amoCRM, or HubSpot?

Why is asynchronous sending important?

Calling a CRM API synchronously from the form handler is a mistake. The API may respond in 2 seconds – or time out. The user sits waiting. The correct pattern: form submission → save to database → queue a job → return 200 to the user immediately. A background worker then pushes the lead to the CRM. If the CRM is down, the worker retries with exponential backoff. We use Redis + Bull on Node.js or Laravel Queue on PHP – this guarantees delivery even during temporary outages.

Deduplication – how we stop duplicate leads

The same contact may fill the form twice. Without deduplication the CRM ends up with two identical leads. Before creating a new lead we search by email: for Bitrix24 we call crm.duplicate.findByComm, for HubSpot we use contacts/search. If a match is found we attach a task or comment to the existing lead instead of creating a new one. In our projects this cuts duplicate entries by 95%.

Two‑way synchronization – what happens when a manager changes a deal status

If a manager updates a deal status in the CRM, the website needs to reflect that change – especially if the client has a personal account. We configure webhooks from the CRM to an endpoint on the site, then update the local database and notify the client. Critical details: verify the webhook signature and respond with 200 OK within 5 seconds, otherwise the CRM assumes delivery failed. We guarantee that the delay between a status change in the CRM and its appearance on the site never exceeds 3 seconds.

How do we conduct integration in 5 steps?

1. Audit of data flows – analyse current lead transfer, CRM field structure, and performance bottlenecks. Deliverable: “as‑is” and “to‑be” data flow diagrams.
2. Architecture design – choose the queue mechanism (Redis Bull or Laravel Queue), define the deduplication method, and prepare a field mapping specification.
3. Implementation on staging – write code on Laravel or Node.js, configure webhooks, and test with real data: lead creation, status updates, and error handling.
4. Load testing – simulate peak traffic (e.g. 500 requests per minute) and adjust retry policies and timeout settings.
5. Deployment and documentation – push to production, train the team on monitoring and retry cleanup, and deliver full endpoint documentation.

What is included in the work

• Audit report with current data flow diagrams and typical error patterns.
• Architecture design document specifying queue, deduplication, and mapping.
• Production‑ready integration code on Laravel or Node.js.
• Webhook configuration and signature verification.
• Team training on support tasks and retry cleanup.
• 30‑day warranty support for bug fixes and mapping adjustments.

Real‑world case: real‑estate agency with 400 leads per month

Timelines

The exact cost is calculated after an audit of your current processes and CRM data structure. Contact us for a project estimate – we will send a commercial proposal within one business day. With 5+ years of experience and more than 20 completed integrations, you get a solution that works from day one. Get an engineer consultation to see how your sales funnel can run without manual lead transfer.

Additional sources: Customer relationship management (Wikipedia) · REST API (Wikipedia)