What goes into each Slack message, Zap by Zap
Every field the Zaps on this site put into Slack, where it goes in the message and a sample value. Use it as a checklist when you write your own.
- 5/5 on G2
- 4.2 on Capterra
- Building QuoteCloud since 2013
Each Zap maps fields from its QuoteCloud trigger into Slack's Send Channel Message, Send Private Channel Message or Send Direct Message: usually the document's number and title, who acted, an amount, and the owner. Direct messages also use the owner's email, with Find User by Email. Check each trigger's test data for the exact field names.
Last reviewed by the QuoteCloud team
Every field, every Zap
| Slack: Slack | Direction | QuoteCloud: QuoteCloud field | Goes into | Example (sample data) | Note |
|---|---|---|---|---|---|
| Win · Document Signing Complete → Send Channel Message | |||||
| Channel | QuoteCloud to Slack | Fixed in the Zap | #deals |
||
| Message Text | QuoteCloud to Slack | Document title, signers, total, owner | Document field | Signed by everyone: Mossbank Health Partners renewed for 24 months |
|
| First open · Recipient First Viewed Document → Send Direct Message | |||||
| Email (Find User by Email) | QuoteCloud to Slack | Owner email | Slack search | rina.takahashi@example.com |
|
| Message Text | QuoteCloud to Slack | Recipient name, viewed at, document number | Opened: Elena Marsh has opened AD-R-2207 for the first time |
||
| Comment · Document Comment Event → Send Direct Message | |||||
| Filter | QuoteCloud to Slack | Comment event type | Document field | Created |
|
| Message Text | QuoteCloud to Slack | Comment text, author, document number | New comment on PW-R-2291 from Dana Whitcombe |
||
| Approval · Document Review Requested / Accepted → Send Direct Message | |||||
| User | QuoteCloud to Slack | Chosen in the Zap, or the owner's email for Accepted | Hollis Grant |
||
| Message Text | QuoteCloud to Slack | Document number, title, owner, total | Approval needed: PW-R-2291 is waiting for your review |
||
| Payment · Document Part Paid / Paid / Payment Event → Send Private Channel Message | |||||
| Channel | QuoteCloud to Slack | Fixed in the Zap | finance (private) |
||
| Message Text | QuoteCloud to Slack | Amount paid, document number, title | Document field | Payment received: $22,968.00 on AL-ES-0412 |
|
| Filter (Payment Event) | QuoteCloud to Slack | Payment status | Document field | Failed |
|
| Digest · Document Expired / Lost → Digest by Zapier → Send Channel Message | |||||
| Entry | QuoteCloud to Slack | Document number, title, client | Digest entry | FS-1431 · 27 Myrtle Street · Sam & Ivy Okonkwo |
|
| Message Text | QuoteCloud to Slack | The digest's content | This week's expired and lost listing proposals (3) |
||
Field names differ by trigger: check each one's test data in Zapier. All values are sample data.
What makes a message worth reading?
A good post answers three questions in one glance: what happened, to which deal, and who owns it. Put the event first in bold, then the client and the document, then two to four facts. The illustration is Ambergrove's direct message to Rina: one line to say what happened, the document, and a link back.
- Lead with the moment: Signed, Opened, Approval needed, Payment received.
- Name the document number, so anyone can find it in QuoteCloud.
- Keep amounts for private channels and direct messages.
Quote alertsDirect message · to Rina Takahashi
Tuesday 20 October
-
Opened: Elena Marsh has opened AD-R-2207 for the first time.
12-month growth retainer for Kinroy Outdoor Co.
- Recipient
- Elena Marsh
- Opened
- Tue 20 Oct, 2:48 pm
Open AD-R-2207 in QuoteCloud
-
New comment on AD-R-2207 from Daniel Kwan, Kinroy Outdoor Co.:
“Can we start paid search before the summer sale on 26 Dec?”
Reply in QuoteCloud
Illustration with sample data: a generic team chat, not Slack's screen. The Zap writes every word you see in its posts.
Three rules for the fields you map
Only what the channel needs
Whoever is in the channel reads what the Zap posts. Leave out what they don't need, such as client emails and phone numbers.
Only what the test data shows
If a field isn't in the trigger's test data, it won't be there when the Zap runs. Use fixed text, or another step to look it up.
The document stays in QuoteCloud
A message carries the fields you map, not the document. People open QuoteCloud for the full quote, signatures and comments.
Write your first message
QuoteCloud's Zapier app is on the Essentials plan and up. Start a free 14-day trial and test a message in a private channel.
Questions about message fields
Which QuoteCloud fields can go into a Slack message?
Whatever the trigger's test data shows: usually the document's number and title, the recipient or signer, amounts and the owner. Each trigger carries its own fields, so check the test data in Zapier for each Zap before you write its message.
Can the message link to the document?
If the trigger's test data includes a link to the document, map it into the message. If not, name the document number, which anyone on your team can search for in QuoteCloud.
Is the whole document sent to Slack?
No. Only the fields you map into the message go to Slack. The document, its signatures and comments stay in QuoteCloud, which is hosted on AWS with 256-bit encryption.
More on QuoteCloud and Slack
Six use cases with the exact Zapier steps, then how to connect, the limits and the cost.
- Post signed deals to a wins channelWhen every signer has signed, a Zap posts the deal to #deals, and a deposit paid can follow it.
- Message the owner when a client opens or commentsA direct message to the quote's owner on the client's first open and on every new comment.
- Nudge approvers in SlackA document goes into review and the approver hears about it; once approved, the owner knows it's ready to send.
- A weekly digest of expired and lost quotesExpired and lost quotes collected through the week and posted once, on Friday afternoon.
- Post payments to a finance channelDeposits, payments in full and failed payments posted to a private finance channel.
- Keep Slack channels quietChoose the moments that matter, filter by value, send the rest as direct messages or a digest.
- Connect Slack to QuoteCloud, step by stepCheck the plan, connect QuoteCloud and Slack in Zapier, build the first Zap and test it.
- Test and troubleshoot the Slack ZapsTest with a sample quote, then fix the usual problems: no message, the wrong person, blank fields.
- What QuoteCloud with Slack can and can't doWhat the Zaps post, where they stop, Zapier or Make, and what we haven't confirmed yet.
- What the Slack connection costsEssentials and up for Zapier; posting to Slack creates no documents, so no per-document fee.
- FAQAnswers to the questions teams ask before connecting QuoteCloud and Slack.
The right fields, in the right place.
Start a free 14-day trial of QuoteCloud and write Slack messages your team will actually read.