Flowstar Urgency Countdown Timer

A hand-built countdown in Webflow usually means custom JavaScript, timezone handling, and a retest on every device each time the layout moves. Whoever wrote the script owns it afterwards, so each new deadline goes back through a developer instead of through marketing.

Flowstar's Urgency Countdown Timer takes the code out of that job. You set an end date and the surrounding messaging in Flowstar's dashboard, and the countdown renders on your published pages. One thing to know before you go looking for it: the timer no longer has its own Marketplace listing. Flowstar retired the standalone app and folded the countdown into Flowstar Sales Booster Widgets, a single install that carries the timer alongside the rest of Flowstar's conversion widgets. Older links pointing at a standalone countdown app return a 404, including the one on Flowstar's own site.

Ecommerce managers use it for flash sales on Webflow Ecommerce stores. Agencies and freelancers reach for it when a client site has to keep running promotions after handover without anyone maintaining a script. Marketers use it on launch pages and event registration deadlines.

How to integrate Flowstar Urgency Countdown Timer with Webflow

What is Flowstar Urgency Countdown Timer? Flowstar Urgency Countdown Timer is a countdown widget for Webflow sites, built by Flowstar. You configure the end date and the copy that runs before and after it in Flowstar's dashboard, and the app renders the countdown on the published site. It is distributed as part of Flowstar Sales Booster Widgets rather than as its own app.

Teams pair the two when a published page has to reflect a real cutoff: limited-time promotions, flash sales, seasonal events, product launches, and event registration deadlines. The timer sits outside your page structure, so changing a campaign never touches your layout, and marketing can run the deadline without a build.

Two paths are worth knowing. The Flowstar Sales Booster Widgets app is the documented no-code route and covers installation, timer setup, and display targeting from a dashboard. The Webflow Data API is the route you take when the campaign dates and deadline copy live in your CMS and other systems have to react when they change, which needs server-side development. Most teams start with the app and add the API only once deadlines stop living in one place.

Install the timer with Flowstar Sales Booster Widgets

Sales Booster Widgets is the app that now carries the countdown, and it has passed Webflow's Marketplace review. During installation it requests permission to read and write site data and publishing, read and write custom code, read information about authorized users, and read your assets, CMS data, page data, and Ecommerce store. It injects its own scripts once installed, and you manage everything from the Flowstar dashboard in your Apps panel.

To set up the integration:

1. Open Apps & Integrations from your Webflow dashboard.
2. Search the Marketplace for Flowstar Sales Booster Widgets, or open the install button on this page.
3. Click Install and approve the requested permissions.
4. Open the Flowstar dashboard from your Apps panel and create a countdown.
5. Set the end date and time, then write the messaging that shows before and after the clock hits zero.
6. Choose where the countdown appears, then save and publish your site.

The countdown runs on the published site from that point, and further edits happen in the Flowstar dashboard rather than in Webflow.

Because the timer arrives as part of a bundle, the same install also gives you the other widgets Flowstar groups under sales and urgency:

• Countdown timer: The urgency widget covered on this page, driven by an end date you set once and edit from the dashboard.
• Estimated delivery date: Shows shoppers when an order placed now would arrive, which pairs with a sale deadline on product pages.
• Sales popups and coupon popups: Surface recent purchase activity or a discount code while the countdown is still running.
• Age verification and size guides: Store-side widgets from the same bundle, with the age gate covered on our age verification integration page.

Check which bundle you are installing before you click through. Flowstar also ships a Visual Widgets Toolkit, and that one carries galleries and sliders rather than the countdown, so installing it will not get you a timer.

The app injects its own scripts, so you never paste anything into your site's head and body tags or into a Code Embed element. Anchor the end date to a deadline that actually exists. A countdown tied to an arbitrary or quietly repeating date reads as a gimmick, and repeat visitors notice. Binding a timer to a per-item date field in a Collection is not documented anywhere, so confirm that behavior with Flowstar support before you scope work around it.

Build with the Webflow Data API

Flowstar publishes no public API, SDK, or webhooks for the countdown, so every programmatic move happens on the Webflow side. This path applies when your campaign deadlines live in Webflow CMS Collections, or when another system has to react the moment a date changes. The CMS holds the deadline copy readers see; the Flowstar dashboard holds the timer's end date. You update the two together.

Two groups of endpoints do the work. The CMS item endpoints list, create, update, and publish the Collection items holding your campaign copy. Registered webhook events such as collection_item_changed, site_publish, and ecomm_new_order tell your backend when that content moves.

Keep CMS deadline copy in sync with your Flowstar timer

Take a sale end date stored in a Collection and rendered by a Collection page template. Your backend reads those items, catches the change when the date moves, updates anything downstream, and republishes. You need server-side code and an authenticated app or site token.

1. Register a webhook against POST https://api.webflow.com/v2/sites/{site_id}/webhooks with triggerType: "collection_item_changed". The payload carries the item ID, site ID, collection ID, and the item's field data.
2. In your handler, validate the x-webflow-signature header, a SHA-256 HMAC signed with your site token secret or your OAuth app's client secret. Webflow's webhook signature validation docs treat a request older than 5 minutes as a possible replay.
3. Update related items with PATCH /v2/collections/{collection_id}/items, then push them live with POST /v2/collections/{collection_id}/items/publish.
4. Republish the site with POST /v2/sites/{site_id}/publish so the change reaches your live domain.

Log delivery failures and re-register the webhook if it deactivates. Note the one thing this cannot do: scheduling a future publication is outside the API's control per the CMS publishing docs, and publishes go out immediately. And because Flowstar exposes no API, a date change in the CMS does not move the countdown. Edit it in the dashboard in the same pass, or the page will show two different deadlines.

If you would rather not write those calls by hand, the Webflow MCP server exposes the same CMS work to an AI agent in plain language, including bulk item updates and publishing, and it reads Webflow Analyze traffic and engagement data so you can check how pages carrying a countdown actually performed. It runs inside your existing Webflow permissions and roles. It does not reach into Flowstar, so the dashboard edit stays manual.

What you can build with Flowstar Urgency Countdown Timer and Webflow

Pairing the two lets you ship time-boxed offers on any page without a hand-maintained timer script, and lets a marketer change the deadline without opening the site.

The combinations teams get the most out of:

• Flash sales on Webflow Ecommerce stores: Run a countdown across the store during a promotion, with messaging that swaps over once the sale closes so the page never strands a dead offer.
• Coming-soon launch pages: Count down to launch day next to a signup form, and let the post-expiry copy hand visitors to the live product.
• Event and webinar registration deadlines: Put the cutoff date above the registration form so the urgency sits where the decision happens rather than in a banner people scroll past.
• CMS-driven seasonal campaigns: Store each promotion's end date in a Collection, render it in your page copy through the API path above, and keep the dashboard timer pointed at the same date.

That last one is where most of the engineering sits. Read our Webflow CMS API guide before you build it.