Thinkific

You build the marketing site, Webflow CMS course catalog and launch landing pages in Webflow. Thinkific handles lesson playback, enrollment tracking, quiz grading, content dripping, certificates, student login, and lesson gating. Webflow retired User Accounts on January 29, 2026, so student identity now lives in Thinkific or another third-party provider, not in Webflow.

Connecting the two splits the work by strength. Your Webflow site keeps its landing pages and lead forms, including the pricing page, while Thinkific maintains student records and runs checkout plus the course player. Buttons link straight to a product's Thinkific checkout, and Sales Widgets render inside a Code Embed element. Zapier enrolls form submitters, and a small server of your own turns Thinkific webhooks into CMS updates.

Independent course creators with an existing Webflow brand site get a buy button without rebuilding anything. Agencies building course marketing sites for clients get a CMS-driven catalog that links to each Thinkific product. SaaS marketing teams use the pair to run a customer academy at academy.yourproduct.com behind a "Get certified" link in the navbar. Partner enablement managers register resellers through a Webflow form and automatically provision their Thinkific accounts.

How to integrate Thinkific with Webflow

What is Thinkific? Thinkific is a learning management platform for creating and selling courses, communities, memberships, digital downloads, coaching, and webinars. It includes a drag-and-drop course builder, a hosted checkout, and a site builder that runs on a thinkific.com subdomain or on your own domain. Its Grow and Plus plans add API access and webhooks.

Both platforms also run MCP servers, so one AI agent can work across them. Webflow's MCP server lets an agent manage your CMS collections and pages, and Thinkific MCP lets Claude search your courses, learners, enrollments, bundles, and products. Thinkific's server is read-only, in beta, rolling out gradually, and limited to Plus plans, so use the pair for work such as drafting Webflow CMS course pages from your live catalog rather than for enrolling anyone.

Every method below either routes a visitor from one domain to the other or moves data between them. Checkout links, Sales Widgets, and a custom subdomain connect the two sites with nothing more than a pasted link or snippet. Automation platforms such as Zapier, Make, IFTTT, and viaSocket move form submissions and enrollments between them without a server of your own. The Webflow Data API and Thinkific APIs give you full control over enrollment logic and CMS sync, but need server-side code. Most builds combine two of these.

Add Thinkific checkout links and Sales Widgets to Webflow pages

Thinkific gives each published product a specific checkout URL, and any Webflow button can point to it. Thinkific also generates a Sales Widget, an HTML snippet showing a product card or a buy button, that you paste into a Code Embed element. Direct links work on all Thinkific plans, and no plan requirement is documented for Sales Widgets. Both keep visitors on your Webflow page until they click through to Thinkific's hosted checkout. A custom subdomain puts that checkout under your own domain. Thinkific's linking guide covers navigation linking, subdomain placement, and checkout linking.

Link buttons to a specific product checkout

The fastest connection is a Link element pointing at a product's direct checkout URL, which takes the form https://yoursite.thinkific.com/enroll/####?price_id=#### and uses your custom domain instead once one is set. Each price option has its own URL, and Thinkific only lets you copy the checkout link after the product is published.

To link a Webflow button to Thinkific checkout:

1. In Thinkific, open the product's Pricing tab and click Copy Link beside the price you want to sell.
2. In Webflow, select the button, open its link settings, choose the URL option, and paste the address.
3. For a CMS catalog, add a Link field named "Checkout URL" to your courses Collection. Bind each card's button inside a Collection List to that field.
4. Publish the site and test the button in a private browser window.

On Start plans and above, Thinkific's After Purchase Flow can redirect buyers to a custom URL, so you can land them on a Webflow thank-you page after checkout.

Embed a Thinkific Sales Widget with Code Embed

A Sales Widget adds a buy button and can show the product's image with its price on a Webflow page. Thinkific generates the snippet under Admin Dashboard > Channels > Widget, and you paste it into a Code Embed element. The product must be published before you create the widget. Buyers complete payment on Thinkific's hosted checkout page. Thinkific documents the widget in its Sales Widgets guide.

