Documentation Index
Fetch the complete documentation index at: https://docs.newie.app/llms.txt
Use this file to discover all available pages before exploring further.
Why Connect Newie + Slack
For teams who live in Slack and want billing events surfaced where they work. Real-time pings for new subscriptions, successful payments, and overdue invoices keep ops, sales, and finance aware.Common Zaps
Subscription Started → Slack: Send Channel Message Post to a #signups channel when the first subscription payment is complete. Map customer name, service, and amount into the message. Payment Paid → Slack: Send Channel Message Post successful payments in a #revenue or #wins channel for team visibility and weekly reviews. For BECS Direct Debit, this posts after bank confirmation, not at initial payment submission. Payment Overdue → Slack: Send Direct Message DM the account owner directly when a payment goes overdue so it gets handled without spamming a channel. Subscription Paused → Slack: Send Channel Message Post to a #retention channel so a teammate can reach out before the pause becomes a cancellation.What You’ll Need
- Newie account with Zapier connected (Settings → Integrations → Zapier)
- A Slack workspace and permission to install the Zapier app
- The target channels created in advance (private channels need the Zapier app added explicitly)
Setup at a Glance
- In Newie, go to Settings → Integrations → Zapier and copy your API token.
- In Zapier, create a new Zap and choose Newie as the trigger. Pick the trigger event.
- Connect Slack as the action app and authorize.
- Choose Send Channel Message (or Send Direct Message).
- Select the channel/user and write the message, dropping in Newie fields like full_name, service, and amount.
- Test, then enable.
Notes
- For private channels, add the Zapier app to the channel before testing or the Zap will fail with a permissions error.
- For richer Slack messages with buttons or Block Kit, use Slack’s API or a webhook-based workflow. The standard Zapier action is best for text, links, files, and thread replies.
- High-volume accounts can get noisy fast. Consider one channel per trigger type so #signups does not drown out #overdue.
