How do I keep the channel quiet?

Filter on amount so routine charges pass silently to the warehouse, while only large payments reach a human.

Can I split by currency?

Branch on the currency field to route EU and US revenue to different channels or owners.

Will retries double-count?

No. The charge id as idempotencyKey collapses retries, so one cleared payment is one event.

Track successful payments in Slack

Surface the payments that matter — a big invoice cleared, an annual renewed — without drowning the channel in every routine charge.

01source

sourcesdk.eventTypeScript SDK

matchpayment.succeeded

02pipeline · 2 steps

01CTLfilter.matchamount ≥ 500.00 only
02ENRenrich.entitycustomer → plan · account owner

03destinations · 1

toslackSlack
channel#alerts

the event

You emit payment.succeeded 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
amountnumberminor units
currencystringISO 4217
invoice_idstring
methodstringcard | sepa | invoice

emit it

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

emit payment.succeeded

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

await ingest("payment.succeeded", {
  customer_id: charge.customer,
  amount:      charge.amount,
  currency:    charge.currency,
  invoice_id:  charge.invoice,
  method:      charge.payment_method_type,
}, {
  idempotencyKey: charge.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

How do I keep the channel quiet?: Filter on amount so routine charges pass silently to the warehouse, while only large payments reach a human.
Can I split by currency?: Branch on the currency field to route EU and US revenue to different channels or owners.
Will retries double-count?: No. The charge id as idempotencyKey collapses retries, so one cleared payment is one event.

build this pipeline or read the quickstart →