Hyvor Talk

Threaded comments, six reaction types, star ratings, spam detection, and membership-gated discussions. Hyvor Talk drops all of it into any Webflow page with a single code snippet. It's GDPR compliant, stores data in Germany, and includes a moderation console plus built-in Stripe payments for paid subscription tiers.

The integration fits blogs, documentation, course sites, and any Webflow CMS Collection template that needs reader engagement without standing up backend infrastructure or a comment database.

How to integrate Hyvor Talk with Webflow

What is Hyvor Talk? Hyvor Talk is a commenting and community engagement platform that you embed as a widget on any website. It includes threaded comments, reactions, star ratings, memberships with Stripe-powered payments, and gated content controls. Hyvor Talk is operated by HYVOR, a French company, and is GDPR compliant with all data stored in Germany.

Teams typically reach for Hyvor Talk to power reader engagement on blog posts, Q&A threads on documentation pages, and gated discussions for paying members. The platform handles moderation, spam detection, and user notifications in its own console, so you manage community interactions separately from your content workflow.

You can add Hyvor Talk to your site in four ways:

• Code Embed elements place the comment widget at a specific position on any page or CMS template.
• Site-level custom code loads the widget across all pages from a single snippet in Site Settings.
• Keyless SSO connects your Memberships accounts to Hyvor Talk commenter profiles.
• The Hyvor Talk Console API gives full access to Console actions, while the Data API reads comments, pages, and users; the Webflow Data API handles CMS sync and publishing, though it requires server-side development.

Most implementations start with a Code Embed element on CMS blog templates and add API-driven features as the site grows.

Add Hyvor Talk comments with code embed elements

Code Embed elements give you precise visual control over where the comment widget appears on a page. Drag the element into position on the canvas, paste the Hyvor Talk snippet, and publish. This is the recommended method for adding comments to specific pages or CMS Collection templates because you can place the widget exactly where you want it relative to your page content. You'll need a Hyvor Talk account (free 14-day trial, no credit card required) and a paid site plan to publish custom code.

To set up comments with a Code Embed element:

1. Sign up at the Hyvor Talk Console and register your website by entering its name and domain, then click ADD.
2. Go to Console > Install and copy the embed snippet. Your website-id is pre-filled.
3. Open the page where you want comments to appear.
4. Open the Add panel and drag a Code Embed element onto the canvas where you want the widget (for example, below the blog post body).
5. Double-click the Code Embed element to open its code editor.
6. Paste the full Hyvor Talk snippet and click Save & Close.
7. Publish your site and open the live URL to verify the widget renders.

The Code Embed element shows as a placeholder on the canvas. The actual comment widget only appears on the published site.

Embed on CMS Collection templates with page IDs from CMS fields

When you add comments to a CMS Collection template (like a blog post template), each post needs its own comment thread. By default, Hyvor Talk uses the page's canonical URL as its identifier. That works without extra configuration, but it creates a risk: if you change a post's slug, the URL changes and the comment thread becomes inaccessible.

To bind a fixed CMS field as the page identifier:

1. Create a plain text field in your CMS Collection to store a fixed identifier for each item (for example, a unique ID that never changes when you edit the post slug).
2. On the Collection template page, add a Code Embed element where you want comments.
3. In the code editor, paste the Hyvor Talk snippet. Place your cursor inside the page-id="" attribute value.
4. Use the connect menu (the purple plug icon) to insert the CMS field reference. The actual field value loads in place of the reference at runtime.
5. Click Save & Close, then publish.

After publishing, open a few Collection items on the live site to confirm each post maps to the intended comment thread.

Binding a CMS field to the page-id attribute requires a Business site plan. On a lower-tier plan, the default URL-based identification still works, but avoid changing post slugs after comments accumulate.

Deploy Hyvor Talk site-wide with custom code

If you want the comment widget on every page rather than on specific pages, custom code in head and body tags in Site Settings is faster than adding individual Code Embed elements. This method places the Hyvor Talk script and component tag in your site's footer code, so it loads on every page automatically. You'll need a paid site plan, and the 50,000-character limit per code section is well above what the Hyvor Talk snippet needs.

To add Hyvor Talk site-wide:

1. Click the gear icon to open Site Settings.
2. Go to the Custom Code tab.
3. Paste the Hyvor Talk embed snippet into the Footer Code field.
4. Click Save Changes, then publish your site.

You can also scope the embed to a single page instead of the entire site. Open the page, click the gear icon next to the page name to open Page Settings, scroll to the Custom Code section, and paste the snippet into the "Before </body> tag" field.

The site-wide approach works best when every page should display comments. For blogs where only post pages need comments, a Code Embed element on the Collection template gives you more control over placement.

Connect Webflow Memberships with Hyvor Talk SSO

If your site uses Memberships, you can connect member accounts to Hyvor Talk so logged-in members comment under their real identity without creating a separate Hyvor Talk account. This uses Hyvor Talk's Keyless Stateless SSO mode, designed for platforms that don't give you server-side backend access. You'll need a Hyvor Talk Business plan to enable SSO.

