IFTTT

A Webflow site collects form submissions and publishes CMS content. It also processes ecommerce orders, but those events stay inside the site. New leads sit in the submissions table until someone exports them. Publishing a blog post doesn't notify your team or post to your social accounts. Keeping outside data sources in sync with your content means manual copying.

IFTTT closes that gap with Applets, automation workflows that react to Webflow events and act in other services. Within minutes, an Applet can add a form submission to Mailchimp or send it to Slack. Data also flows the other way, as IFTTT turns Google Sheets rows and Airtable records into CMS items on your site. RSS items can become CMS items too. IFTTT now runs an MCP server as well, so an AI assistant can build and fire those Applets from a chat prompt.

The integration fits freelance designers who hand off sites to clients and agency ops managers who route inbound leads. Small-business owners running Webflow stores can use it too. Content marketers use it to syndicate CMS posts and pull social content back onto their sites. None of the core workflows require writing code.

How to integrate IFTTT with Webflow

What is IFTTT? IFTTT (If This Then That) is a no-code automation platform that connects apps, services, and devices through Applets. Each Applet pairs a trigger from one service with one or more actions in another. Applets run in this order: trigger, queries, filter code, delay, actions. Applets can chain multiple actions and call arbitrary HTTP endpoints, which is how they read from and write to Webflow.

A form submission becomes a CRM record. A new Google Sheets row becomes a Webflow CMS item, and a new product can kick off a social post. IFTTT ships a native Webflow service for the common pairings, and pre-built Applets cover most of them without any configuration beyond authorizing your account.

The IFTTT and Webflow integration supports four approaches:

• IFTTT MCP: An AI assistant connected to IFTTT's MCP server can find, create, and run Webflow Applets from a chat prompt instead of the Applet builder.
• The IFTTT app: Installing it from the Webflow Marketplace connects your site to IFTTT's native Webflow service for no-code Applets.
• Forms, RSS, and email: Built-in form webhooks, Collection RSS feeds, and form notification emails send site events into IFTTT without custom code.
• The APIs: The Webflow and IFTTT APIs deliver real-time triggers and direct CMS writes, but require developer work such as registering webhooks and formatting JSON payloads.

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

Create and run Applets from an AI assistant

IFTTT's MCP server exposes your IFTTT account to an AI assistant, across the 1,000+ services IFTTT connects to and Webflow among them. You describe the automation you want in plain language, and the assistant finds a matching Applet or creates a new one on your behalf. It can also run an action immediately, which is useful for one-off jobs like publishing a site after a content review.

Setup runs through your AI tool's own connector directory rather than a Webflow install path. You need a paid plan on the AI tool, then you open its connectors page, add IFTTT, authenticate, and enable the connector inside a conversation. IFTTT documents that flow for Claude, Claude Code, ChatGPT, Cursor, CoPilot, OpenClaw, and Perplexity.

The MCP server drives IFTTT rather than Webflow, so the Webflow service still has to be authorized and the same plan requirements still apply. An assistant can assemble the Applet for you, but it can't grant itself Pro features or invent triggers the Webflow service doesn't publish.

Install the IFTTT app

The IFTTT app in the Webflow Marketplace connects your site to IFTTT's native Webflow service, which publishes 12 triggers, queries, and actions in total. The app requests read and write access to CMS data, page data, site data, and publishing. It also requests read access to forms, form submissions, Ecommerce store data, and authorized users. You don't need a paid Webflow plan to install it. On the IFTTT side, the Webflow triggers and actions require a Pro plan.

To set up the integration:

1. Install the IFTTT app from the Webflow Marketplace, or connect the Webflow service inside IFTTT, and authorize your account.
2. In IFTTT, start a new Applet. Under If This, select Webflow, choose a trigger like "Form submitted", fill in the site and form fields, and click Create Trigger.
3. Under Then That, pick the destination service, configure the action, then click Create Action, Continue, and Finish.

Those 12 building blocks break down as follows:

• Triggers: Webflow fires "Form submitted", "New order", "New product added", and "New collection item" events into IFTTT.
• Content actions: "Publish site", "Create collection item", and "Create live collection item" write back to the site you authorized.
• Order actions: "Fulfill order", "Unfulfill order", and "Refund order" cover the store side for Webflow Ecommerce sites.
• Queries: "List products" and "List collections" add lookups to multi-step Applets, and both of them require Pro+.

Webflow triggers are polling triggers, so they check on a schedule rather than firing the instant an event happens. There is also no action for updating an existing CMS item, a gap that needs Make or another tool that can send PATCH requests.

Send Webflow events to IFTTT with forms, RSS, and email

Built-in form webhooks, Collection RSS feeds, and form notification emails can feed IFTTT directly, with no Marketplace app involved. The webhook method uses IFTTT's Webhooks service, which requires an IFTTT Pro plan and fires within seconds of a request. The other two approaches work with IFTTT's RSS Feed and Email services.

Send form submissions with a form webhook

A form's submission data can POST straight to an IFTTT Webhooks trigger URL. The webhook method fires in real time, unlike the polling-based "Form submitted" trigger.

To connect a form to IFTTT:

1. In IFTTT, create an Applet with the Webhooks trigger "Receive a web request" and name an event. Copy the trigger URL, https://maker.ifttt.com/trigger/{event}/with/key/{webhooks_key}. Your key sits on the Webhooks documentation page.
2. In Webflow, select the form, open the Settings panel, and click add next to Send to. Choose Webhook.
3. Paste the IFTTT trigger URL, click Save, and store the Secret key. It's displayed only once.

Adding a Webhook under Send to still lets Webflow store the submission and send email notifications, so you can keep Webflow and Email notifications selected alongside one or more webhooks. Webflow's separate Custom action option is the one that bypasses Webflow storage. The standard trigger URL passes at most three values, so switch to the /json/ URL format to receive the full payload as a single {{JsonPayload}} ingredient.

