flowstar-polls-post-purchase-survey-nps

Webflow native forms collect submissions. Interactive poll and survey widgets need question logic plus a place to store and review responses. Asking one question on a product page or after checkout can turn into a custom development project.

Connecting Flowstar Polls with Webflow lets you ask visitors questions directly on your pages without building any of that infrastructure. Flowstar handles the widget and stores responses for reporting. Setup runs through the Webflow Marketplace with no coding required.

Ecommerce merchants can gather post-purchase feedback with the integration, while product managers and marketing teams can use poll responses for idea validation and audience segmentation. Agencies managing client Webflow sites can install and configure it without touching code.

How to integrate flowstar polls post-purchase survey nps with Webflow

What is Flowstar Polls- post-purchase survey NPS? Flowstar Polls is a no-code tool for adding interactive polls and surveys to your Webflow site. Flowstar builds apps exclusively for Webflow and distributes them through the Webflow Marketplace. 

You can integrate Flowstar Polls with Webflow in three ways, from simplest to most technical: install the Flowstar: Polls Marketplace app to build and run polls with no code, add a CSS class or ID to control where the poll widget appears, and call the Webflow Data API when you want poll pages tied into your own backend. Most site owners, marketers, and agencies need only the app. Which pages you put a poll on depends on what you want to learn from visitors.

A shop can ask buyers about their checkout experience directly after purchase, and blogs can poll readers on topic ideas. A startup can test a concept from its landing page. Flowstar positions Polls for homepages, product pages, blog posts, and custom pages.

Setup usually starts with the Marketplace app. Depending on placement and backend needs, these options may matter:

• The Flowstar: Polls app handles no-code installation and poll building, with reporting inside Flowstar.
• CSS class and ID targeting is documented for Flowstar Bundle Builder; for Polls, confirm the same placement control in the app UI or with Flowstar before relying on it.
• The Webflow Data API supports server-side workflows around your poll pages and requires backend development. Flowstar itself exposes no public API.

Most setups need only the app; the other two paths cover potential placement control and custom builds.

Install the Flowstar Polls app

The Flowstar: Polls app on the Webflow Marketplace is the only integration method Flowstar officially supports, and the listing carries the "Approved by Webflow" badge. Installation runs through OAuth 2.0. The app requests the custom_code:write scope, which means it injects its widget code into your site automatically after you authorize it. You never paste a script tag. Because of that scope, your site needs custom code access, which requires a Core, Growth, Agency, or Freelancer Workspace plan, or an active paid Site plan; see Custom code in head and body tags.

To set up the integration:

1. Open the app page on the Webflow Marketplace and click Add to site.
2. Select the Workspaces or sites where you want the app, then click Authorize app.
3. Create a Flowstar account with your name, email, and password.
4. Click Go to Flowstar: Polls and follow the app's setup instructions.
5. Build your poll inside the app, then publish your site to push it live.

The app's Marketplace listing documents four features:

• A drag-and-drop builder for branded polls
• Ready-made templates
• Full mobile responsiveness
• Real-time reporting that lets you analyze responses as they come in

After install, the app appears in the Apps section. Manage its authorization under Site settings > Integrations > Authorized apps, or at the Workspace level under Workspace settings > Integrations > Connected apps.

Target widget placement with CSS classes and IDs

Flowstar has not published a Polls-specific setup guide for CSS class or ID placement. For Bundle Builder, Flowstar documents inline widget placement by matching a CSS class or element ID that you define in Webflow. You enter the class name or ID in the app's settings panel, and the widget renders on the matching element. Flowstar documents this pattern in its Bundle Builder documentation, which instructs users to "Enter the necessary class where you would like to display your widget." Confirm in the Polls app UI or with Flowstar before assuming Polls uses the same targeting method.

If the Polls app exposes this setting, the pattern is:

1. In Webflow, select the element where the widget should appear.
2. Add a class or set an element ID on that element.
3. Open the Flowstar app from the Apps section and enter the class or ID in the placement settings.
4. Publish the site.

Build around the integration with the Webflow Data API

Flowstar publishes no public API, webhooks, or automation platform connectors, as its own Webflow integration documentation confirms. Programmatic work in a Flowstar-Webflow setup therefore happens entirely on the Webflow side through the Data API v2. The production base URL is https://api.webflow.com/v2/, and requests authenticate with a bearer token in the Authorization header. This path suits developers who want poll-driven content or site events flowing through their own backend, and it requires server-side development.

For Webflow-side development, choose the API area that matches the workflow:

• CMS Collection Items endpoints read and write Webflow CMS content with the cms:read and cms:write scopes
• Form submission endpoints list native Webflow form data with the forms:read scope
• Webflow webhooks trigger real-time events such as form_submission, ecomm_new_order, and collection_item_published

OAuth authorization codes are single-use and expire after 15 minutes, so build the token exchange into your flow early. Webhook registrations cap at 75 per trigger type, per site.

Publish poll findings to the CMS

Flowstar's reporting lives in its own dashboard, and no API exposes it. To display poll results on your site, write them to a CMS Collection and render them with a Collection List. Pulling numbers out of the Flowstar dashboard is a manual step, but the publishing side can be fully automated.

To implement this:

1. Find your target collection with GET https://api.webflow.com/v2/sites/{site_id}/collections, or create one with a POST to the same endpoint.
2. Add result fields with POST /v2/collections/{collection_id}/fields; supported field types include PlainText, Number, and DateTime.
3. Create and publish items in one call with POST /v2/collections/{collection_id}/items/live, or stage up to 100 at once via POST /v2/collections/{collection_id}/items/bulk and then POST /v2/collections/{collection_id}/items/publish.

Plan result archives against CMS item capacity; the CMS plan holds 2,000 items and the Business plan holds 10,000.

What can you build with the Flowstar Polls Webflow integration?

Integrating Flowstar Polls with Webflow lets you collect visitor feedback on live pages without building survey infrastructure or sending traffic to an external form tool.

• On-page visitor polls: A clothing retailer places a one-question poll on a product page to learn which variant to stock next, with responses visible in the Flowstar dashboard as they arrive.
• Post-purchase surveys: An ecommerce store asks buyers about the checkout experience after an order completes. Flowstar positions Polls for browsing, checkout, and post-purchase contexts.
• Product idea validation: A startup landing page polls early visitors on a planned feature before committing development time.
• Audience segmentation and personalization: A podcast site polls listeners on preferred episode formats, then uses responses to personalize the site experience for returning visitors.

If you need more control over publishing results or reacting to site events, the API integration path covers those cases with full flexibility.