To embed the widget:

1. Publish the product in Thinkific, then go to Channels > Widget and generate the snippet as a card or a button.
2. Copy the HTML.
3. In Webflow, open the Add panel and drag a Code Embed element onto the page.
4. Paste the snippet and click Save and close.
5. Publish the site.

The widget method has a few documented limits:

• Coaching and Webinars: Thinkific does not support these product types in Sales Widgets.
• Free lead magnets: Digital Downloads set as free lead magnets are not supported either.
• Code Embed size: Each Code Embed element accepts up to 50,000 characters and runs HTML, CSS in <style> tags, and JavaScript in <script> tags only.
• Webflow plan: Code Embed requires an active Site plan or a Core, Growth, Agency, or Freelancer Workspace plan.

To show a different widget for each course, place the Code Embed inside a Collection List or on a Collection page and insert CMS field values into the snippet with dynamic embed data. The same pattern powers Webflow's guide to embedding Shopify products.

Serve Thinkific on a subdomain of your Webflow domain

With the root domain on Webflow and Thinkific at courses.yourdomain.com, visitors move between the two sites under one brand. The Thinkific side needs a CNAME record pointing your subdomain to yoursite.thinkific.com. The Webflow side keeps its own DNS records for the root domain. Thinkific supports subdomains only, so learn, courses, or academy work but the apex domain does not. Any paid Thinkific plan and a paid Webflow Site plan cover this setup.

To put Thinkific on a subdomain:

1. At your DNS host, keep the root-domain records from Webflow's manual domain setup, an A record for @ pointing to 198.202.211.1 and a CNAME for www pointing to cdn.webflow.com.
2. Add a CNAME record for courses pointing to yoursite.thinkific.com.
3. In Thinkific, go to Settings > Site > Site URL > Add Custom URL, enter the subdomain, and save. Propagation can take up to 24 hours, per the Custom Domains guide.
4. In Webflow, add a "Courses" link to the Navbar pointing to the new subdomain.
5. In Thinkific, set the header logo to link back to your Webflow root domain.

Without SSO, which Thinkific sells only on its Plus plan, students log in on the Thinkific subdomain separately from anything they do on the Webflow site.

Connect with Zapier, Make, IFTTT, or viaSocket

The Webflow Marketplace has no Thinkific app, and the Thinkific App Store has no Webflow app. Automation platforms provide the no-code bridge between them. Thinkific's own documentation describes Zapier as "a tool that allows you to connect applications that aren't in our App Store". Zapier also publishes a ready-made Webflow-to-Thinkific template, and Thinkific's Zapier connection has used OAuth since January 4, 2023. Zapier triggers work on every plan, while the Enroll User and Unenroll User actions need Grow or higher, according to Working with Zapier.

Enroll Webflow form submitters with Zapier

Zapier's ready-made template maps a Webflow New Form Submission trigger to Thinkific's Enroll User action, which creates or finds the user and enrolls them in a course or bundle. It needs First Name, Last Name, and Email from the form, so add those fields to your Webflow form first. The Webflow trigger only connects after at least one submission exists, per Webflow's Zapier guide. Thinkific's Lead Capture section asks only for an email address, so a Webflow form with custom fields is the better front door.

To set up the Zap:

1. In Thinkific, go to Apps > App Store, open Zapier, click Install, then Accept to authorize with OAuth.
2. Publish your Webflow site and submit the form once so a sample submission exists.
3. Open Zapier's Webflow-to-Thinkific template, connect your Webflow account, and pick the site and form.
4. Connect Thinkific, choose the course, and map the First Name, Last Name, and Email fields.
5. Test the Zap and turn it on.

Other Webflow-to-Thinkific combinations you can build in Zapier include:

