Team Notifications
Keep your team in the loop with real-time Slack alerts for important product events.
Instant Slack alerts
New signup? Large order? Support escalation? Your team knows immediately in Slack.
Channel routing
Sales events to #sales, support escalations to #support, engineering alerts to #ops.
Rich formatting
Slack messages with buttons, links, and formatted data — not just plain text.
Same API, different channel
Use the same Sendivent API for customer emails and team Slack notifications.
Actionable alerts
Include links to dashboards, customer profiles, or admin actions right in the message.
Reduce noise
Configure which events go to Slack vs. just logging. Keep signal high.
How it works
// When a large order comes in, notify the sales team
await sendivent
.event('order.large')
.channel('slack')
.to('#sales-alerts')
.payload({
customerName: order.customer.name,
orderTotal: formatCurrency(order.total),
itemCount: order.items.length,
customerUrl: `https://admin.example.com/customers/${order.customerId}`,
orderUrl: `https://admin.example.com/orders/${order.id}`
})
.send();
// When support ticket is escalated
await sendivent
.event('support.escalated')
.channel('slack')
.to('#support-urgent')
.payload({
ticketId: ticket.id,
customerName: ticket.customer.name,
subject: ticket.subject,
priority: 'high',
ticketUrl: `https://support.example.com/tickets/${ticket.id}`
})
.send();
Implementation steps
Connect Slack workspace
One-click OAuth to connect your Slack workspace to Sendivent.
Create internal events
Define events like new.signup, order.large, support.escalation with Slack templates.
Trigger from your backend
Same API as customer notifications — just different event names and channel config.
Why Slack for internal alerts?
Your team lives in Slack. When something important happens in your product, they should know immediately — without checking dashboards or waiting for daily reports. Slack notifications for internal events are the fastest way to do that.
Common team notification use cases:
- New signups — especially from target companies or high-value leads
- Large orders — sales team wants to know about big deals
- Support escalations — urgent tickets need immediate attention
- System alerts — errors, outages, or unusual patterns
- Milestones — 1000th customer, revenue goals, etc.
Same API, different audience
The power of Sendivent is using one API for everything:
// Customer notification
await sendivent.event('order.confirmed').to({ email: 'customer@...' }).payload({...}).send();
// Team notification
await sendivent.event('order.large').channel('slack').to('#sales').payload({...}).send();
Same patterns, same templates system, same delivery guarantees — just different channels.
Slack message best practices
- Include actionable links — don't make people search for context
- Use formatting — headers, bullet points, code blocks for readability
- Add buttons — "View Customer", "Respond", "Assign to Me"
- Keep it scannable — busy teams skim, make the important info obvious
Slack Template Example
Sendivent uses Slack Block Kit for rich formatting:
{
"blocks": [
{
"type": "header",
"text": { "type": "plain_text", "text": "🎉 Large Order Received!" }
},
{
"type": "section",
"fields": [
{ "type": "mrkdwn", "text": "*Customer:*\n{{payload.customerName}}" },
{ "type": "mrkdwn", "text": "*Amount:*\n{{payload.orderTotal}}" },
{ "type": "mrkdwn", "text": "*Items:*\n{{payload.itemCount}} items" }
]
},
{
"type": "actions",
"elements": [
{
"type": "button",
"text": { "type": "plain_text", "text": "View Order" },
"url": "{{payload.orderUrl}}"
},
{
"type": "button",
"text": { "type": "plain_text", "text": "View Customer" },
"url": "{{payload.customerUrl}}"
}
]
}
]
}
The same Handlebars variables work in Slack templates — just embedded in Block Kit JSON.
Keep your team in the loop automatically. Create a free account and route your internal alerts to Slack without building webhook infrastructure.
Frequently asked questions
How do I connect Sendivent to Slack?
Use our one-click OAuth flow to connect your Slack workspace. Once connected, you can send to any channel your Slack app has access to.
Can I send to different Slack channels for different events?
Yes, specify the Slack channel directly (e.g., `#sales`) or configure it per event. Sales alerts go to #sales, support escalations to #support, and so on.
Do Slack notifications support buttons and rich formatting?
Yes, Slack templates use Block Kit formatting. Add buttons, links, and formatted text to your messages. You define the Block Kit structure in the template and we inject your payload data.
Can I use the same API for customer emails and team Slack alerts?
Yes, that's the power of Sendivent. Same API, same event system — just different channel configuration per event.
Related content
Compare Sendivent and Intercom for notifications. See how Sendivent's event-driven notifications compare to Intercom's customer messaging platform.
Read moreBuild beautiful notification templates with Handlebars, preview across channels, and personalize content for every user. No code changes needed to update templates.
Read moreSend order confirmations, shipping updates, and delivery notifications via email and SMS with Sendivent's multi-channel API.
Read moreCompare Sendivent and Customer.io for product notifications. See how Sendivent's developer-first approach compares to Customer.io's marketing automation platform.
Read moreStill relying only on email for product notifications? Learn why multi-channel matters and when to expand beyond the inbox.
Read moreCompare Sendivent and Braze for product notifications. See how Sendivent's simple API compares to Braze's enterprise customer engagement platform.
Read moreReadytogetstarted?
Start sending team notifications in minutes with Sendivent's simple API.