What you'll build
By the end of this article, you'll have a Zap that:
Triggers when a Vinyl summary email arrives
Posts client meeting summaries to a designated Teams channel (e.g. a client-updates or meeting-notes channel)
Posts internal meeting summaries to your team channel
Does nothing for private meetings
This article assumes you already have a three-path Zap set up: one that triggers from your Vinyl summary emails (Email by Zapier) and has an AI step that classifies each meeting as Client, Internal or Private. The finished structure is shown further down.
What you'll need
A Zapier account (Starter plan or above)
Microsoft Teams connected to Zapier — go to My Apps in Zapier, search for Microsoft Teams, and sign in with your Microsoft 365 account
At least one Teams channel to post to
Vinyl summary emails switched on. By default, they go to the meeting owner, only for meetings they attended, and only when Email me summaries is on in Settings › You › Summaries and email. You can switch it to cover all meetings you own.
A note on client data
Anything you forward to Zapier, an AI service or Teams leaves Vinyl's sharing and permission controls. The "Private" label in this Zap comes from the AI step's best guess, not from Vinyl's own meeting permissions. It's worth checking your firm's policy before posting client meeting content to shared channels.
Setting up the Client path (Path A)
Inside your Path A — Client branch, add a Microsoft Teams → Send Channel Message step.
Set Team to your Microsoft 365 team.
Set Channel to wherever your client-facing updates live (e.g. "Client Updates", "Meeting Notes", or a general channel your team monitors).
Set the Message body. Here's a recommended format you can copy and adapt:
📋 **Client meeting summary****Meeting:** [Subject field from email]**Recorded by:** Vinyl[Body Plain field from email]
The Body Plain field contains the Vinyl summary as plain text, with the meeting details and the sections Summary, Key discussion points, Action items and Next steps. It also includes links back to Vinyl, which you may want to strip out before posting. Teams renders line breaks correctly, so the message will be readable without extra formatting.
Setting up the Internal path (Path B)
Inside your Path B — Internal branch, add another Microsoft Teams → Send Channel Message step.
Set Team to your Microsoft 365 team.
Set Channel to your internal team channel (e.g. "General" or "Team Updates").
Use the same message format as above, or a simpler version — internal messages don't need as much context.
Tip: Post to a client-specific channel
If your firm uses a separate Teams channel per client (e.g. "Smith & Associates", "Jones Family Trust"), you can make the routing smarter. Add an AI step before the Teams step to extract the client name, then use Microsoft Teams → Find Public Channels to search for a matching channel by name.
1. AI / ChatGPT — Extract client name2. Microsoft Teams — Find Public Channels (search by client name)3. Filter — Stop if no channel found4. Microsoft Teams — Send Channel Message (to the matched channel)
This means each client's meeting notes automatically land in their own dedicated channel, with no manual routing required. Note that "Find Public Channels" only searches public channels — if your client channels are private, you'll need to hardcode the channel name or use "Get Channel by ID" with a known channel ID instead.
Tip: Send a direct message instead of a channel post
If you'd rather receive a private notification than post to a shared channel, use Microsoft Teams → Send Chat Message instead. Set the recipient to yourself (or a specific team member) and map in the same message content.
Finished Zap structure
1. Email by Zapier — New Inbound Email (trigger)2. AI / ChatGPT — Classify meeting (CLIENT / INTERNAL / PRIVATE)3. Paths by Zapier ├─ Path A: CLIENT │ 4. Microsoft Teams — Send Channel Message (client updates channel) │ OR: Find Public Channels by name → Send Channel Message ├─ Path B: INTERNAL │ 4. Microsoft Teams — Send Channel Message (team channel) └─ Path C: PRIVATE (no action)
Troubleshooting
Teams not appearing in Zapier: Make sure you've signed in to Microsoft Teams in Zapier with an account that has access to the teams and channels you want to post to. If your organisation uses conditional access policies, you may need an admin to approve the Zapier connection.
Message posts but is hard to read: Teams renders markdown in some contexts but not all. If the message looks unformatted, try removing the asterisks from the template above and using plain text only.
Find Public Channels returns no results: This search only covers public channels. If client channels are private, use "Get Channel by ID" with the channel's ID (found in Teams under the channel's link/settings) instead of searching by name.
What's next?
If your firm also uses Slack, see Post meeting summaries to Slack. Or read Practical Zapier workflows for accounting firms for the complete picture of what's possible when you combine these Zaps.