Systeme.io new sale to Slack alert with buyer context

PromptCreate

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.

What does this prompt do?

Listens for the New sale event from Systeme.io and triggers as soon as a purchase comes in.
Looks up the buyer in Systeme.io to pull their tags, course enrollments, and prior orders.
Posts a short, useful Slack message naming the product, the amount, the buyer, and whether this is a first-time customer or a repeat.
Calls out tags that hint at how the buyer found you, so the team knows which channels are converting.

What do I need to use this?

A Systeme.io account where you can create an outgoing webhook for the New sale event.
A Systeme.io API key so the agent can look up buyer details and tags.
A Slack workspace and the channel you want sales posts in, such as #sales.

How can I customize it?

Change which Slack channel the alert posts in, or send to a thread instead of a top-level message.
Tune what the message highlights, for example always show lifetime spend, or only flag repeat buyers.
Filter to only specific products, price tiers, or tag groups so noisy low-ticket sales stay out of the channel.

FAQs

Do I need a paid Systeme.io plan for this to work?

You need any plan that lets you create outgoing webhooks and a public API key. Most Systeme.io paid tiers include both. The free tier does not expose the API.

Will this post for every single sale, including small upsells?

By default it posts every sale that Systeme.io sends. You can tell the agent to filter by minimum amount, product, or tag so the channel only fires on the sales you care about.

Can I send the alert to a private channel instead of a public one?

Yes. Invite the Slack bot to the private channel and point the workflow at that channel name. The post will land there instead.

How does it know whether a buyer is new or returning?

It looks up the contact in Systeme.io and checks their existing tags and order history. If there is prior purchase activity it labels them as a returning customer, otherwise it calls out a first-time buyer.

What if Systeme.io does not have the buyer in contacts yet?

The agent still posts the sale using whatever the webhook included, and notes that this is a brand new contact with no prior history.

Related templates

Review desk for portal forms your team still fills in by hand

Stage a batch of filings overnight, then approve each completed form from a screenshot before anything is ever submitted.

App

Client-by-client cold email pipeline review for agencies

Pick a client and a date range to see sent, replies, meetings booked and the real deal value your cold email produced, campaign by campaign.

App

Audit what Intercom's Fin AI actually resolved before you pay

Review every conversation Fin closed as resolved, judge which ones actually stuck, and see what the gap is worth against your bill.

App

One triage console for every Jira service desk queue

Merge your IT, HR and Facilities queues into one list ranked by SLA time left, then reply, change status and escalate without ever opening Jira.

App

Run your Webflow site translations from one review desk

See every page's translation status at a glance, edit translations side by side with the English, and publish only what your team has actually approved.