Customer layoff detection and financial health risk monitoring

Starting promptUse this prompt as a starting point to build your workflow.

Build a workflow that tracks the public layoffs.fyi dataset and flags any of our own customers that appear in it, so account teams get early warning when a customer announces layoffs. Trigger it on a daily cron schedule. On each run: Fetch the full layoffs.fyi dataset. The data lives in a public Airtable shared view that layoffs.fyi embeds, so pull it directly over HTTP — no headless browser needed. (If you'd rather source the data another way, swap this out.) Compare every company in that dataset against our customer list. Start with the customer list as a static file seeded from a CRM export (I planned to use Planhat — use whatever CRM you have), but leave it easy to swap for a live CRM fetch behind a connector later. Normalize company names before comparing (lowercase, strip punctuation and common suffixes like Inc/Ltd/Group) and tag each hit as an exact or fuzzy match, flagging fuzzy ones for human review. Persist the matched results to a named volume so the dashboard can read them. Add a JSON endpoint that serves the latest matched results from the volume, and a customer-facing dashboard webpage that renders the risk view by fetching from that endpoint. Keep all routes private to the space. The workflow should be read-only externally — it only fetches public data and writes to its internal volume; it creates no records or messages. Optionally, extend it to post alerts to Slack (or your team's chat tool) when a new customer match appears. Tools used: layoffs.fyi (Airtable public shared-view JSON API), Planhat, internal named volume storage

New to Tines?Sign up free for Tines 3B Explore Edition

What this prompt builds

This workflow monitors the public layoffs. fyi dataset daily and automatically flags any customer appearing in it, giving account teams early warning of potential churn risk or automation opportunities. It compares company names from the dataset against a CRM customer list, normalizes matches, and surfaces flagged accounts through a dashboard and optional Slack alerts.

The problem

Account teams at B2B companies often learn too late when their customers announce layoffs — a critical signal that a renewal may be at risk or that the customer could benefit from cost-saving automation. Manually tracking layoff news across hundreds of customers is impractical, and CRM data alone doesn't surface these external financial health signals. This workflow solves that by automatically monitoring the public layoffs.fyi dataset every day and flagging any customer that appears in it, so AEs and CSMs get early warning and can act before a renewal slips or an upsell opportunity is missed. Note that the customer list is sample data, and in a production example would fetch directly from the user's customer database.

Solution and impact

Account teams receive proactive, automated alerts whenever a customer announces layoffs, giving them days or weeks of lead time to reach out, assess renewal risk, or pitch automation solutions that reduce headcount pressure. The workflow delivers a live dashboard view of flagged customers and optional Slack notifications, eliminating manual news-monitoring and ensuring no at-risk account goes unnoticed. Teams using it report faster response times to churn signals and more timely, relevant conversations with customers facing financial pressure.