Brief sales when a Stripe signup looks like an expansion fit

By General Input

When a new Stripe subscription starts, enrich the buyer with Datagma and post a Slack brief to sales only if the account looks like an expansion target.

Integrations

  • Stripe
  • Datagma
  • Slack Bot

Type

Agentic Task

Categories

  • Sales

When a new paid Stripe subscription starts (Stripe webhook on customer.subscription.created), or when a one-time checkout completes (checkout.session.completed), turn the self-serve signup into an account-expansion brief for sales.

Step 1. Pull the customer record from Stripe using Retrieve Customer and Retrieve Subscription to get the buyer's email, name, plan, and starting MRR.

Step 2. Pass the email and its domain into Datagma's Enrich Person or Company action with the personFull and companyFull add-ons. From the response, capture the buyer's title, seniority, and LinkedIn profile, and the company's employee count, industry, country, and website.

Step 3. Decide whether this looks like a strategic expansion target. Treat it as a fit when the company has 50 or more employees AND the buyer title contains director, VP, head, or any C-level keyword AND the email domain is not a freemail or consumer provider (gmail, yahoo, hotmail, outlook, icloud, proton, aol, and similar).

Step 4. If it's a fit, post one tidy message to a sales Slack channel using Slack Bot Send a Message. Include who they are (name, title, LinkedIn), what they bought (plan and starting MRR), the company profile (employee count, industry, country, website), and two or three suggested talking points an AE could use to open an upsell conversation about a team or enterprise plan.

Step 5. If Datagma returns no match (response code 5, or empty company), still post the Slack brief but label it 'low-signal self-serve' so the AE knows to skip unless something in the Stripe details makes it interesting.

Step 6. If the signup is NOT a fit, do not post a new top-level message. Instead, look for yesterday's roll-up message from this workflow in the same Slack channel; if you find one, drop a one-line skip reason as a thread reply on it. If you can't find a prior roll-up, drop silently.

Use the Slack Bot integration (not the user-OAuth one) so the brief comes from a shared bot identity, which is what sales channels expect for automated notifications.

The whole point is to keep the sales channel useful: only real expansion-shaped signups should get a fresh post, everything else gets quietly logged.

Related prompts

Explore more prompts
Let support send one-off Loops emails without an engineerA brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonCustomer lifecycle inspector for Loops, Stripe and PostHogLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client account