Keep your Webflow press page updated with new coverage
Every morning we scan the news for mentions of your company and stage each new article on your Webflow press page, ready for a quick review.
Every day at 8am, find new articles that mention my company and stage them on the "In the news" page of my Webflow site, so the page stays current without anyone maintaining it by hand. Use a cron trigger set to 8am in my timezone. NewsAPI is a read-only API with no outgoing webhooks, so a schedule is the right trigger here.
Step one, search for coverage. Use NewsAPI Search Everything. Take my company name as a configurable input and wrap it in double quotes in the query so it is matched as an exact phrase, for example "Acme Robotics" rather than the bare words. This matters because a brand name that doubles as a common word will otherwise pull in unrelated coverage. Also expose an optional input for a list of known outlets, and when it is set, restrict the search to those sources or domains. Sort by publish date, request the maximum page size, and set the start of the date range to three days ago so nothing is missed. The free NewsAPI plan delays articles by up to 24 hours, so a slightly wider window than one day is deliberate. Every NewsAPI response carries a top level status field, so check it is ok before reading the articles.
Step two, read what is already on the site. Call Webflow Get Collection Details on my press collection first to discover the field slugs, since Webflow item data is keyed by field slug rather than display name. Then call Webflow List Collection Items on the same collection and page through it using offset based pagination, incrementing the offset by the limit until the offset reaches the total in the pagination object. Collect the article link stored on every existing item.
Step three, dedupe on the article link, not the headline. The same story is frequently re-syndicated with slightly reworded headlines, so the link is the reliable identity. Normalize both sides before comparing by lowercasing the host, stripping tracking and query parameters, and dropping any trailing slash. Discard every search result whose link already exists on the page.
Step four, stage each genuinely new article. For every remaining result, call Webflow Create Collection Item as a staged draft rather than a live item. Map the article headline to the item name, the source name to the publication field, the publish date to the date field, and the article URL to the link field, using the field slugs read from the collection schema. Staging as a draft is deliberate, because a person should approve anything that renders on a public site and reviewers often want to exclude low quality outlets.
Step five, tell comms. Close with a single Slack Send a Message to the comms channel stating how many new mentions were staged, followed by the headline and publication of each one, and a note that they are drafts awaiting review and publishing. Send one message per run, not one per article.
A few constraints. Never publish items to the live site, always leave them staged for review. Run once per day with a single search so the workflow stays well inside the free NewsAPI quota of 100 requests per day. If NewsAPI returns an error status or a rate limit response, stop without creating any items and say so in the Slack message rather than leaving the page half updated.
What does this prompt do?
- Searches the news every morning for articles that mention your company by name, matched as an exact phrase so unrelated stories stay out.
- Reads what is already on your press page first and drops any article you have already covered, so the same story never gets added twice.
- Adds each genuinely new mention to your Webflow press collection as an unpublished draft, carrying the headline, publication name, publish date, and link.
- Sends one Slack message telling your comms team how many new mentions are waiting for review.
What do I need to use this?
- A NewsAPI account. The free plan covers one run per day for non-commercial use.
- A Webflow site with a CMS collection for press or news coverage, with fields for the headline, publication name, date, and article link.
- A Slack workspace and a channel where your comms team will pick up the review.
- Your company name exactly as it appears in coverage, plus an optional list of outlets you want to limit the search to.
How can I customize it?
- Change the timing. Every day at 8am suits most teams, but you can run it weekly if your coverage is lighter.
- Limit the search to a list of outlets you trust. This matters most when your brand name doubles as a common word.
- Skip the Slack message on quiet days, or have new mentions publish straight to the live site instead of waiting for review.
FAQs
Will this publish articles to my website automatically?
My company name is also a common word. Will this fill my page with junk?
How quickly will a new article show up?
Can the same story get added twice?
Do I need a paid NewsAPI plan?
Related templates
When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.
Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.
Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.
Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.
Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.
When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.
Stop hand-updating your press page.
New coverage lands on your site as drafts every morning, ready for a quick review.