albato

A Webflow site captures leads and publishes content. Webflow Ecommerce also processes orders, but that data stays inside the platform unless something moves it. Getting a form submission into a CRM or an order into a fulfillment system means manual exports or custom code. The same is true when a spreadsheet row needs to become a Webflow CMS item. Integration platforms like Albato close that gap.

Connecting Albato with Webflow turns site events into automated workflows. A form submission can create a HubSpot contact, while Google Sheets rows can become live CMS items. New ecommerce orders can also update fulfillment status in another system. Albato's visual builder connects Webflow to more than 1,000 apps without connector code.

Marketing ops teams routing leads get the most from this integration. Content teams publishing CMS items from external sources and ecommerce operators automating order handling do too. Agencies managing multiple client sites use it to replace one-off scripts with maintained automations. Developers also get a Custom API request action for scenarios the standard triggers and actions don't cover.

How to integrate Albato with Webflow

What is Albato? Albato is a no-code integration platform (iPaaS) that connects more than 1,000 apps through a visual automation builder. It supports one-to-one automations and multi-step workflows with routers, filters, JSON parsing, and other data transformers. It also offers Solutions, ready-made templates for launching common integration scenarios quickly.

Teams pair Albato with Webflow when site data needs to flow into other systems continuously. Webflow CMS content pipelines and lead routing from forms are common uses. Ecommerce order automation can use the same connector. Albato's native Webflow connector covers all three without code.

The Albato-Webflow integration supports these connection paths:

• The Albato app handles trigger-and-action automation between Webflow and 1,000+ apps without writing code.
• Webflow form webhooks send submission data straight to a webhook URL generated in Albato.
• Webflow Data API and Albato APIs give you full control over custom requests and event handling, but require server-side development for full builds.

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

Install the Albato app

The Albato app in the Webflow Marketplace carries the "Approved by Webflow" badge and connects your site to Albato's automation builder through OAuth. On install, Albato requests write access to CMS data, ecommerce store data, site data and publishing, site configuration, and user accounts. It also requests read access to forms and submissions. This method suits anyone who wants automations running without touching code. A free Albato plan is available to test the connection.

To set up the integration:

1. Log in to Albato, open the Apps section, and authorize Webflow through the connection flow.
2. Pick a second app to pair with Webflow from Albato's 1,000+ integrations.
3. Click Create Scenario, choose a Webflow trigger, and add actions.
4. Run a test, then activate the scenario.

Once connected, Albato exposes 11 Webflow triggers and 10 actions:

• CMS triggers for Collection Item Created, Updated, Unpublished, and Deleted, plus Site Publish
• CMS actions for Create Collection Item, Create Live Collection Item, Update Live Collection Item, Publish Collection Item, and Delete Single Live Collection Item
• A Form submission trigger that routes field data to CRMs, email tools, or spreadsheets
• Ecommerce triggers for New eComm Order, Updated eComm Order, and Updated eComm Inventory, with Fulfill Order, Refund Order, Unfulfill Order, and Update Order actions
• Membership triggers for New User Added and Account Updated
• A Custom API request action for anything the standard actions don't cover

Site Publish and Collection Item Created fire in real time through webhooks, while the other triggers poll the API at intervals set by your Albato plan. For instant form routing without the app's polling delay, the webhook method below is the direct path.

Send Webflow form submissions to an Albato webhook

Form submissions can bypass polling entirely by posting straight to a webhook URL that Albato generates. Albato documents this pattern in its webhook automation guide, which walks through routing Webflow form data to Mailchimp. The setup has two halves, one in each platform, and neither requires code.

Create the webhook trigger in Albato

Albato's "Webhooks by Albato" trigger generates a unique URL that starts a workflow the moment a request arrives.

To create the trigger:

1. Create an automation with Webhooks by Albato as the trigger.
2. Copy the webhook URL Albato provides.
3. Configure the data fields you expect, such as a subscriber email.
4. Select the downstream action, such as Add Subscriber for Mailchimp, then map fields and test.

