AWeber

Native Webflow forms collect submissions, store them in your site's form submissions view, and send notification emails to your team. Welcome messages, tags, and drip sequences depend on AWeber. Webflow has no built-in path from a form to an AWeber list, so a signup on your site sits in a submissions table until someone exports it.

Connecting the two gives every Webflow signup a destination. An AWeber form embedded on a Webflow page submits straight to an AWeber list and can start a welcome workflow. Native Webflow form submissions and Ecommerce orders can also feed AWeber, where tags route subscribers into automated follow-up.

Client leads can route into separate AWeber lists without manual imports, and gated downloads, event registrations, and Webflow Ecommerce checkouts can each start their own follow-up sequence.

How to integrate AWeber with Webflow

What is AWeber? AWeber is an email marketing and automation platform for small businesses. It includes a drag-and-drop email builder, visual automation workflows, sign-up forms, landing pages, and subscriber tagging. Its REST API uses OAuth 2.0 and covers subscribers, lists, custom fields, and broadcasts.

Webflow is the front door while AWeber runs the email program behind it. A blog with an end-of-post signup, a course page with a free lesson, a store with a post-purchase sequence, and an event registration page all fit this pattern. AWeber's own Webflow tutorial, linked above, covers end-of-post forms, exit-intent pop-ups, inline forms, and sidebar forms on Webflow pages.

The AWeber-Webflow integration supports four approaches:

• AWeber sign-up form embeds place AWeber's forms on Webflow pages through site-wide head code or a Code Embed element, without writing code.
• Automation platforms relay native Webflow form submissions and Ecommerce orders to AWeber lists.
• A native form custom action posts Webflow form data straight to AWeber without an automation platform.
• The Webflow Data API and AWeber API give you full control over subscriber sync, CMS records, and broadcasts, but require server-side development.

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

Add AWeber sign-up forms with head code, Code Embed, or a hosted link

Submissions from an AWeber form bypass Webflow's form settings and go directly to AWeber. The head code and Code Embed paths need custom code access. That requires a Core, Growth, Agency, or Freelancer Workspace, or an active Site plan. The hosted-link path needs neither. Choose the JavaScript snippet for pop-ups and auto-updating forms, and raw HTML when you want to style the markup yourself.

• Pop-up, slide-in, inline, sticky bar, full page, and split layout form types from the AI Signup Form builder
• Tags applied at the form level, so each page can start its own workflow
• Submissions that land in AWeber without counting against Webflow's own form submission limits
• A hosted landing page URL for sites with no custom code access at all

Which path suits you comes down to whether you have custom code access and how much control you want over the markup.

Install the AWeber JavaScript snippet in site-wide head code

One paste in Site settings activates every AI Signup Form you build for that domain. The snippet is AWeber's recommended publish option and the method its Webflow guide documents. Editing the form in AWeber updates the live site without touching Webflow again.

To install the snippet:

1. In AWeber, open the Sign Up Forms tab, select your form, and go to the Publish step.
2. Choose I Will Install My Form and copy the JavaScript Snippet.
3. In Webflow, open Site settings > Custom code and paste the snippet into the Head code section.
4. Click Save changes, then publish the site.
5. Load your domain with ?hello_aweber= appended to the URL. The AWeber Status panel opens if the install worked.

The snippet shows only a placeholder on the canvas; the form renders on preview and on the published site. AWeber documents the snippet for site-wide head code.

Paste the raw HTML version into a Code Embed element

Inline forms are the only AWeber forms available as raw HTML, which gives you the full markup to edit and style with Webflow classes or custom CSS. Popover, lightbox, and pop-up forms ship as JavaScript only. Changes in AWeber's form editor do not flow into pasted HTML, so you re-copy after edits. Uncheck Include beautiful form styles before copying to strip AWeber's CSS.

To embed the HTML:

1. On the Publish step, choose I Will Install My Form > Raw HTML Version and copy the form code.
2. In Webflow, open the Add panel and drag a Code Embed element onto the page.
3. Paste the code, then click Save and close.
4. Publish the site and submit a test entry.

Each Code Embed element holds up to 50,000 characters. AWeber's custom HTML forms post to https://www.aweber.com/scripts/addlead.pl and carry hidden fields you can edit. AWeber marks listname, redirect, and meta_required as required; meta_tags applies comma-separated tags, and meta_redirect_onlist sets a URL for existing subscribers.

Link to an AWeber-hosted form or landing page

The hosted URL works without custom code access. Publish the form with Use My Form as a Landing Page and link any Webflow button or text to the generated address. No embed code goes into Webflow, so there is no plan requirement on the Webflow side.

