Slack brief for multi-threading new Stripe customers

Build me an agent workflow that fires every time a brand-new paying customer lands in Stripe and arms our CS lead to multi-thread the account before the relationship is one buyer deep.

Trigger: a Stripe webhook for invoice.payment_succeeded. Only continue if this is the customer's first successful payment (skip renewals and any subsequent billing cycle) so the workflow runs exactly once per customer, not every month. Read the customer ID off the invoice and use Stripe's Retrieve Customer to pull the full customer object.

From that customer, take the email address and grab the root domain (everything after the @). If the domain is a personal provider like gmail.com, outlook.com, yahoo.com, icloud.com, or hotmail.com, stop and post a short Slack note saying we cannot enrich a personal-email customer, and skip the rest. Otherwise, also grab the customer's name, description, and any website field if Stripe has one.

Then call Website Contacts Scraper's Scrape Contacts on that root domain. We want every public email, every phone number, and every social profile link the scraper exposes (LinkedIn, Twitter/X, Instagram, YouTube, TikTok, Facebook, and any others returned).

Now build a customer-expansion brief from what came back. Rank the emails by role pattern: founder@, ceo@, coo@, cto@, head-of-*@, vp-*@, ops@, revops@, and sales@ outrank generic info@, hello@, contact@, support@, and team@. For each ranked contact, label the role you inferred from the email pattern. Flag a likely economic buyer (founder/CEO/CFO-style inboxes) and a likely champion (ops/product/operator-style inboxes) where you can tell them apart. List every social handle so the CS lead can warm up the account on LinkedIn or send a quick comment on a recent post. If the scraper returned nothing usable, say so plainly instead of fabricating contacts.

Post the brief as a Slack message via Send a Message. The recipient should be configurable (a DM to the CS lead by default, but easy to switch to a shared CS channel). The message should lead with the customer name, then the ranked expansion contacts, then the social handles, then the champion-vs-economic-buyer flags, then a one-line suggestion of who to reach out to first and why.

Important: this fires once per customer, never on renewals or plan changes. Treat any obvious failures (personal email domain, scraper returns empty, missing website) as a successful but short Slack message rather than a hard error, so the CS lead always hears something when a new customer pays.