Founders watching launch day
A single #launch channel receives New purchase and Upsell accepted posts, so a small team sees sales and upsell uptake as the doors open without refreshing the Stripe dashboard.
Native integration
Your team sees each Stripe sale, renewal, upsell and refund in a Slack channel, and failed automations are reported there as well.
No credit card required. No coding required.
SlackPlandalf connects them with a native Slack app, not a direct Stripe-to-Slack feed. Payments taken through a Plandalf checkout on your Stripe account can post to a channel through the Slack notifications recipe or a Send Slack Message step. Plandalf can also post failed-automation alerts to Slack. It covers Plandalf invoices, not every charge on the Stripe account.
| Event | From and to | Through | What happens |
|---|---|---|---|
| New purchase | Plandalf (paid via Stripe) → Slack | Native step | The Slack notifications recipe posts when a customer completes a checkout. You choose the channel and can edit the message text. |
| Subscription / invoice paid | Plandalf (paid via Stripe) → Slack | Native step | Fires on any paid invoice, so renewals reach the channel too, which is how a team notices a plan quietly continuing. |
| Upsell accepted | Plandalf (paid via Stripe) → Slack | Native step | Posts when a customer pays for the offer shown after the main checkout, which lets you watch whether the add-on is selling. |
| Refund | Stripe → Slack | Native step | Posts for every refund that succeeds in Stripe, partial ones included, and shows the amount refunded. A refund made in the Stripe dashboard counts. Voided invoices do not post. |
| Failed automation | Plandalf → Slack | Native step | A switch on the Slack connection sends the same failure alerts that go to your notification emails to a channel you pick, at most once every 15 minutes per sequence. |
You need a Stripe account connected to Plandalf with a published checkout, and permission to add apps to your Slack workspace.
In Plandalf open Automation, then Marketplace, and click Connect on Slack. Click Add to Slack, check the workspace named in the top-right of the Slack window, and click Allow. There is no API key. Plandalf shows Slack connected.
Under Automation, then Templates, open Slack notifications in the Recipes section and check the Slack workspace shown is the one you connected.
Choose from New purchase, Subscription / invoice paid, Refund and Upsell accepted. For each, pick a Channel such as #sales for purchases and #support for refunds, edit the Message if you like and click Save.
Public channels work at once. For a private channel, open it in Slack, go to its details, choose Integrations and add the Plandalf app, then reopen the channel list in Plandalf.
In a sequence, add Slack, Send Slack Message and pick a Channel. In a sequence that starts on Invoice Refunded, use {{trigger.refund_amount_formatted}} for this refund and {{trigger.refunded_total_formatted}} for the total refunded so far.
Under Automation, then My apps, open the Slack connection, switch on Post automation failures to Slack, choose a Failure alert channel and click Save Changes. Failed automation notifications must also be on under Settings, then Notifications.
A step test posts a real message to the real channel, so warn the channel first. Test purchases skip automations by default, so confirm the setup with a step test and look at the Events view for each run.
A single #launch channel receives New purchase and Upsell accepted posts, so a small team sees sales and upsell uptake as the doors open without refreshing the Stripe dashboard.
Refund posts go to #support with the amount refunded, so the person who answers email knows a refund went through in Stripe before the customer writes in.
If sequences grant course or community access, the failure alert channel shows when a step could not run. That tells you a paying customer may be waiting without access.
not_in_channel or channel_not_found points to the same cause.status: failed with Slack's error code, such as is_archived or invalid_auth. Read the run in the Events view.Checked October 26, 2026 against Plandalf's own setup guides.