Can I celebrate only the big ones?

Filter on mrr or plan so a #wins channel sees the deals worth celebrating, while everything still streams to your warehouse.

Who owns the account?

enrich.entity attaches the account owner and seat count in flight, so the alert names a person, not just an id.

How is this different from a successful payment?

A subscription.created fires once when the plan starts; payment.succeeded fires every billing cycle. Track both for different signals.

ingestlayer/recipes/v0.4

Track new subscriptions in Slack

Know the second a customer starts paying — which plan, how much, monthly or annual — so revenue moments reach the team while they still feel like wins.

01source

sourcesdk.eventTypeScript SDK

matchsubscription.created

02pipeline · 2 steps

01ENRenrich.entitycustomer → company · seats · owner
02CTLfilter.matchannual or scale-plan only

03destinations · 1

toslackSlack
channel#alerts

the event

You emit subscription.created with this shape. The TypeScript SDK keeps the call type-safe, and the event is stored whole — so every field below is available to the pipeline by name.

customer_idstring
planstringpro | scale
mrrnumberminor units
intervalstringmonth | year
trialbooleanconverted from trial

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit subscription.created

import { ingest } from "@ingestlayer/sdk";

await ingest("subscription.created", {
  customer_id: sub.customer,
  plan:        sub.plan.nickname,
  mrr:         sub.plan.amount,
  interval:    sub.plan.interval,
  trial:       sub.trial_end != null,
}, {
  idempotencyKey: sub.id,
});

route it to Slack

Post to any channel in your workspace. Connect once with OAuth, pick the channel per pipeline.

01
connect your workspace
Authorize the ingestlayer Slack app over OAuth from the destinations page. We hold only a channel-scoped bot token, in-region, in the same KMS as your other credentials.
02
pick a channel
Choose any public channel, or invite the bot to a private one. The channel is set per pipeline, so different events can land in different places.
03
map the message
Reference event fields with $event.* in the message template. The default renders a titled block with the event name and its key fields.

in slackdelivered

┌─ #alerts ──────────────────────────────┐
│  ingestlayer  APP                       │
│  user.signed_up                         │
│  email   ada@acme.com                   │
│  plan    pro                            │
│  source  marketing-site                 │
└─────────────────────────────────────────┘

notes

Slack rate-limits to roughly one message per second per channel; bursts are queued and retried, never dropped.
The bot must be a member of a private channel before it can post there — invite it explicitly.
Block Kit caps a message at 50 blocks and 3000 characters per text field; oversized events are truncated with a link to the full payload.

questions

Can I celebrate only the big ones?: Filter on mrr or plan so a #wins channel sees the deals worth celebrating, while everything still streams to your warehouse.
Who owns the account?: enrich.entity attaches the account owner and seat count in flight, so the alert names a person, not just an id.
How is this different from a successful payment?: A subscription.created fires once when the plan starts; payment.succeeded fires every billing cycle. Track both for different signals.

build this pipeline or read the quickstart →