Post enriched Systeme.io sales alerts to Slack

By General Input

When a new sale fires in Systeme.io, post a Slack alert that includes the buyer's history, tags, and whether they're new or returning.

Integrations

  • Systeme.io
  • Slack Bot

Type

Agentic Task

Categories

  • Sales
  • Marketing

Build an agent workflow that posts a celebratory but informative new sale alert in our Slack #sales channel whenever a sale comes through in Systeme.io.

Trigger: the workflow should be triggered by Systeme.io's outgoing webhook for the New sale event. The webhook payload includes the order, the product, the amount, and the buyer's email.

What the agent should do on each trigger:

1. Read the buyer's email, the product, and the sale amount from the webhook payload.

2. Use Systeme.io's Get Contact operation to look up that buyer by email. Pull their existing tags, any course or community enrollments, and any prior orders or subscriptions on the contact record. If the buyer is not yet a known contact, treat them as a brand new lead.

3. If any tag IDs come back that need to be resolved to human-readable names, use Systeme.io's List Tags operation to map them. Focus on tags that hint at acquisition source (lead magnet, referral, campaign, funnel) and on tags that indicate product ownership.

4. Decide whether this is a first-time buyer or a repeat customer based on the contact's prior order or subscription history, not on the tags alone.

5. Write a short Slack message (3 to 6 lines) using Slack mrkdwn that includes: the buyer's name or email, the product they bought, the sale amount, a clear label of first-time buyer vs repeat customer, and any relevant tags that hint at how they found us or what else they already own. The tone should be useful for the team, not a generic emoji bot. One small celebration emoji at the start is fine, but the message must lead with substance.

6. Post the message to #sales using the Slack Send a Message operation via the Slack Bot integration so it appears from a shared bot, not from a specific user.

Make the channel name (#sales) and any optional filters (minimum amount, included or excluded products) easy to change at the top of the agent's instructions.

If the Systeme.io lookup fails or the contact is missing, still post the alert using whatever the webhook provided, and clearly note that this is a brand new contact with no prior history.

Related prompts

Explore more prompts
A 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 reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seatsPause marketing emails to escalated customers, then restore them