Available triggers
What Plutio events can trigger Discord notifications?
Zapier offers multiple Plutio triggers that can send messages to your Discord server. Each trigger represents a business event that might matter to your team or community. You create a separate Zap for each event type, so you control exactly which events produce notifications and where those notifications land.
Invoice paid
Send a message when a client pays an invoice. Include client name, amount, and payment method. Celebrate wins with your team or track revenue in real-time. For agencies that route payment alerts to a #revenue channel, these notifications create a running log of income that the finance team can reference without logging into Plutio.
Proposal signed
Alert your team when a client accepts a proposal. Share client name, project title, and total value. New work is confirmed and visible to everyone who needs to know. Delivery teams watching the channel can start planning resources the moment a proposal closes.
New contact created
Notify when new leads enter your pipeline. See contact name and source. Useful for sales teams tracking lead flow. Agencies monitoring a #leads channel can respond to new inquiries within minutes instead of discovering leads hours later when someone checks Plutio.
Task completed
Post updates when tasks are marked complete. Share task name, project, and who finished it. Keep project channels updated without manual status reports. Routing task completions to project-specific Discord channels gives each team a running log of progress that anyone can review at any time.
Project created
Announce new projects as they start. Share project name, client, and start date. Keeps team aware of incoming work. For agencies where multiple team members might be assigned to new projects, these announcements give everyone visibility into what is coming before formal assignments are made.
Time entry logged
Track billable hours as they are recorded. See duration, project, and description. Useful for agencies monitoring utilization across the team. Managers watching a #time-tracking channel get a real-time view of where hours are going without pulling reports from Plutio.
How do I send notifications to specific Discord channels?
In Zapier, you select which Discord channel receives each notification when setting up your automation.
Discord's Zapier action lets you choose any text channel in your server. Create multiple Zaps to route different event types to different channels. Payment notifications can go to #finances while task completions go to #project-updates.
For project-specific routing, create separate Zaps with filters. Route task completions for Project Alpha to #alpha-updates while Project Beta notifications go to #beta-updates. Zapier's filter step checks the project name before sending. You can also filter by amount (only notify on invoices over $500) or by client (only notify for specific high-priority clients) to keep notification volume manageable.
Recommended setup: create one Zap per notification type, each pointing to the appropriate channel. Separate Zaps keep your automations organized and easy to modify later.
Setting up channel routing
- Step 1: In Zapier, create a new Zap with Plutio as the trigger
- Step 2: Select your trigger event (invoice paid, task completed, etc.)
- Step 3: Add Discord as the action and select "Send Channel Message"
- Step 4: Choose the specific channel from your server
- Step 5: Customize the message format using Plutio data fields
Can I customize how Discord messages look?
Yes. Zapier lets you format Discord messages using markdown and embed data from Plutio dynamically.
When configuring the Discord action in Zapier, you write the message template. Insert Plutio data fields like client name, amount, project title, and task name. Add markdown formatting for bold text, links, and line breaks. The template applies to every notification of that type, so formatting stays consistent across all messages.
Discord supports embeds for richer formatting. Using Zapier's embed options, you can create messages with colored sidebars, thumbnails, and multiple fields. Discord embeds make notifications stand out more than plain text. Embeds are especially useful for payment notifications where you want the amount, client name, and invoice number displayed as separate structured fields rather than a single line of text.
Simple approach: use plain text with key information like "Invoice #1234 paid: $5,000 from Acme Corp". Richer approach: use Discord embeds with structured fields for amount, client, date, and a link to view in Plutio.
Formatting examples
- Plain text: Invoice #Invoice Number paid: $Amount from Client Name
- With markdown: Payment received! Client Name paid $Amount for invoice #Invoice Number
- With link: New proposal signed! [View in Plutio](Proposal URL)
Test your message formatting by running the Zap manually before activating. Zapier sends a sample notification to your Discord channel so you can verify the layout, field placement, and links look correct before notifications start flowing automatically.
How do I connect Discord to Plutio via Zapier?
Create a Zapier account, connect both apps, and build your first automation. The whole process takes about 10 minutes.
You need server administrator permissions on Discord or the "Manage Webhooks" permission to connect Zapier. For Plutio, you need access to the workspace settings. Zapier connects to both using OAuth, so no API keys to copy. If you manage a large Discord server with multiple roles, ensure the Zapier bot role has permission to post in the channels you select during setup.
After connecting, test your Zap before turning it on. Zapier can send a test message to verify everything works. Check that the message appears in the right channel with the expected formatting.
Free Zapier accounts get 100 tasks per month. Each notification counts as one task. If you expect more than 100 notifications monthly, consider Zapier Starter ($19.99/month for 750 tasks).
Step by step
- Step 1: Go to zapier.com and sign in or create an account
- Step 2: Click "Create Zap" and search for Plutio as the trigger app
- Step 3: Select your trigger event and connect your Plutio account
- Step 4: Search for Discord as the action app and select "Send Channel Message"
- Step 5: Connect your Discord account and select the destination channel
- Step 6: Format your message using Plutio data fields, test by sending a sample notification, and turn on your Zap to start receiving Discord notifications
What does this integration cost?
The integration itself is free. Costs depend on your Zapier and Discord plans.
Plutio includes Zapier connectivity on all plans at no extra charge. Discord's free tier works fully with Zapier notifications, including unlimited channel messages and voice channels. Zapier's free tier allows 100 tasks per month with 15-minute update intervals and single-step workflows.
For more notifications or faster updates, Zapier Starter ($19.99/month) gives you 750 tasks with 2-minute updates and multi-step workflows. Discord Nitro ($2.99-$9.99/month) is optional and only affects Discord features like file uploads and custom emoji, not the Zapier integration functionality.
Cost breakdown (as of January 2026): Plutio plan (any tier) + Discord Free + Zapier Free = $0 extra for the integration. Only upgrade Zapier if you need more than 100 notifications monthly or faster than 15-minute delivery.
Plan comparison
- Zapier Free: 100 tasks/month, 15-minute polling, single-step Zaps only
- Zapier Starter: $19.99/month, 750 tasks, 2-minute polling, multi-step Zaps
- Discord Free: Unlimited messages, voice, and servers, which works fully with Zapier
- Discord Nitro Basic: $2.99/month for custom emoji everywhere, bigger uploads, and profile customization (not needed for the Plutio integration)
Should I use Discord or Slack for Plutio notifications?
Use whichever platform your team already uses daily. If you are starting fresh, consider what else you need.
Slack has a native Plutio integration with real-time delivery (seconds, not minutes). Discord requires Zapier with 2-15 minute delays depending on your plan. If notification speed matters for time-sensitive events like payment confirmations, Slack is faster. For events like new project creation where a few minutes of delay does not affect the workflow, Discord works fine.
Discord is built around community features with voice channels, screen sharing, and public servers. If your business involves client communities, Discord might already be part of your stack. Slack is more common in corporate and agency environments where teams need structured channels, thread conversations, and integrations with other business tools.
Quick decision: If you already use Discord for team chat, add Plutio notifications there. If you do not have either yet and want the simplest Plutio setup, choose Slack for the native integration.
Comparison
- Notification speed: Slack (seconds) vs Discord via Zapier (2-15 minutes)
- Setup complexity: Slack (2 minutes, native) vs Discord (10 minutes, Zapier)
- Voice channels: Discord (built-in, free) vs Slack (Huddles, limited on free)
- Cost: Both can be free, but Discord offers more on free tier
What if Discord notifications stop working?
Check your Zap status in Zapier first. Most issues are caused by turned-off Zaps or disconnected accounts.
Zapier shows whether each Zap is on or off, and logs recent runs with success or error status. If a Zap shows errors, the log usually explains what went wrong (permission issues, channel deleted, account disconnected). You can replay failed runs after fixing the issue, so notifications that were missed during an outage can still be sent to Discord.
Discord permissions can change if someone modifies server settings. Verify the Zapier bot still has permission to post in your target channel. If the channel was deleted or renamed, update your Zap configuration. Server administrators who manage channel permissions should keep the Zapier bot's posting access in mind when restructuring channels or adjusting role permissions.
First troubleshooting step: go to Zapier → Zaps → find your Plutio-Discord Zap → check the history tab. Errors there tell you exactly what failed and when.
Common issues and fixes
- Zap turned off: Check Zapier dashboard and turn the Zap back on
- Discord disconnected: Reconnect Discord in Zapier's connected accounts
- Channel not found: Channel was deleted or renamed, so update Zap configuration
- Permission denied: Re-authorize Discord or check server permissions for the Zapier bot
- Zapier task limit: Free tier exhausted, so wait for monthly reset or upgrade plan