Trigger Applets from a Webflow RSS feed

Every Collection page can publish an RSS 2.0 feed, and IFTTT's RSS Feed service reads it with two triggers. "New feed item" fires on every new item, while "New feed item matches" fires only when an item contains a keyword. Both are polling triggers and both require Pro.

To connect a feed:

1. Open the Pages panel, hover over the Collection page, and click the settings cog.
2. Scroll to RSS Feed Settings, toggle Enable RSS 2.0 feed on, and configure the channel and item fields.
3. Click Save and publish the site. The feed URL only works after publishing.
4. Copy the feed URL from the same settings section and paste it into an IFTTT RSS trigger.

Republishing an edited Collection item adds it to the feed the same way a brand new item is added, so an RSS Applet can fire again after an update rather than only on first publish. The RSS feed guide covers each configuration field.

Route form notification emails to IFTTT

Form notification emails can trigger IFTTT. IFTTT's Email service fires in real time when a message arrives at trigger@applet.ifttt.com, with no Webhooks key required.

To set this up:

1. Select the form, open the Settings panel, and find Email Notifications under Send to.
2. Add trigger@applet.ifttt.com as a recipient, then click Apply.
3. In IFTTT, build an Applet with the "Send IFTTT any email" trigger, or "Send IFTTT an email tagged" if you add a hashtag to the subject line.

On the free Starter Site plan, notification recipients have to be Workspace members, which rules out adding IFTTT's trigger address until you upgrade. For cases none of these paths cover, client-side JavaScript can POST to a trigger URL from a Code Embed element or from head and body code.

Build with the Webflow and IFTTT APIs

Real-time triggers and CMS operations beyond the native Applet actions run through the Webflow Data API v2 and IFTTT's Webhooks service. You need a Webflow API token from a Data Client App, since the Create Webhook endpoint requires a Data Client App token with the sites:write scope rather than any site token, plus an IFTTT Pro plan and a way to send one registration request.

Components for API-based workflows:

• Data API: The Webflow Data API v2 serves CMS collection items and form submissions at https://api.webflow.com/v2.
• Webflow webhooks: Site webhooks push events such as form_submission and collection_item_created to any URL in real time.
• Inbound IFTTT triggers: The "Receive a web request" triggers accept those events and start an Applet within a few seconds of delivery.
• Outbound IFTTT requests: The "Make a web request" action calls Webflow endpoints directly, which is how an Applet writes CMS items back to your site.

Webflow webhooks send events to IFTTT, while IFTTT requests write data back to Webflow.

Register a Webflow webhook for real-time triggers

Native Webflow triggers in IFTTT poll on a schedule. Registering a site webhook that targets an IFTTT trigger URL removes the wait, because Webhooks triggers run within a few seconds.

To implement this:

1. In IFTTT, create an Applet with the trigger "Receive a web request with a JSON payload" and copy its URL, https://maker.ifttt.com/trigger/{event}/json/with/key/{webhooks_key}.
2. Register the webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks, an Authorization: Bearer header, and the body {"triggerType": "form_submission", "url": "<your IFTTT trigger URL>"}.
3. Publish the site, submit a test form, and map the {{JsonPayload}} ingredient into your action fields.

Webhook requests carry Content-Type: application/json, which the /json/ trigger URL requires. Parsing individual fields out of {{JsonPayload}} takes filter code, a Pro+ feature. The same pattern works for collection_item_created, site_publish, and the other webhook event types.

Create CMS items with the "Make a web request" action

The "Make a web request" action turns any IFTTT trigger into a Webflow CMS write. Point it at the live items endpoint to create and publish in one call, or at the staged endpoint to create drafts.

To implement this:

1. Add the "Make a web request" action and set the URL to https://api.webflow.com/v2/collections/{collection_id}/items/live, or /items for drafts.
2. Set the method to POST, the content type to application/json, and add Authorization: Bearer YOUR_WEBFLOW_TOKEN under Additional Headers.
3. Set the body to a JSON payload whose fieldData includes at least name and slug:

{
  "fieldData": {
    "name": "Post Title",
    "slug": "post-title",
    "post-body": "Content here"
  }
}

Wrap IFTTT ingredients in <<< >>> inside the body to preserve formatting. The action's method dropdown documents GET, POST, and DELETE, so PATCH update endpoints stay out of reach and item edits need a tool that can send PATCH requests. The same action can also call POST https://api.webflow.com/v2/sites/{site_id}/publish, though the native "Publish site" action handles authorization through your connected account instead.

What you can build with the IFTTT Webflow integration

Integrating IFTTT with Webflow lets you route site events into the rest of your stack without exporting data by hand or running your own webhook server. These are the pairings teams reach for first:

• Lead capture with CRM routing: Send new form submissions to Pipedrive, Salesforce, or Google Sheets, or post them to Slack so your team responds before the lead goes cold.
• Email list building: Turn form opt-ins into Mailchimp subscribers or Constant Contact contacts automatically, so a newsletter signup page feeds your audience with no export step.
• Automated content publishing: Create CMS items from Google Sheets rows, Airtable records, or Eventbrite events, so an events calendar or article index stays current from a spreadsheet.
• Store automation: A new order can fire an SMS alert, and a new product can post to X through IFTTT's Pro+ tweet generator query.

For tighter control over delivery timing, pair Webflow webhooks with the IFTTT Webhooks service, and plan around the fact that CMS item edits still need a tool that can send PATCH requests. See how the same pattern moves orders into Airtable.

If an assistant is already creating your Applets, connect the Webflow MCP server next, so the same agent can manage CMS content, pages, and publishing on the Webflow side instead of routing every change through an automation.