• Webflow New Order to Thinkific Enroll User: Enrolls buyers when you sell a course through Webflow Ecommerce.
• Thinkific New Full Enrollment to Webflow: Creates a live CMS item, or updates an existing one, for each new student.
• Thinkific New Order to Webflow Update Item: Writes order details onto an existing CMS item.
• Thinkific Course Completed to Webflow Create Live Item: Publishes a graduate entry when a student finishes a course.
• Thinkific Subscription Cancelled to Webflow Update Item: Flags a member record when a subscription ends.

Thinkific exposes eight Zapier triggers in all, including Lesson Completed, New Lead, and New Free Preview Enrollment, each described in the same Working with Zapier article.

Build the same flows in Make, IFTTT, or viaSocket

All three platforms carry both a Webflow connector and a Thinkific connector, and you assemble the flow from the two yourself. Make's Webflow app has no dedicated form-submission trigger, so start from its Watch Events webhook module or poll with List Form Submissions, then chain Thinkific's Create a User and Enroll a User modules. Webflow's Make setup guide covers connecting your Webflow account.

The building blocks for a Thinkific flow on each platform are:

• Make, Thinkific side: Triggers include Watch Enrollment Created, Watch Enrollment Completed, Watch Order Created, and Watch New User, listed among the Thinkific modules.
• Make, Webflow side: Actions include Create an Item, Update an Item, Publish an Item, and Publish a Site, listed among the Webflow modules.
• IFTTT: Thinkific triggers New full enrollment, New order, New user, and Course completed with the action Create and enroll user, plus Webflow triggers Form submitted, New order, and New collection item with actions Create collection item, Create live collection item, and Publish site (Thinkific on IFTTT, Webflow on IFTTT).
• viaSocket: Thinkific triggers When a new user is created and When a new order is created with actions Enroll Student In Course and Create User Account, plus Webflow triggers New Form Submission, New Order, and Site Published with actions Create Item, Create Live Item, and Update Item (Thinkific on viaSocket, Webflow on viaSocket).

In every case, pushing an enrollment into Thinkific counts as an enrollment write, and Thinkific gates enrollment writes to the Grow plan and above in its REST Permissions and Scopes.

Build with the Webflow and Thinkific APIs

Zapier's fixed actions cannot express deduplication, enrollment checks, or a fully synced course catalog. Those requirements call for a server you control, whether a serverless function, an existing backend, or an app on Webflow Cloud, which runs Next.js, Astro, Vite, and static apps. On the Thinkific side, standard API access and webhooks require the Grow plan or above. Create a token under Settings > Code & analytics > API Access Tokens > Add API access token, give it a name and an expiry date, and copy it right away because it displays only once, per Thinkific's token guide. Plan to rotate it before that date. On the Webflow side, generate a site token under Site settings > Apps & integrations > API access > Generate API token. Use Data API v2, since v1 reached end of support on March 31, 2025.

The APIs involved are:

• Thinkific Admin API: Handles users, enrollments, courses, products, and orders at https://api.thinkific.com/api/public/v1, per the Admin API reference.
• Thinkific Webhooks API: Registers subscriptions to event topics such as enrollment.created and order.created through the Webhooks API reference.
• Webflow Data API: Reads and writes CMS collections and lists form submissions.
• Webflow webhooks: Send real-time events such as form_submission and collection_item_created, as covered in the webhooks guide.

Your Webflow token needs the cms:read, cms:write, forms:read, and sites:write scopes for the flows below, and Thinkific accepts either an API Access Token or an OAuth 2.0 Bearer token.

Enroll a student from a Webflow form submission

This flow replaces the Zapier template with your own endpoint, which lets you deduplicate users and skip enrollments that already exist. Each form submission triggers a signed POST to your URL. Your server then looks up or creates the Thinkific user and creates the enrollment.

To implement this:

1. Register the webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks. Set triggerType to form_submission and point it at your endpoint. This call needs the sites:write scope.
2. On each delivery, verify the x-webflow-timestamp and x-webflow-signature headers and reject requests older than five minutes. The payload contains name, siteId, formId, data, and submittedAt.
3. Check for an existing user with GET https://api.thinkific.com/api/public/v1/users?query[email]={email}.
4. If none exists, call POST https://api.thinkific.com/api/public/v1/users with email, first_name, and last_name.
5. Check GET /enrollments?query[user_id]={user_id}&query[course_id]={course_id}. If nothing returns, call POST https://api.thinkific.com/api/public/v1/enrollments with course_id, user_id, and an activated_at timestamp. Without activated_at, Thinkific creates the enrollment as a free trial.

