BuildShip

Sites built in Webflow handle site design while Webflow manages content and hosting without server-side code. That also leaves no built-in place for scheduled backend jobs or AI model calls, including workflows that push form data into an external database. A form submission can trigger an email notification, but enriching that lead or routing it to a CRM needs a backend.

BuildShip fills that gap with a visual backend that connects natively to Webflow. Its Webflow Trigger subscribes to site events over OAuth. Those events span site publishes, page events, Webflow CMS collection changes, and e-commerce orders. (Webflow retired its user-account webhook events when it sunset User Accounts on January 29, 2026.) Prebuilt action nodes can write results back into CMS collections and products, and read form schemas or submissions for downstream processing.

The integration fits no-code builders, including founders and agencies shipping client work on Webflow. EPYC, a no-code development studio, paired a Webflow frontend with BuildShip. The team built LinkedIn authentication and data routing for Accel's Atoms cohort application. The same pattern suits lead enrichment and AI-generated CMS entries.

How to integrate BuildShip with Webflow

What is BuildShip? BuildShip is a cloud-hosted visual backend builder from Rowy Inc. You build workflows on a canvas with AI-generated logic, then ship each workflow as an API endpoint or scheduled job, with webhook receiver support. Every node's code is editable JavaScript or TypeScript, and workflows support over one million NPM packages.

Teams pair the two tools when a site needs behavior Webflow doesn't run natively. A contact form can enrich leads through Apollo before they reach HubSpot. A Webflow CMS collection can fill its own fields with AI-generated content the same way. Webflow fires an event, BuildShip runs the logic, and the result lands back in Webflow or a third-party tool.

The BuildShip-Webflow integration supports these approaches:

• The BuildShip app handles event triggers and prebuilt Webflow action nodes without writing code.
• Code Embed elements and form settings let you place BuildShip widgets and workflow endpoints directly on your pages.
• The Webflow Data API and BuildShip APIs give you full control over CMS writes and webhook work, including order-related API calls, for cases the prebuilt nodes don't cover, but require server-side development.

Most implementations combine two or more of these methods depending on the complexity of the setup.

Install the BuildShip app

The BuildShip app on the Webflow Marketplace is the fastest path and needs no code. Its Webflow Trigger subscribes to site events over OAuth and registers the webhook for you. Prebuilt action nodes then write results back to the CMS or store and can read form data. You need a BuildShip account and a Webflow site you can authorize.

To set up the integration:

1. In BuildShip, create a workflow, add the Webflow Trigger, and click Authenticate to log into Webflow and select your sites.
2. In Webflow, go to Site settings > General, copy the Site ID from the bottom of the page, and paste it into the trigger..
3. Select a trigger event, such as form_submission, and optionally filter by form name on multi-form sites.
4. Click Connect, then publish the workflow. Publishing registers a form submission webhook in Webflow.
5. Publish your Webflow site, then confirm the webhook under Site settings > Apps & integrations.

Once connected, the app covers these triggers and actions:

• Trigger events for form submissions, site publishing, page events, e-commerce orders, and CMS collections
• CMS nodes including Create Item, Create Live Item, Create Collection, Create Collection Field, and Get Collection Details
• E-commerce nodes for Create Product & SKU and List Products and SKUs
• Form nodes for Get Form Schema and Get Form Submission

After connecting, click Get Data to pull a real sample payload from the Webflow API before mapping downstream nodes.

Add BuildShip endpoints with Code Embed and form settings

BuildShip workflows also connect to Webflow pages without the trigger. A shipped workflow produces either a code snippet you embed or an endpoint URL you point a form at. Both paths keep the logic in BuildShip while the site stays fully visual. Code Embed requires a Core, Growth, Agency, or Freelancer Workspace, or an active Site plan.

Embed the AI chatbot widget

BuildShip ships its AI Assistant as a ready-made chat widget. Per BuildShip's AI assistant tutorial, you copy the snippet BuildShip provides and add it to a page with an embed component.

To embed the widget:

1. In BuildShip, build the assistant workflow and copy the widget code snippet.
2. In Webflow, drag a Code Embed element onto the page and paste the snippet.
3. To load the widget site-wide, paste the snippet under Site settings > Custom code instead, following the steps for custom code in head and body tags.

