Connect Microsoft Teams to QuoteCloud, step by step
Your first Zap in an afternoon: a signed quote posts to a channel and chats the account manager. Test it in a quiet channel, then point it at the real one.
- 5/5 on G2
- 4.2 on Capterra
- Building QuoteCloud since 2013
You need QuoteCloud's Essentials plan or higher, a Zapier account and a Microsoft account with Teams. In Zapier, pick a QuoteCloud trigger such as Document Signing Complete, connect QuoteCloud, add Microsoft Teams' Send Channel Message, connect the account that will post, map the fields, test it in a test channel and switch it on.
Last reviewed by the QuoteCloud team
Three illustrative Zap editor panels with sample data, taking turns at the front. Step 1: QuoteCloud's Document Signing Complete trigger; the test found QF-P-0417, signed by Martin Thornbury and Rebecca Webb. Step 2: Microsoft Teams' Send Channel Message to Projects › Thornbury & Webb, with the document title and total in the message. Step 3: Create Chat and Send Message to Nina Castell.
How do I connect Microsoft Teams to QuoteCloud?
Seven steps, about an hour the first time. No code.
Check your QuoteCloud plan
QuoteCloud's Zapier app is on Essentials and up. Approval Zaps also need the approval workflow, on Business.
Agree which account posts
With IT, pick the Microsoft account the Zaps connect with, ideally a dedicated one, and add it to the channels you'll post to.
Make a Zap and connect QuoteCloud
In Zapier, create a Zap, choose QuoteCloud and a trigger such as Document Signing Complete, and sign in to QuoteCloud.
Load test data
Let Zapier find a recent document, and check it carries what you'll post: title, reference, client, total.
Add Microsoft Teams
Add Send Channel Message, sign in with the posting account, and pick the team and channel.
Write the message
Map the fields into Message Text, add a mention or importance if you need one, and test it into a test channel.
Point it at the real channel
Switch the channel, run one more test, then turn the Zap on.
Step 1: the trigger, and its test data
Choose QuoteCloud, then the event that starts the Zap. Zapier fetches a recent matching document as test data.
Check it has what you plan to post. If a field is missing, take a test document through the moment again and load fresh data.
What else a signature can start1QuoteCloudTrigger
Document Signing Complete
- Account
- Quillfield IT (QuoteCloud)
- Trigger event
- Document Signing Complete
Test: Found a document: QF-P-0417, signed by Martin Thornbury and Rebecca Webb
Illustration with sample data, not Zapier’s screen.
Step 2: Send Channel Message, mapped
Pick the team and the channel, then write Message Text with fields from step 1: the reference, title, client and total.
To mention someone, put their name between Teams' user tags, such as <user>Nina Castell</user>. Set Importance only on posts that need it.
- Team and Channel: chosen from the posting account's teams
- Message Text: your words plus mapped fields
- Importance: optional
2Microsoft TeamsAction
Send Channel Message
- Team
- Projects
- Channel
- Thornbury & Webb
- Message Text
- Signed: 1. Document title, 1. Total
- Message Text Format
- Markdown
Test: Message posted to Projects › Thornbury & Webb
Illustration with sample data, not Zapier’s screen.
Ready to build your first Zap?
QuoteCloud's Zapier app is on the Essentials plan and up. Start a free 14-day trial and connect Teams this afternoon.
Step 3: a chat to the person who needs it
Add Create Chat and Send Message and pick the team member, or find them first with Find Team Member when it depends on the document's owner.
The chat is between the posting account and that person, so it reads as coming from your automations account.
Chat the owner when a client acts3Microsoft TeamsAction
Create Chat and Send Message
- Team Member(s)
- Nina Castell
- Message Text
- Your SOW 1. Document title is signed
Test: Chat message sent to Nina Castell
Illustration with sample data, not Zapier’s screen.
Can I connect Microsoft Teams through Make instead?
Yes, as a bring-your-own setup. QuoteCloud connects to Make through Make's built-in OAuth connection, and a scenario calls QuoteCloud's API or Zapier endpoints, beside Make's own Microsoft Teams modules for the posting.
There's no ready-made QuoteCloud app on Make, so you design each step yourself. Teams that already run Make, or have a developer, often prefer it; everyone else starts faster with Zapier.
- QuoteCloud's API is on Essentials and up, like the Zapier app.
- Compare the two routes.
Before you start
A QuoteCloud plan
Essentials or higher for the Zapier app; Business for the approval workflow.
A Zapier account
A plan that covers your task volume, and Paths if you'll route by team.
The posting account
A Microsoft account with Teams that belongs to every channel you'll post to.
A test channel
A quiet channel for testing, so the real one only sees real quotes.
Set-up questions
What do I need to connect Microsoft Teams to QuoteCloud?
QuoteCloud's Essentials plan or higher, a Zapier account, and a Microsoft account with Teams that belongs to the channels you'll post to. Approval Zaps also need QuoteCloud's approval workflow, on the Business plan.
Do I need a developer?
No. Zapier is built for people who aren't developers: pick a trigger and an action, map the fields and test. A developer who wants more control can build the same jobs in Make or with QuoteCloud's API, on Essentials and up.
Will my Microsoft 365 admin need to approve anything?
Possibly. Depending on your organisation's settings, connecting Zapier to Microsoft Teams may need an admin's approval, and bot messages and approval cards need the Zapier app installed from the Teams Store. Plain channel messages and chats don't need that app.
How do I test without spamming the team?
Point the Zap at a quiet test channel and use test documents sent to @example.com addresses. When the post looks right, change the channel to the real one, run one more test and switch the Zap on.
More on QuoteCloud and Microsoft Teams
Five use cases with the exact Zapier steps, then how to connect, the IT admin side, the limits and the cost.
- Post quote news to each team's channelSent, first viewed and signed quotes posted to the channel of the team or region that owns them.
- Chat the account owner when a client actsA one-on-one Teams chat to the person who owns the quote when the client opens it or leaves a comment.
- Approval requests for large deals and discountsQuotes over your value or discount limit post an approval request in Teams; approve there or in QuoteCloud.
- Book a kickoff meeting when the quote is signedWhen every signer has signed, Outlook books an online kickoff meeting and the project channel hears.
- File the signed PDF in OneDrive and share it in TeamsThe signed PDF uploaded to OneDrive in the same Zap, with a sharing link posted to the operations channel.
- Microsoft Teams set-up for IT adminsWhich account posts, who can see each channel, the Zapier app in the Teams Store and what reaches Teams.
- What QuoteCloud with Microsoft Teams can and can't doWhat the Zaps post, where they stop, Zapier or Make, and what we haven't confirmed yet.
- What the Microsoft Teams connection costsEssentials and up for Zapier; the Teams Zaps create no documents, so they carry no per-document fee.
- FAQAnswers to the questions teams and IT admins ask before connecting QuoteCloud and Microsoft Teams.
Your first Zap, this afternoon.
Start a free 14-day trial, connect Microsoft Teams in Zapier and post your first signed quote to a test channel.