To link a hosted form:

1. On the Publish step, choose Use My Form as a Landing Page and copy the URL.
2. In Webflow, select a button or text link and set its link destination to that URL.
3. Publish the site.

Connect with Zapier, IFTTT, or viaSocket

A Webflow form must receive at least one submission before Zapier can detect it and map its fields. Automation platforms then let you keep native Webflow forms, with their storage, notifications, and reCAPTCHA, while each submission reaches AWeber. Zapier, IFTTT, and viaSocket each publish a direct Webflow and AWeber connector.

To build the Zapier relay, follow AWeber's Zapier guide:

1. In Zapier, click Create Zap and choose the Webflow New Form Submission trigger. Select your site and form.
2. Add the AWeber Create Subscriber action, enter your AWeber login, and click Allow Access.
3. Choose the account and list, then map the Webflow email and name fields. Add tags if you want per-form segmentation.
4. Test the Zap and turn it on.

The connectors expose these triggers and actions:

• Zapier Webflow triggers: New Form Submission, New Order, and Updated Order all fire instantly rather than on a poll.
• Zapier AWeber actions: Create Subscriber and Find or Create Subscriber both carry an optional Tags field, and Update Subscriber can change status or move a subscriber to another list.
• Zapier prebuilt template: a ready-made Zap adds Webflow orders as subscribers without any field mapping of your own.
• IFTTT applets: two ready-made applets cover form submissions and orders, including one that creates subscribers from form submissions, with polling every five minutes on Pro and Pro+ and hourly on Free.
• viaSocket Webflow to AWeber: New Form Submission, New Order, Updated Order, Site Published, and Page Created pair with Add Subscriber To List, Update Subscriber, and Search Subscribers.
• viaSocket AWeber to Webflow: New Subscriber Joins and Subscriber Unsubscribed can drive Webflow CMS steps, though viaSocket warns that a re-subscribe clears the unsubscribe data and the event stops being detected.

AWeber counts subscribers added through any of these platforms as API subscribers, which is why the API confirmation toggle governs them rather than the sign-up form one.

Point a native Webflow form at AWeber with a custom action

Set a native form's Custom action to https://www.aweber.com/scripts/addlead.pl with the POST method, the setup AWeber documents for custom HTML forms. You keep your Webflow form styling and skip any automation platform. You lose Webflow storage and notification emails, because a custom action cannot be combined with the Webflow or Email notification destinations. The reCAPTCHA element does not work with custom actions. A form without it fails immediately when site-wide reCAPTCHA is enforced.

To configure the custom action:

1. Select the form, open its settings, and choose Custom action as the destination.
2. Enter the addlead.pl URL and set the method to POST, the same shape Webflow documents for exported sites.
3. Add hidden inputs for listname, redirect, and meta_required inside the form. Create any custom fields first under List Options > Custom Fields, per AWeber's hidden field guide.
4. Publish and submit a test to confirm the redirect fires.

If you need Webflow-side storage or notifications alongside AWeber, use the automation relay above.

Build with the Webflow and AWeber APIs

Field transformation, custom field mapping, deduplication, and sync from AWeber back into Webflow require server-side code on AWS Lambda, Netlify, Vercel, a Cloudflare Worker, or your own server. You also manage tokens. AWeber authenticates with OAuth 2.0; access tokens expire after two hours and refresh at POST https://auth.aweber.com/oauth2/token with the stored refresh token. The v1 Data API was deprecated March 31, 2025, so new work uses v2 with scoped Bearer tokens. AWeber prohibits posting subscribers to its web form URL from a server-side script, so anything running on your own server has to call the API instead.

The available APIs are:

• AWeber API handles accounts, lists, subscribers, tags, custom fields, and broadcasts at https://api.aweber.com/1.0
• Webflow's Data API handles Webflow CMS collection items and form submissions at https://api.webflow.com/v2
• Webflow webhooks trigger real-time events between systems such as form_submission, collection_item_published, ecomm_new_order, and ecomm_order_changed
• AWeber webhooks push subscriber.added, subscriber.subscribed, and subscriber.unsubscribed back to an endpoint you control, on a best-effort basis

Together, these APIs and webhooks support event-driven sync in either direction.

Create AWeber subscribers from Webflow form submission webhooks

Each site allows up to 75 webhook registrations per trigger type. Register a form_submission webhook, verify each delivery, and post the mapped fields to AWeber's subscribers endpoint. This mirrors the Zapier flow with your own logic between the two steps.