Each embed holds up to 50,000 characters; reference an external script or split the code if the snippet runs longer.

Route form submissions to a workflow endpoint

BuildShip's REST API Call Trigger generates an HTTP endpoint for any workflow. You can point a Webflow form at that endpoint through the form's custom action setting.

To route a form:

1. In BuildShip, go to the Connect tab, select Rest API Call, and define an endpoint path. POST is the default method.
2. Click Connect to generate the unique endpoint URL.
3. In Webflow, select the form, open the Settings panel, choose Custom action, and paste the URL with the POST method.

A custom action URL bypasses Webflow's native form processing, so submissions stop appearing in Site settings > Forms and email notifications stop. Use the Webflow Trigger method instead when you want to keep both.

Build with the Webflow and BuildShip APIs

Direct API work covers what the prebuilt nodes don't. BuildShip lists Create Item and Create Live Item nodes for the CMS, but no Update Item or Delete Item node. Those operations go through Webflow's Data API v2 at https://api.webflow.com/v2. This path suits developers who need exact control over payloads and scopes, with their own error handling.

• BuildShip's REST API Call Trigger turns any workflow into an HTTP endpoint accepting JSON request bodies; it also handles form-encoded and plain-text requests.
• Webflow's Data API v2 handles CMS collection items and form submissions with bearer-token authentication.
• Webflow webhooks push real-time events like collection_item_created and ecomm_new_order to any endpoint.

Creating webhooks via the API requires a Data Client App token with the sites:write scope; site tokens cover other Data API operations. See the create webhook reference.

Update and delete CMS items with the HTTP node

BuildShip's Starter HTTP node sends requests to any API with a UI-based configuration, which fills the gap left by the missing update and delete nodes.

To update a CMS item from a workflow:

1. Add the Starter HTTP node from the Core Nodes section.
2. Send PATCH https://api.webflow.com/v2/collections/{collection_id}/items/{item_id} with an Authorization: Bearer header and a token holding the CMS:write scope, per the update item reference.
3. Publish the staged change with POST https://api.webflow.com/v2/collections/{collection_id}/items/publish, per the publish items reference.

Deleting works the same way with DELETE on the item endpoint.

Call a BuildShip endpoint from page code

Client-side JavaScript on a Webflow page can call any shipped BuildShip workflow. Each ship produces a project-specific URL in the format https://008vd0.buildship.run/story-gen.

To call a workflow from a page:

1. Ship the workflow in BuildShip and copy its endpoint URL.
2. Add a Code Embed element with a fetch call:

<script>
fetch('https://YOUR-PROJECT.buildship.run/your-endpoint', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Authorization': 'Bearer YOUR_API_KEY'
  },
  body: JSON.stringify({ email: 'visitor@example.com' })
});
</script>

3. In the workflow, add an Authorization input mapped from request headers and return HTTP 401 for invalid tokens, following BuildShip's secure API tutorial.

CORS behavior for browser calls to BuildShip endpoints is not covered in the official BuildShip or Webflow docs, so test browser requests before relying on them in production.

What you can build with the BuildShip Webflow integration

Integrating BuildShip with Webflow lets you run backend logic behind your site without provisioning servers.

• Lead capture with enrichment and CRM routing: A Webflow contact form triggers a workflow that enriches submissions with Apollo's Enrich People Data node. The workflow then sends the lead to Salesforce or HubSpot and replies to the submitter.
• AI chatbot on a marketing site: An embedded chat widget answers visitor questions using OpenAI and Claude models or Azure-backed deployments. BuildShip's AI assistant guide backs the widget with data pulled from Google Sheets.
• Self-filling CMS content: A workflow listens for new CMS entries, generates the remaining field values with AI, and writes them back to the entry through the Data API, since BuildShip lacks a prebuilt Update Item node.
• E-commerce social automation: The Webflow Item Created Instagram Post workflow triggers automatic posts to Instagram, LinkedIn, X, or Facebook when someone creates a new product in Webflow, with AI-generated images from Flux.

If you need more control over CMS updates and order fulfillment, including unsupported Webflow actions, the API integration path covers those cases with full flexibility. See the Webflow CMS API guide to get started with those write operations.