The Keyless SSO method passes user data (name, email, ID) from the client side to the Hyvor Talk embed. It doesn't use HMAC cryptographic signing because no server-side code runs on Webflow-hosted sites. Hyvor Talk's documentation explicitly designates this as the SSO approach for no-backend environments like Webflow and notes you should only use it when backend access isn't available.

To configure Keyless SSO:

1. In the Hyvor Talk Console, go to Console > Settings > SSO.
2. Enable SSO, set the type to Stateless, and check the Keyless option.
3. Enter your site's login page URL (for example, /log-in) as the Login URL. Unauthenticated users who click "Login" in the comment widget land here.
4. On your page, use a Code Embed element with JavaScript that reads the logged-in member's data and passes it to the Hyvor Talk component via the sso-user attribute.

You'll need a third-party JavaScript library such as Sygnal Attributes to access Memberships member data on the client side. The official Webflow Memberships SSO tutorial walks through the full code pattern, including the callback function that sets the sso-user attribute with a JSON payload containing the member's ID, name, email, and a Unix timestamp.

When a member deletes their account, you must explicitly call the Hyvor Talk Console API's DELETE /sso/user endpoint to remove their data. This step isn't automated and requires an external mechanism like a serverless function.

Build with the Webflow and Hyvor Talk APIs

If you need to sync comment data to CMS fields, automate moderation tasks, or pull engagement metrics into external dashboards, the API path gives you full programmatic access. This approach requires server-side development and suits developers building custom integrations between the two platforms.

Three APIs are relevant:

• The Hyvor Talk Data API reads public comments, pages, and users. It supports filtering, sorting, and pagination.
• The Hyvor Talk Console API covers everything you can do in the Console: posting comments, moderating, managing SSO users, configuring webhooks, and running bulk operations.
• The Webflow Data API handles CMS collections, collection items, page custom code, and site publishing.

The Hyvor Talk Console API authenticates with an API key you'll find in your Console settings. The Data API uses website_id, supports api_key for server-side requests, and can also run client-side when you enable public access in the Console. The Webflow Data API uses Bearer token authentication with either site tokens or OAuth tokens.

Sync comment counts to Webflow CMS items

You can display comment counts on blog listing pages by storing them in a CMS field. Since Collection List elements pull data from CMS fields, you can store comment counts as a CMS field value and update it whenever a new comment is posted.

To implement comment count sync:

1. Add a number field (for example, "Comment Count") to your blog post CMS Collection.
2. Hyvor Talk webhooks are available on the Business plan and during the trial period, so you'll need that plan level for this sync workflow.
3. Set up a Hyvor Talk webhook for the comment.create event and point it at your server or serverless function endpoint.
4. When your endpoint receives the webhook payload, extract the page identifier from the comment data.
5. Call the Webflow Data API's PATCH /v2/collections/{collection_id}/items/{item_id} endpoint to update the "Comment Count" field on the matching CMS item.
6. Call POST /v2/collections/{collection_id}/items/publish to publish the updated item.

Hyvor Talk webhooks use HMAC-SHA256 signatures (sent in the X-Signature header) for payload verification. Validate signatures on your server before processing any webhook data. Webhooks retry twice after a failure for a total of three delivery attempts, with no replay mechanism after that.

Pull engagement metrics from the Data API

The Data API's /pages endpoint returns comments_count, per-type reaction counts, and average ratings for each page. Use this data to build a dashboard or populate CMS fields for content performance tracking.

To fetch page engagement data:

1. Send a GET request to https://talk.hyvor.com/api/data/v1/pages?website_id=YOUR_ID&api_key=YOUR_KEY.
2. Filter results using the filter parameter, for example comments_count > 0 to return only pages with comments.
3. Map each page's identifier field to your CMS items and update the relevant fields via the Webflow Data API.

Data API responses are cached for 30 seconds. Each cache-miss request costs 0.25 credits. Within that 30-second window, 1,000 calls to the same endpoint consume just 1 credit total. The Hyvor Talk Data API has no documented per-minute numeric rate limit, but the Webflow Data API v2 allows 60 requests per minute per token, so batch your CMS update calls accordingly.

What can you build with the Hyvor Talk Webflow integration?

Integrating Hyvor Talk with your Webflow site gives you community engagement features on any page without building backend infrastructure or managing a comment database.

• Blog post discussions with moderation: Add threaded comments below each CMS blog post, with automated spam detection (via Akismet or Hyvor's FortGuard engine), pre-moderation queues, and shadow banning. Your editorial team can run conversations from the Hyvor Talk Console while content editors keep working in the Designer independently.
• Member-only commenting on gated content: Connect Memberships to Hyvor Talk via Keyless SSO so only logged-in members can comment. Combine this with Hyvor Talk's gated content embed to restrict article sections to paying subscribers, with Stripe handling subscription payments directly on the page.
• Engagement-ranked content listings: Sync comment counts and reaction data from the Hyvor Talk Data API into CMS number fields. Use those fields to sort Collection Lists by engagement, surfacing the most-discussed posts on your homepage or category pages.
• Multi-language community pages: Deploy the comment widget across your site for international audiences using Hyvor Talk's 30+ language support through a single embed attribute. Each page gets its own comment thread, reactions, and ratings without separate system instances per locale.

If you need more control over data sync or automated moderation rules, the API integration path covers those cases.