TeamNotifications

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

typescript
// When a large order comes in, notify the sales team
await sendivent.send({
  event: 'order.large',
  user: {
    slackChannel: '#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}`
  }
});

// When support ticket is escalated
await sendivent.send({
  event: 'support.escalated',
  user: {
    slackChannel: '#support-urgent'
  },
  payload: {
    ticketId: ticket.id,
    customerName: ticket.customer.name,
    subject: ticket.subject,
    priority: 'high',
    ticketUrl: `https://support.example.com/tickets/${ticket.id}`
  }
});

Implementation steps

1

Connect Slack workspace

One-click OAuth to connect your Slack workspace to Sendivent.

2

Create internal events

Define events like new.signup, order.large, support.escalation with Slack templates.

3

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.

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
sendivent.send({ event: 'order.confirmed', user: { email: 'customer@...' }, ... });

// Team notification
sendivent.send({ event: 'order.large', user: { slackChannel: '#sales' }, ... });

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

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 channel in the user object for each event. Sales alerts go to #sales, support escalations to #support, and so on.

Do Slack notifications support buttons and rich formatting?

Yes, we support Slack Block Kit formatting. Add buttons, links, formatted text, and even interactive elements to your Slack messages.

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.

Ready to get started?

Start sending team notifications in minutes with Sendivent's simple API.