Popular automations
What events can you send to Teams?
Plutio automations trigger on almost any business event, so you choose which ones post to Teams and where they go. Each card includes context about what happened and a link back to the item in Plutio.
Invoice paid
Route payment cards to a revenue or finance channel. The card shows client name, invoice amount, invoice number, and payment method the moment payment arrives. Finance teams get an ambient awareness of cash flow without running reports, and agencies celebrate wins in real time.
Proposal signed
Post signed proposals to a wins or sales channel. The card includes client name, proposal title, and total value, so the team knows a new engagement just started and delivery can begin planning kickoff.
New lead or contact
Send new lead alerts to an inbound channel. Response speed matters in sales, and having leads land in Teams within seconds of form submission means a team member can reply before the lead has moved on to a competitor. The card includes contact name, email, and source (form, manual entry, API).
Task completed
Route task completion cards to project-specific channels. Project managers tracking deliverables across client accounts get a live progress feed per project without asking for status over email. The card includes task name, project name, and who marked the task complete.
Booking confirmed
Notify the assigned team member when a client books a meeting through a Plutio scheduler. The card shows client name, meeting type, and scheduled date, so freelancers know about upcoming meetings without constantly refreshing their calendar.
Invoice overdue
When an invoice passes its due date, a card posts to the finance channel with the client name, amount owed, and days overdue. Agencies that previously relied on monthly reviews to catch late payments now see overdue invoices the day they cross the due date, which speeds up collections.
How do I send Plutio events to Teams with a Workflow?
Create a Teams Workflow that accepts an HTTP POST, copy the webhook URL, then build a Plutio automation that triggers on your chosen event and adds an API call action that POSTs a JSON card to the Workflow URL.
Microsoft Teams Workflows replaced the older Office 365 Connectors as the supported way to receive incoming webhook messages in 2025. A Workflow is tied to a specific channel and accepts an Adaptive Card payload over HTTPS. Plutio's automation builder has a generic API call action that lets you POST any JSON payload to any URL, so you can wire Plutio events to Teams without Zapier, Make, or any third-party service in the middle.
Because both sides run inside tools your team already has (Microsoft 365 on their side, Plutio's automation builder on ours), there's no subscription to add and no polling delay. Cards reach Teams within seconds of firing in Plutio.
The Workflow path is free on both sides: Teams Workflows come with every Microsoft 365 business subscription, and Plutio's automation builder runs on every Plutio plan. The only real limit is Plutio's monthly trigger allowance, which starts at 1,000 on Core and scales up on Pro.
Fields you can include in the Teams card
- Client name pulled from the Plutio entity so the team knows who the event relates to
- Entity amount (invoice total, proposal value) pulled from the triggering record
- View in Plutio action button linking back to the item for one-click access
- Status or stage (paid, signed, completed) for quick visual parsing
- Assigned team member so the responsible person gets @-mentioned in the channel
How do I send Plutio events to Teams through Zapier?
Create a Zapier or Make workflow with Plutio as the trigger (via webhook) and Microsoft Teams as the action, then pick the channel, message format, and any conditional routing rules on the automation platform side.
The Zapier or Make path makes sense when you need to route events to different channels based on field values. Workflows on either platform filter on invoice amount (under $500 goes to one channel, over $500 goes to another), on project name (Acme project events route to #proj-acme), or on assigned team member (route direct messages to the right person). Plutio's native automation builder supports conditions as well, but complex multi-branch routing is easier to build visually in Zapier or Make.
Both platforms have a native Microsoft Teams module, so once the Plutio webhook fires, you pick the Teams channel or chat and map the event fields into the card template through dropdown menus. No coding, no JSON payload hand-crafting.
Zapier Free covers 100 runs per month with 15-minute checks. Make Free covers 1,000 operations per month with 15-minute checks. For teams sending fewer than 100 Teams cards per month, either free tier handles the workload without an upgrade.
Step by step
- Step 1: In Plutio Settings, generate an API key and enable the webhooks for events you want to listen for (invoice paid, proposal signed, task completed).
- Step 2: In Zapier or Make, create a workflow with Webhooks as the trigger and paste the Plutio webhook URL.
- Step 3: Add Microsoft Teams as the action app and pick "Send Channel Message" or "Send Chat Message."
- Step 4: Map Plutio fields to the Teams message template (client name, amount, link).
- Step 5: Test with a real Plutio event, then turn the workflow on.
How do I route different events to different Teams channels?
Build one Plutio automation per channel-event pair. Payments to a revenue channel, leads to sales, task completions to project-specific channels. Each automation has its own trigger filters and its own destination URL.
Separate automations per channel keep routing readable. When you need to change where payments go, you update one automation instead of hunting through branches inside a single mega-workflow. For teams with 3-5 channels, this keeps Plutio's automation list short and clear.
If you need more complex routing (same event type splitting across 5+ channels based on custom field values), the Zapier or Make path is a better fit. Their visual builders handle multi-branch logic with less effort than building many separate Plutio automations.
Common routing patterns: invoice paid and proposal signed go to #revenue or #payments, new leads go to #sales or #inbound, task completions go to project-specific channels, booking confirmations go to the assigned team member's chat.
Setting up routing
- Step 1: Create one Teams Workflow per destination channel and copy each webhook URL.
- Step 2: Build one Plutio automation per event-channel pair with the right trigger, any filters, and an API call action pointing to the matching Teams webhook URL.
- Step 3: For private channels, create the Workflow from inside the private channel's settings so the webhook is scoped correctly.
- Step 4: Test each automation with a real event and adjust the card template until the message reads clearly in the target channel.
How much does Plutio + Microsoft Teams cost?
Microsoft Teams Workflows come free with every Microsoft 365 business subscription. Plutio's automation builder is free on every Plutio plan. The direct Workflow path costs nothing beyond your existing subscriptions. Zapier and Make both offer free tiers if you want their routing features.
Microsoft 365 pricing
Microsoft 365 Business Basic costs $6 per user per month and includes Teams with Workflows. Business Standard costs $12.50 per user per month and adds desktop Office apps. Business Premium costs $22 per user per month and adds Intune device management. Teams and Workflows are included in all three tiers, so any business plan works with the integration.
Zapier or Make pricing
Zapier Free covers 100 runs per month with 15-minute checks. Paid plans start at $29.99 per month for 750 runs and 2-minute checks. Make Free covers 1,000 operations per month with 15-minute checks. Paid plans start at $10.59 per month for 10,000 operations. For most freelancers, either free tier handles Teams routing without an upgrade.
Plutio pricing
Plutio offers a 7-day free trial with full access to the automation builder, API, and webhooks. After that, Core costs $19 per month and Pro for teams costs $49 per month. Trigger allowances start at 1,000 per month on Core and scale up on Pro.
Bottom line: A freelancer on Plutio Core ($19/month) plus Microsoft 365 Business Basic ($6/user/month) pays about $25 per month per user for real-time Plutio event cards in Teams. Add Zapier Free or Make Free only if you want their visual routing rules.
What if Teams cards stop arriving?
Check the Plutio automation run history first. The log shows which runs fired, which succeeded, and what error Teams returned if any of them failed.
Most delivery problems come from an expired Teams Workflow, a deleted channel, or a payload that no longer matches Teams' expected Adaptive Card format. Plutio's automation log shows the exact HTTP response from Teams, so you can tell immediately whether the issue is on Plutio's side or Microsoft's side.
If you are using Zapier or Make instead, check their task history. Both platforms surface the Teams error message and let you re-run failed runs once the root cause is fixed.
Common issues and fixes
- Workflow returned 404: The Teams Workflow was deleted or the channel was removed. Create a new Workflow, copy the fresh URL, and update the Plutio automation.
- "Invalid card format" error: The JSON sent by Plutio no longer matches Teams' Adaptive Card schema. Check the payload structure in the automation's API call action against Microsoft's Adaptive Card documentation.
- Workflow returned 401 or 403: Microsoft 365 admin policies changed or the user who created the Workflow lost access. Ask a workspace admin to recreate the Workflow from an active account.
- Automation silently disabled: Plutio disables automations after repeated failures to protect your trigger allowance. Fix the root cause in the API call action, then reactivate the automation.
- Private channel not receiving: Teams Workflows are scoped to a specific channel at creation time. Create the Workflow from inside the private channel's settings rather than a public one.
Disabling or deleting an automation does not delete any Plutio data. Previously posted Teams cards stay in the channel history. You can regenerate a Workflow URL at any time, paste it into the automation, and resume sending cards.
