Thinkific

How to integrate Thinkific with Webflow

Course creators want design flexibility for marketing pages without sacrificing Thinkific's course delivery features. Integration options include native embeds and sales widgets (no-code), Zapier or Make automation (form-to-enrollment), or custom API middleware (real-time sync).

A split-site architecture provides full Webflow marketing control while Thinkific handles courses. Simple methods require no code; API integration via the Thinkific REST API and Webflow Data API enables advanced real-time sync.

Native embeds and sales widgets

Thinkific offers two no-code connection methods: direct checkout links and sales widgets. Both redirect visitors to Thinkific-hosted pages for enrollment.

Direct checkout links work by copying a course URL from Thinkific's product settings (e.g., yourschool.thinkific.com/courses/course-name/checkout) into any Webflow button or link. No embed code is needed.

Sales widgets display course info and enrollment buttons. Generate them in Thinkific under Settings → Sales Widgets, customize appearance, then paste the HTML into a Webflow custom code embed.

Sales widget customization options:

• Button widgets for minimal CTAs
• Card widgets with images, titles, descriptions, and pricing
• Custom button/background colors
• Custom button text
• Landing page or direct checkout destinations
• Specific course or community selection

Full course content cannot be embedded on Webflow pages. The CSP and X-Frame-Options security restrictions prevent iframe embedding. The course player must run on Thinkific-hosted pages. Use a custom domain like learn.yoursite.com and match theme styling for brand consistency.

Connect with Zapier or Make

Zapier and Make provide no-code automation connecting Webflow forms to Thinkific enrollments. Data syncing requires custom API middleware or additional configuration.

Zapier offers 8 Thinkific triggers and 4 actions. Triggers: New Order, New Full Enrollment, Course Completed, Lesson Completed, New User, Subscription Cancelled, New Free Preview Enrollment, New Lead. Actions: Enroll User, Unenroll User, Create User, Find User. The Webflow integration provides form submission triggers and CMS item actions.

A common workflow enrolls users upon submission of a Webflow form. The pre-built template guides account connection and field mapping.

Zapier automation scenarios:

• Sync new enrollments to Webflow CMS student records
• Update CMS items on course completion
• Sync order data for unified customer databases
• Convert form submissions to enrollments (requires Thinkific Grow plan+)

Enroll/Unenroll actions require Thinkific Grow plan or higher. Basic and Start plans only receive data.

Make offers integration via the official Thinkific integration with a visual flowchart interface. The Watch Enrollments trigger monitors new enrollments; the Webflow integration supports CMS operations and custom API calls. Make excels at complex multi-platform scenarios but lacks Zapier's pre-built templates.

Build with Webflow and Thinkific APIs

Custom API integration enables real-time sync, conditional enrollment logic, and programmatic course management. This requires server-side middleware since both APIs block client-side calls due to CORS restrictions. Sales widgets and checkout links don't require middleware.

The Thinkific REST API and Webflow Data API v2 use JSON over HTTPS. Common uses: syncing course catalogs to Webflow CMS, dynamic course pages with real-time pricing, and complex enrollment rules.

Authentication and setup

Both platforms use API key authentication. Thinkific requires X-Auth-API-Key and X-Auth-Subdomain headers per the authorization documentation. Find credentials in Site Settings → Code & Analytics.

Webflow uses Bearer token authentication per the authentication documentation. Generate Site Tokens in Apps & Integrations → API access, or use OAuth 2.0 for multi-user apps. See the API overview.

Sync course catalog to Webflow CMS

Technical challenge: Displaying Thinkific course data in Webflow requires syncing catalogs across independent platforms.

Build a Webflow course catalog using the GET /courses endpoint. Limitation: you can display course info in Webflow but cannot embed the course player due to CSP restrictions. Pull titles, descriptions, and pricing for display, then direct students to Thinkific for the course experience. Alternatively, use Sales Widgets for promotional cards with checkout links.

Create a "Courses" collection with fields for ID, title, description, price, and status. Fetch from GET https://api.thinkific.com/api/public/v1/courses with parameters like published=true and limit=250. Map responses to Webflow CMS using the Webflow CMS API.

Use POST https://api.webflow.com/v2/collections/:collection_id/items/bulk for batch updates. Store the returned id alongside Thinkific course IDs for reference. Schedule hourly syncs or trigger via Thinkific webhooks on course.created, course.updated, or enrollment.created.

Automate enrollment with webhooks

Technical challenge: Polling for enrollment changes is inefficient. The webhooks API pushes real-time notifications for signups, completions, and orders.

Register webhooks via POST https://api.thinkific.com/api/v2/webhooks. Key events: user.signup, enrollment.created, enrollment.completed, order.created.

Verify the X-Thinkific-Hmac-Sha256 header for security. Extract payload data and update Webflow CMS collections—e.g., update student records with completion status on enrollment.completed.

Display course enrollment data in Webflow

Create promotional displays and enrollment links using Webflow Memberships for authentication and the Thinkific Enrollments API for status. Students access progress, certificates, and history within Thinkific directly due to CSP restrictions.

For logged-in members, middleware calls GET https://api.thinkific.com/api/public/v1/enrollments filtered by user_id with headers X-Auth-API-Key and X-Auth-Subdomain. Query the Webflow Users API to match users.

Use server-side middleware that caches API responses. For certificates, subscribe to enrollment.completed webhooks, retrieve URLs via API, and store in CMS. Display download links—direct embedding isn't possible. Fetch progress server-side for CMS pages; client-side API calls fail due to CORS.

What you can build

Thinkific-Webflow integration enables custom learning experiences with split-site architecture: Webflow for marketing, Thinkific for delivery.

• Custom course marketplaces: Build filterable catalogs in Webflow CMS with Sales Widgets or checkout links
• Lead generation funnels: Create multi-step Webflow forms, trigger automated Thinkific enrollments via Zapier or Make, and track the full funnel
• Corporate training portals: Build branded landing pages per department, link to Thinkific courses on learn.yourcompany.com, automate enrollment from forms
• Member-exclusive learning hubs with enrollment tracking: Combine Webflow Memberships with Thinkific course delivery to create gated learning portals