Keep the URL handy, because the Webflow side of the setup needs it next.

Register the webhook in Webflow

Form submission data posts to any registered webhook URL from site settings.

To register the webhook:

1. Open Site settings > Apps & integrations and find the Webhooks section.
2. Click Add webhook.
3. Set the trigger type to Form submission, then choose your API version (v1 or v2).
4. Paste the Albato webhook URL into the Webhook URL field and save.

You can also route an individual form by adding Webhook to the Send to list in the form's Settings panel, as covered in the Forms overview. The generated Secret key appears only once, so store it securely.

Build with the Webflow and Albato APIs

When the built-in triggers and actions don't cover a scenario, work with the APIs directly. This path suits developers who need custom event handling through endpoints Albato doesn't surface, or who need workflow execution from code. Full builds require server-side development, though Albato's Custom API request action runs inside a no-code scenario.

Three APIs are relevant:

• Webflow's Data API handles CMS collections, forms, ecommerce orders and products, and site publishing at the base URL https://api.webflow.com/v2
• Webflow webhooks trigger real-time events between systems
• Albato's Universal API executes trigger-actions synchronously or asynchronously from your own backend

Developers commonly handle custom requests through Albato or register Webflow webhooks directly.

Send a Custom API request from Albato

The Custom API request action calls any Webflow Data API v2 endpoint from inside an automation through your connected Webflow account. It covers operations the standard actions skip, such as bulk item creation.

To implement this:

1. Add the Custom API request action to a scenario after any trigger.
2. Point it at the endpoint you need, such as PATCH https://api.webflow.com/v2/sites/{site_id}/orders/{order_id} to update an order, or POST https://api.webflow.com/v2/collections/{collection_id}/items/bulk to create items in bulk.
3. Map trigger fields into the request body and run a test.

The CMS publishing guide documents a publishing behavior to account for: items created with POST /v2/collections/{collection_id}/items are staged with isDraft: true, not live. Either call POST /v2/collections/{collection_id}/items/publish afterward or use Albato's Create Live Collection Item action, which publishes in one step.

Register Webflow webhooks directly

The Data API supports webhook triggerType values Albato's trigger list doesn't expose, including page_created, page_deleted, page_metadata_updated, collection_item_published, and comment_created. Registering these yourself and pointing them at an Albato incoming webhook extends what your automations can react to.

To implement this:

1. Create the webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks and set a triggerType such as collection_item_published.
2. Set the destination URL to an incoming webhook trigger in Albato, then use Albato's Webhook catcher to capture a test payload and generate trigger fields from its parameters.
3. Map payload fields such as fieldData, collectionId, and lastPublished into your automation steps.

Each site supports up to 75 webhooks per triggerType, the filter parameter works only with form_submission, and failed deliveries retry up to 3 times at 10-minute intervals, per Webflow's webhooks documentation.

What you can build with the Albato Webflow integration

Integrating Albato with Webflow lets you move site data between your site and 1,000+ apps without writing or maintaining connector code. The same integration can move form submissions, CMS content, order data, and related records between systems.

• Lead capture with CRM routing: A contact page whose submissions create HubSpot contacts and add Mailchimp subscribers, with Google Sheets receiving each lead as a row.
• Spreadsheet-driven CMS publishing: A blog or resource directory where new rows in Google Sheets, Notion, or Airtable become live CMS items through the Create Live Collection Item action, with no manual entry.
• Ecommerce order automation: A store where a New eComm Order trigger fires a WhatsApp Business notification to the team and a Fulfill Order action updates status once an external system ships the item.
• Ad conversion tracking: A landing page whose form submissions fire conversion events to the Facebook Conversions API and Google Ads, so paid campaigns target real leads instead of pageviews.

For more control over event types, bulk operations, or custom endpoints beyond Albato's standard triggers and actions, the API integration path covers those cases. To see a comparable automation built end to end, route form submissions to HubSpot.