Skip to main content

Setting Up Slack Notifications for Payment & Payroll Activity

A guide for payer organizations This article walks payers through connecting Slack, choosing channels, and troubleshooting common issues.

If your team pays contractors or runs payroll through Rise, you can have key payment and payroll events posted straight into your own Slack channels — so your finance and ops team sees activity where they already work, without logging into Rise to check.

Note: these notifications are for your internal admin team only — contractors and payees are not part of this setup and will continue receiving their usual email and in-app notifications.


What you can send to Slack

Five notification types can be routed to Slack:

Notification

Triggered when…

Invoice created

A contractor submits an invoice to your account

Payment complete

A payment finishes settling

Payment failed

A payment fails

Cash requirement complete

A payroll cash requirement is funded

Cash requirement chargeback

A payroll cash requirement is charged back

Every notification is off by default, nothing posts to Slack until you pick a channel and switch it on.


Before you start

You'll need:

  • Organization Owner or Organization Admin access on your Rise organization — connecting Slack is an org-level action

  • Permission to install apps in your Slack workspace (if your Slack admin restricts installs, get the Rise app approved first)

  • Slack channels already created for the notifications — public or private both work

Any Slack plan works, including the free tier.


Step 1: Connect your Slack workspace

  1. In Rise, switch to your Organization workspace

  2. Go to Admin → Integrations and open Slack

  3. Review the notice describing message contents, then click Connect Slack

  4. Choose your workspace in Slack and approve the requested permissions

  5. You'll return to Rise with a confirmation, and the card will read Connected

⚠️ Always connect from Rise, not from Slack's app directory. Installing directly through Slack skips a security check and Rise won't have a record of the installation. If this happens, disconnect in Rise and reconnect from Admin → Slack.

💡 Note the bot name on the connection card — you'll need it in Step 3 if you use private channels.


Step 2: Choose a channel for each notification

  1. Click Configure channels on the connection card (this opens Notifications → Slack)

  2. Confirm the Account selector at the top matches the account you're configuring

  3. Pick a channel from the dropdown next to the notification you want

  4. The toggle turns on automatically once a channel is selected

Choices save instantly — there's no separate save step.

Public channels work immediately. Private channels need one extra step below.


Step 3: Using a private channel

Slack only lets an app see private channels it's already been added to.

  1. In Slack, open the private channel

  2. Type /invite @[rise-bot-name] and send it (e.g. /invite @rise)

  3. Back in Rise, click Refresh channels

  4. The private channel now appears in the dropdown — select it as usual

Rise also gives you a Copy /invite button next to any selected private channel, so you can paste the exact command into Slack.

image.png

⚠️ Add the bot before looking for the channel — if you check the dropdown first, the channel won't show up at all.


Step 4: Different channels per account (optional)

If your organization runs multiple accounts, each can have its own channel setup:

  1. Use the Account selector on the Slack notifications page to switch accounts

  2. Configure channels for that account the same way

Each account's settings are independent — set your organization default, then override specific accounts as needed.

image.png


Who can manage these settings

Role

Connect/disconnect Slack

Choose channels

Organization Owner

✅

✅ Any account

Organization Admin

✅

✅ Any account

Account Admin

❌

✅ Own account only

All other roles

❌

❌

Channel settings are shared, not personal — any admin who can see an account's settings can change it, and the change applies for everyone.


What's in a Slack message

Each message includes:

  • The notification title and a short summary

  • The amount (for invoices, completed payments, cash requirements) — failed payments show a transaction ID instead

  • Your company and account name, if the notification is account-specific

  • The submitter's name, alias, or email (Invoice created only)

  • A View in Rise link to the relevant page

Because messages can include payment amounts and recipient details, choose channels accordingly — a private finance-team channel is usually the safer default.


Turning notifications off

  • One notification: switch its toggle off. Your channel choice is kept for later.

  • Everything: go to Admin → Slack and click Disconnect. This removes Slack access entirely and stops all messages, but your channel selections are preserved for when you reconnect.

If you disconnect and reconnect, double-check private channels — you may need to re-invite the Rise bot.


Troubleshooting

A private channel isn't in the dropdown

The Rise bot hasn't been added yet — follow Step 3, then click Refresh channels.

A channel I just created isn't listed

The channel list is cached — click Refresh channels.

I set a channel, but nothing's arriving

Check, in order: the toggle is on → the bot is still in the channel (if private) → the Account selector was correct when you saved → wait a minute or two (delivery isn't instant) → check the delivery status shown under the notification row.

Notifications stopped working suddenly

Rise shows a banner on the Slack page if the connection needs attention. If the Rise app was removed from Slack, an Organization Admin needs to reconnect it.

Some notifications I expected aren't listed

Only these five notifications support Slack today. If you see just three, your organization doesn't have payroll enabled — the two cash requirement notifications only appear for payroll-enabled orgs.


Need help?

Contact Rise support from within the app, or reach out to your Account Admin.

Did this answer your question?