Thinkific's Admin API reference documents no idempotency key, so the two lookups are what prevent duplicate accounts when a delivery retries. Webflow retries a failed webhook delivery up to 3 times at 10-minute intervals.

Write Thinkific events into Webflow CMS items

The enrollment.completed payload includes percentage_completed, completed_at, certificate_url, and the student's user.email. The order.created payload includes order_number, amount_dollars, product_name, and coupon.code. Thinkific sends these events to your server in near real time, and the Data API writes them into a Collection. Full payloads for all topics are in Thinkific's Webhooks Documentation.

To sync events into the CMS:

1. Create the subscription with POST https://api.thinkific.com/api/v2/webhooks. Send Authorization: Bearer <api_key> along with your target URL and topic.
2. On delivery, verify the X-Thinkific-Hmac-Sha256 header and respond 200 OK within 5 seconds. Thinkific retries up to 14 times over 16 hours with a growing delay, per Using Webhooks.
3. Find the target item with GET https://api.webflow.com/v2/collections/{collection_id}/items, which accepts filter parameters on custom field values, and decide from the result whether to create or update.
4. Update in place with PATCH https://api.webflow.com/v2/collections/{collection_id}/items/{item_id}/live, which publishes the change to the live site. Or use PATCH .../items/{item_id} followed by POST .../items/publish with an itemIds array.

Leave the slug field out of update requests unless you intend to change it, because changing a slug breaks every link that references the old one.

Sync the Thinkific course catalog into a Collection

Pull the catalog once with the Admin API, then keep it current with the product.created, product.updated, and product.deleted webhooks. A course catalog Collection lets you build filterable course pages in Webflow while Thinkific stays the source of truth.

To sync the catalog:

1. List courses with GET https://api.thinkific.com/api/public/v1/courses and products with GET https://api.thinkific.com/api/public/v1/products. Pages default to 25 items and accept up to 250 via limit, per the response format docs; follow meta.pagination.next_page.
2. Create items in bulk with POST https://api.webflow.com/v2/collections/{collection_id}/items/live. Send an items array. A request carrying both fieldData and items returns a 400.
3. Map the product payload fields name, slug, card_image_url, description, and product_prices[0].price to Collection fields, and store each checkout URL in a Link field.
4. Render the Collection with a Collection List and bind each card's button to the Link field.

If you want the initial import held for review, create staged items with POST .../items instead and publish them later with POST .../items/publish.

What you can build with Thinkific and Webflow

Four common implementations use these methods:

• CMS course catalog with direct checkout: A courses Collection where each card's button points to that product's Thinkific checkout URL. An IT training company gets a filterable catalog page on its own domain, and every buy button ends in Thinkific's hosted checkout.
• Launch landing page with automatic enrollment: A cohort waitlist form on a Webflow landing page wired to the Zapier Enroll User action. A coaching business confirms participants and enrolls them in the Thinkific course without leaving its brand site.
• Customer academy on a branded subdomain: A "Get certified" link in the Webflow navbar that sends customers to academy.yourproduct.com. The SaaS company's onboarding courses run on Thinkific there, and the Thinkific logo links back to the Webflow site.
• Live completion and certificate feed: A graduates Collection populated by enrollment.completed webhooks that store each certificate_url and completion date. An association publishes a searchable directory of certified members in a Collection List.

Gating Webflow pages by enrollment status needs an identity layer of its own, because Webflow no longer has native User Accounts. Pair a membership tool such as Memberstack or Outseta, or a Webflow Cloud app with its own sign-in, with the Thinkific enrollment API. To see the same catalog pattern on another course platform, follow our guide to integrate Kajabi courses with Webflow Cloud.