Stripe Automation: Payments to Invoices, Sheets and Slack

What to automate around payments

Workflow	Trigger	Actions
Payment log	Payment succeeded	Add row to Sheets / accounting tool
Sales alert	Checkout completed	Slack message with amount and product
Invoice/receipt	Payment succeeded	Generate PDF invoice, email customer
Failed payment	Invoice payment failed	Alert team, email customer a payment link
Onboarding	New subscription	Create account, add to Mailchimp, create project
Churn signal	Subscription canceled	Notify owner, add to win-back sequence

The example: payment → Sheet + Slack + invoice email

In Zapier

1. Trigger: Stripe → New Payment (or New Charge).
2. Formatter: convert amount from cents to currency (Stripe sends 4999 for $49.99).
3. Google Sheets → Create Spreadsheet Row.
4. Slack → Send Channel Message: 💰 {{customer}} paid {{amount}}.
5. Google Docs → Create Document from Template → email as PDF (see Docs automation).

In Make

1. Stripe → Watch Events, event type charge.succeeded or checkout.session.completed (instant webhook).
2. Use {{amount / 100}} in mapping to convert cents.
3. Google Sheets → Add a Row, Slack → Create a Message, document and email modules.

In n8n

1. Stripe Trigger, events checkout.session.completed and invoice.payment_failed.
2. Switch on event type.
3. Success branch: Edit Fields ({{ $json.data.object.amount_total / 100 }}) → Google Sheets → Slack → document generation.
4. Failure branch: Slack alert → Gmail with the hosted invoice URL.

Use Stripe's own features first

Stripe can already email receipts and send hosted invoices. Automate around it rather than rebuilding it: log data, alert people, and connect other systems.

Comparison

	Zapier	Make	n8n
Instant events	Yes	Yes	Yes
Multiple event types in one flow	Paths or separate Zaps	Router	Switch
Cost for 1,000 payments, 4 steps	~4,000 tasks	~5,000 credits	~1,000 executions or $0

Tips

• Use test mode keys while building; switch to live keys only after testing.
• Make automations idempotent: store the Stripe event ID and skip duplicates, because webhooks can be retried.
• Never put secret keys in Slack messages or logs.

Related

• Mailchimp automation
• CRM automation