MeldAPI

MeldAPI syncs external data sources directly into Webflow CMS collections, mapping fields, filtering records, and pushing updates on a schedule or in real time. It replaces the manual re-entry that bogs teams down when listings live in Guesty, content sits in Airtable, or assets are stored in Dropbox.

The integration fits agencies managing CMS content across client sites, property managers keeping listings current, content teams publishing from Airtable or SeaTable, and developers triggering syncs programmatically.

How to integrate MeldAPI with Webflow

What is MeldAPI? MeldAPI is a no-code data synchronization platform that connects third-party apps to Webflow CMS. It includes connectors for Airtable, Guesty, SeaTable, Mailchimp, Dropbox, OpenAI, and OpenWeather. A BYO (Bring Your Own) connector handles any REST API. All configuration happens in MeldAPI's dashboard, with no Code Embed codes or scripts placed on your site.

Teams use MeldAPI and Webflow together when CMS content originates in another system. A vacation rental company might manage properties in Guesty and need real-time listing updates on their Webflow site. A content team might draft posts in Airtable and publish them to a blog collection. In both cases, MeldAPI syncs the source system and the CMS.

You can use the MeldAPI-Webflow integration in 2 ways:

• The MeldAPI app handles CMS data syncing, field mapping, image compression and format conversion, and form-to-CMS routing without writing code.
• The Webflow and MeldAPI APIs give you programmatic control over sync triggers, connection monitoring, and webhook-driven automation, but require server-side development.

Most implementations start with the MeldAPI app for standard sync workflows. They add API-driven triggers only when external systems need to initiate syncs on demand.

Install the MeldAPI app

The MeldAPI app on the Webflow Marketplace connects your site's CMS to external data sources through a visual dashboard. You configure everything in MeldAPI's portal: field mapping, sync schedules, data filters, and add-ons. Add-ons include image compression, format conversion, and Markdown-to-HTML conversion. The app supports all CMS field types, including single and multi-reference fields and multi-image fields.

To set up the integration:

1. Install the MeldAPI app from the Webflow Marketplace listing and register for a MeldAPI account at us.meldapi.io/portal.
2. In the MeldAPI dashboard, click the + icon and select Create a Meld.
3. Choose your source connection (Airtable, Guesty, Dropbox, or another connector) and select Webflow as the destination.
4. Map source fields to your CMS collection fields. Use the AUTOMAP feature for fields that share the same name. Designate a Linking Field as the unique identifier to prevent duplicate records.
5. Configure optional Data Filters to exclude records that do not meet your criteria. Use Data Setters to assign preset values to specific CMS fields.
6. Under Meld Settings, choose your sync mode. Enable Auto sync updated records for real-time updates, set a Sync Schedule for timed intervals, or use manual sync.
7. Run a Preview Sync to verify your configuration before triggering a live sync.

MeldAPI monitors your source app for changes after setup. It updates corresponding CMS items based on your sync settings. If you enable Auto publish updated Webflow CMS items, synced records go live automatically. Draft and Archived items are excluded from auto-publishing. Items held in those states will not appear on the live site even after a sync updates their field data.

The app includes these capabilities:

• Real-time, scheduled, and conditional syncing between source apps and CMS collections
• Visual field mapping with an AUTOMAP feature that matches fields by name
• Data filters that exclude source records not meeting specified criteria
• Data setters that assign preset values to destination fields during sync
• Flows that chain multiple Melds (sync configurations) into sequential, automated operations
• Outgoing webhook notifications to Slack or Jira Service Desk (plus email) after sync completion
• Guest access for clients to connect their own Webflow sites securely

These capabilities handle most sync workflows without requiring any code or external tools.

Optional paid add-ons extend what happens to data during sync:

• Image Optimizer converts images to AVIF or WebP format with configurable dimensions and compression before uploading to Webflow CMS
• Markdown to HTML/Text converts Markdown content into HTML for Webflow CMS Rich Text fields
• Slugify generates custom URL slugs from chosen text fields instead of relying on auto-generated slugs
• PDF Content Extractor converts PDF content to text and images for editing, search indexing, and accessibility

The Unlinked Destination Records setting in Meld configuration determines what happens to CMS items when their corresponding source records are deleted. The options are keep, archive, or delete. Review this setting carefully before running production syncs. Misconfiguring it can cause unintended mass deletion of CMS content.

Build with the Webflow and MeldAPI APIs