To implement this:

1. Register the webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks. Send {"triggerType": "form_submission", "url": "https://your-server.example.com/webhook/webflow-form"} with a token holding sites:write.
2. Verify each request per the webhooks guide. Compute an HMAC-SHA256 of timestamp + ":" + JSON.stringify(request_body) and compare it to x-webflow-signature. Reject deliveries whose x-webflow-timestamp is more than 5 minutes (300,000 ms) old.
3. Read payload.data for the submitted values, such as "email" and "First Name", and payload.formId to pick the AWeber list and tags. The form_submission event also includes a schema array with fieldName, fieldType, and fieldElementId.
4. Call POST https://api.aweber.com/1.0/accounts/{account_id}/lists/{list_id}/subscribers with {"email": "...", "name": "..."}. The Bearer token needs the subscriber.write scope.
5. Return a 2xx response quickly. Failed deliveries retry up to 3 times at 10-minute intervals.

Since April 14, 2025, each site-settings webhook has its own secret key, so store each webhook's key separately. To avoid duplicates, update an existing subscriber by email with PATCH /accounts/{accountId}/lists/{listId}/subscribers.

Write AWeber subscriber events to Webflow CMS items

Configure three AWeber webhook events on a webhooks-enabled integration: subscriber.added (including unconfirmed), subscriber.subscribed (confirmed), and subscriber.unsubscribed. They use the subscriber.read and account.read scopes and can create or update a CMS item, for example a confirmed-member directory or a public subscriber count. There is no subscriber.updated event, so tag or custom field changes after signup require polling the AWeber API.

To implement this:

1. Set the Webhook URL on your integration in the AWeber control panel, matching a prefix in the integration's Callback URL Allow-list, then verify each delivery with the Verification Key using HMAC-SHA256 over the Date header and body.
2. Deduplicate on the AWeber-Delivery-ID header. AWeber batches rapid events into one delivery and does not guarantee order or delivery.
3. On subscriber.subscribed, call POST https://api.webflow.com/v2/collections/{collection_id}/items/live. Include fieldData with at least name and slug; the token needs cms:write.
4. On subscriber.unsubscribed, call PATCH https://api.webflow.com/v2/collections/{collection_id}/items/{item_id}/live to update a status field.

Bulk live updates accept up to 100 items per PATCH /collections/{collection_id}/items/live call. One item per subscriber consumes collection capacity fast. Use aggregate CMS records for a large list. Since July 7, 2025, setting isDraft to true on a live item no longer unpublishes it; use the dedicated unpublish endpoints.

Send an AWeber broadcast when a CMS item publishes

A collection_item_published webhook fires when a new blog post publishes and can create an AWeber broadcast for that post. This suits publishers who want each CMS post to reach the list without a manual copy step.

To implement this:

1. Register a webhook with triggerType set to collection_item_published, or collection_item_created if you want to draft from staged items.
2. Read fieldData.name and fieldData.slug from the item payload to build the subject line and post link.
3. Call POST https://api.aweber.com/1.0/accounts/{account_id}/lists/{list_id}/broadcasts with a token holding email.write. The payload limit is 1 million bytes.

Scheduling the broadcast is a separate operation on the AWeber API and also needs email.write.

What you can build with the AWeber Webflow integration

A tagged signup can deliver a download, begin buyer onboarding, schedule event reminders, or create a broadcast without manual CSV exports or a separate form builder.

• Gated lead magnet pages: Build a Webflow landing page with an inline AWeber form placed in a Code Embed element. Tag the form so an AWeber workflow emails the PDF the moment someone signs up, and the page needs no thank-you logic of its own.
• Post-purchase sequences from Webflow Ecommerce: Sell a course or digital product through Webflow Ecommerce and use the Zapier New Order trigger to add each buyer with a "buyer" tag. An AWeber workflow then sends access details and onboarding emails without anyone touching the order list.
• Event and webinar registration: Collect registrations with a native Webflow form and relay them through Zapier with a tag per event name. AWeber sends pre-event reminders and post-event follow-ups from that tag.
• Blog launch broadcasts: Publish a post in the Webflow CMS and let a collection_item_published webhook create the AWeber broadcast for that post. The result is a blog where every published article reaches subscribers on the same day.

If you need more control over custom field mapping or two-way subscriber sync, the API path covers those cases. For the relay pattern end to end, read our guide to building a marketing automation hub.

Once the email side is wired up, the site side can be driven the same way. Connect the Webflow MCP server to your AI client and you can create the CMS items, pages, and forms these flows depend on without leaving the conversation.