Weekly vendor watchlist tracker with Slack alerts

Build me a code workflow that maintains a weekly vendor watchlist in Google Sheets and pings Slack only when something material changes.

Trigger: cron, every Monday at 7:00am America/New_York.

Inputs (configurable on the workflow): a list of Ramp Rate vendor slugs to watch (e.g. ["salesforce", "hubspot", "notion"]), the Google Sheets spreadsheet ID and tab name to write into, the Slack channel ID for alerts, and a numeric week-over-week growth threshold (default 5 percentage points).

For each vendor slug, call the ramp-data Get Ramp Rate Vendor Profile operation. Ramp Data is a public, no-auth API, so no credential is needed for it. Read the vendor's primary category, adoption rate, year-over-year growth, new adopter share, competitor switch rate, and rank within its primary category from the response. Handle empty/404 responses gracefully (log and skip that vendor for the week, do not fail the whole run).

Then, for each vendor, append exactly one row to the configured Google Sheet using the google-sheets Append Values operation. Columns, in order: run_date (ISO date in ET), vendor_slug, primary_category, adoption_rate, yoy_growth, new_adopter_share, competitor_switch_rate, category_rank. Use USER_ENTERED value input so dates and percentages format cleanly.

After the sheet write, use google-sheets Get Values (or Batch Get Values) to read the same tab back, find the most recent prior row for each vendor (the row with the largest run_date strictly before today's run_date), and compare against this week's numbers. Flag a vendor if any of: yoy_growth flipped from non-negative to negative, abs(yoy_growth_this_week - yoy_growth_last_week) > threshold (default 5 percentage points), or category_rank changed. Skip vendors with no prior row (first run, or new addition).

If at least one vendor is flagged, send a single Slack message via the slack Send a Message operation to the configured channel. Format it as a short header line (e.g. "Vendor watchlist alerts for {date}") followed by one bullet per flagged vendor naming the vendor, the specific change(s) detected, and the before/after numbers. If nothing is flagged, do not send a message.

This is a deterministic pipeline (fixed list, fixed columns, fixed thresholds), so ship it as a code workflow with discrete nodes, not an agent. Keep retries and error handling defensive: a failure on one vendor should not block the others, and rate-limit/5xx responses from Ramp Data should retry with backoff.