External systems sometimes need to trigger syncs on demand. For on-demand syncs and programmatic sync health monitoring, both MeldAPI and Webflow expose REST APIs. This approach requires server-side development and a backend function host such as Vercel Functions, Netlify Functions, or Cloudflare Workers. API credentials must never be placed in client-side code or Custom code in head and body tags. Any key in a browser-executed script is visible to anyone inspecting the page source.

The APIs handle different parts of the integration:

• The MeldAPI API (base URL: https://api.meldapi.io/api/public/v1/) handles sync triggering, connection health checks, and processing status monitoring
• The Webflow Data API handles CMS collections, form submissions, and site publishing
• Webflow webhooks trigger real-time events when CMS items are created, updated, deleted, or published

All MeldAPI API requests require a Bearer token in the Authorization header. Generate tokens under your Profile in the MeldAPI portal. Webflow API v2 requires its own Bearer token, either a site token or an OAuth token depending on your use case.

Trigger syncs from external systems

A record update in a CRM or other external app can trigger a sync. Your backend calls MeldAPI's trigger endpoint to push that change into a CMS collection. This is the primary developer use case for the API.

To trigger a sync from an external system:

1. Create a Meld in the MeldAPI dashboard with your source system and Webflow as the destination. Note the Meld ID from the dashboard URL.
2. Validate your API token by calling GET https://api.meldapi.io/api/public/v1/auth/check with the Authorization: Bearer <API_TOKEN> header.
3. From your backend, call GET https://api.meldapi.io/api/public/v1/meldsyncs/add/:meld_id to trigger the configured sync.
4. Monitor progress by polling GET https://api.meldapi.io/api/public/v1/meldsyncs/processing until no active syncs remain.

Run a Preview Sync from the MeldAPI dashboard before triggering your first live sync via the API. The preview emulates a sync without altering destination records.

Monitor connection health

Connections between MeldAPI and external apps can enter EXPIRED, RECONNECT_REQUIRED, or DEGRADED states that cause silent sync failures. Checking connection status before triggering syncs prevents data from going stale without any visible error.

To check a connection's health:

1. Locate the Connection ID in the MeldAPI dashboard.
2. Call GET https://api.meldapi.io/api/public/v1/connections/:id with your Bearer token.
3. Parse the connection state from the response. Only trigger syncs when the connection is healthy.

If a connection is in an EXPIRED or RECONNECT_REQUIRED state, re-authenticate through the MeldAPI dashboard before attempting further syncs.

React to Webflow CMS changes with webhooks

Some workflows run in reverse: a Webflow CMS change triggers a sync back to another system. Register Webflow webhooks to notify your backend when CMS items change.

To set up a Webflow-to-MeldAPI webhook flow:

1. Register a webhook via POST /v2/sites/{site_id}/webhooks with a trigger type such as collection_item_created, collection_item_changed, or collection_item_deleted. This endpoint requires an OAuth token.
2. On your receiving server, validate the x-webflow-signature HMAC-SHA256 header on every incoming payload. Reject payloads with timestamps older than 5 minutes.
3. Extract payload.collectionId and payload.id from the Webflow event to identify the changed item.
4. Call MeldAPI's trigger endpoint (GET /api/public/v1/meldsyncs/add/:meld_id) to sync the change to the destination system.

Webflow retries failed webhook deliveries on non-200 responses. After all retries fail, the webhook is deactivated and the registered email receives a notification.

What can you build with the MeldAPI Webflow integration?

Integrating MeldAPI with Webflow lets you keep CMS content current across multiple data sources without manual re-entry or custom middleware.

• Connect Guesty to a CMS collection so that property details, pricing, and availability update on your Webflow site. Changes sync whenever they happen in the property management system. A vacation rental site can display dozens of listings that stay accurate without anyone touching the CMS directly.
• Sync blog posts, team profiles, or product catalog data from Airtable into CMS collections. Content teams draft and edit in Airtable while the Webflow site publishes updates automatically. The Slugify add-on generates custom URL slugs. The Markdown to HTML add-on converts formatted content into Rich Text fields.
• Route Webflow form submissions into CMS collections. This approach works for user-submitted directories, testimonial pages, or community content feeds. MeldAPI's Data Filters determine which submissions qualify. Flows can route the same submission to both a CMS collection and a Mailchimp list simultaneously.
• Connect OpenAI as a source to generate or enrich text. Sync that content into CMS Rich Text fields using the Markdown to HTML add-on. A product catalog page could auto-generate descriptions for new items. The Image Optimizer add-on converts any associated images to WebP or AVIF before they reach the CMS.

If you need more control over sync timing or webhook-driven updates, the API integration path covers those cases with full flexibility.