Connect Zendesk Sell to QuoteCloud and test it
One page for the whole set-up: check the plan, connect both apps in Zapier, map the fields, make sure every Zap can find its deal again, and test with sample data before the reps rely on it.
- 5/5 on G2
- 4.2 on Capterra
- Building QuoteCloud since 2013
You need QuoteCloud's Essentials plan or higher, a Zendesk Sell account and a Zapier account. In Zapier, connect QuoteCloud and Zendesk Sell when a Zap asks, build one Zap per job from the recipes on this site, keep the deal's name as the document's title so Find Deal can match it, then test with an @example.com contact.
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 TS-2614, signed by Jess and Arlo Penhaligon. Step 2: Zendesk Sell's Find Deal, on the document title; it found deal 51877. Step 3: Zendesk Sell's Update Deal, setting the stage to Won.
How do I connect Zendesk Sell to QuoteCloud?
Five steps, about as long as one test deal takes.
Check the plan
QuoteCloud's Zapier app needs the Essentials plan or higher. A free trial includes it, so you can build and test first.
Prepare the template
Add data items for what the Zaps fill, such as the Zendesk Sell deal ID and a site address, to the template your reps quote from.
Connect both apps
In Zapier, start a Zap and sign in to QuoteCloud and to Zendesk Sell when it asks. Add Zendesk Support too if you'll hand off to it.
Build one Zap per job
Start with the quote Zap or the won Zap, picking each event by its exact name.
Test, then switch on
Run it with a test deal and an @example.com contact, check both apps, then switch the Zap on.
Step 1: the trigger, and its test data
Every Zap starts from one event. For the won Zap that's QuoteCloud's Document Signing Complete; Zapier pulls a recent signed document as test data.
Read that test data before you map anything: it shows which fields the trigger really carries, such as the document title, the reference and, if your template has them, the data items.
1QuoteCloudTrigger
Document Signing Complete
- Account
- Tallowwood Solar & Storage (QuoteCloud)
- Trigger event
- Document Signing Complete
Test: Found a document: TS-2614, signed by Jess and Arlo Penhaligon
Illustration with sample data, not Zapier’s screen.
How does a Zap find the deal again?
Each Zap runs on its own, so a Zap that starts in QuoteCloud has to find its Zendesk Sell deal. Zendesk Sell's Find Deal searches on a Deal ID or a Deal Name.
So the quote Zap writes the deal's name into the document's title, and its ID into a data item. The return Zaps search on the name, or on the ID when your test data shows the data item. Keep deal names unique, such as client and job, and don't rename the document.
The quote Zap that sets bothData items filled by the Zap
Prepared for- Priya Desai, Orchard Lane ChildcareFrom Zendesk Sell · Contact name
Zendesk Sell deal ID- 48213From Zendesk Sell · Deal ID
Site address- 14 Orchard LaneFrom Zendesk Sell · Site address
Designer- Marcus TeoFrom Zendesk Sell · Owner
Which Zendesk Sell fields go where?
Every field the Zaps on this site pass, one row group per Zap. Each Zap runs one way, so a value that travels both ways is two rows.
| Zendesk Sell: Zendesk Sell field | Direction | QuoteCloud: QuoteCloud field | Goes into | Example (sample data) | Note |
|---|---|---|---|---|---|
| Quote from the deal (Deal Enters New Stage → Create Document) | |||||
| Name (deal) | Zendesk Sell to QuoteCloud | Document Title | Document field | Orchard Lane Childcare · CCTV & access control |
|
| ID (deal) | Zendesk Sell to QuoteCloud | Zendesk Sell deal ID | Data item | 48213 |
|
| Site address (custom field) | Zendesk Sell to QuoteCloud | Site address | Data item | 14 Orchard Lane |
|
| Email, First Name, Last Name (Find Contact) | Zendesk Sell to QuoteCloud | Find or Create Contact | Contact field | priya.desai@example.com |
|
| Task Content (Create Task) | QuoteCloud to Zendesk Sell | Document reference | Task | Check and send HF-SP-0436 |
|
| First viewed (Recipient First Viewed Document → Create Task) | |||||
| Deal Name (Find Deal) | QuoteCloud to Zendesk Sell | Document title | Search value | Halden Property Group · Lakeview windows & carpets |
|
| Hot (Update Deal) | QuoteCloud to Zendesk Sell | A fixed value | Deal field | Yes |
|
| Task Content, Due Date | QuoteCloud to Zendesk Sell | Recipient name, a date | Task | Call Clare, she's opened PF-3218 |
|
| Signed (Document Signing Complete → Update Deal) | |||||
| Deal Name (Find Deal) | QuoteCloud to Zendesk Sell | Document title | Search value | Penhaligon · Solar & battery, 18 Larkspur Lane |
|
| Stage (Update Deal) | QuoteCloud to Zendesk Sell | A fixed value | Deal field | Won |
|
| Content (Create Note) | QuoteCloud to Zendesk Sell | Document reference, signed date | Note | TS-2614 signed in person, 2 of 2 |
|
| Expired and lost (Document Expired / Document Lost) | |||||
| Task Content (Create Task) | QuoteCloud to Zendesk Sell | Document reference | Task | PF-3197 expired unsigned, call Ruth |
|
| Stage (Update Deal) | QuoteCloud to Zendesk Sell | A fixed value | Deal field | Lost |
|
All values are sample data. The hand-off ticket's fields are mapped on the hand-off page.
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 Zendesk Sell with a test deal.
The usual problems, and the fix
Find Deal finds nothing
The document's title no longer matches the deal's name, or the name isn't unique. Keep the title as the Zap wrote it, or search on the deal ID.
Blank data items
The data item's name in the template doesn't match what the Zap maps, or the deal field was empty. Check the trigger's test data first.
The deal didn't move
Stages belong to a pipeline: pick the won stage of the pipeline your deals are in, or the Zap writes a stage the deal can't use.
Two tasks for one quote
Recipient First Viewed Document can fire for each recipient. Add Filter by Zapier if you want one task per quote.
No PDF on the ticket
The PDF link is short-lived. Fetch it with Generate or Fetch Document PDF Link in the same Zap as Create Ticket, never from an earlier run.
Signed in person, nothing happened
Check the quote had a recipient before signing, that every signer signed, and that the Zap was on. Test in-person signing once before go-live.
Can I connect Zendesk Sell through Make instead?
Yes, as a bring-your-own setup. QuoteCloud has no ready-made app or module list on Make. In Make you set up Make's built-in OAuth connection to QuoteCloud, then call QuoteCloud's API or Zapier endpoints from your scenario, beside Make's own Zendesk Sell modules for the deal side.
That suits teams who already run Make and want to design each step themselves. The jobs are the same as the Zaps on this site; API access is on QuoteCloud's Essentials plan and up. Book a demo if you'd like to talk it through.
Before you start
QuoteCloud Essentials
Or higher, or a free trial: the Zapier app and the API are on Essentials and up.
Zendesk Sell access
An account that can read and update the deals, contacts and tasks your Zaps touch.
A Zapier plan
One that runs multi-step Zaps, and Filters or Paths if you use them, at your volume.
A template ready
Your quote template with the data items the quote Zap fills, and a test deal with an @example.com contact.
Set-up questions
Do I need a developer to connect Zendesk Sell to QuoteCloud?
No, not with Zapier. You pick events from lists and map fields, with no code to write. A developer or a Make user is only needed if you build the bring-your-own route in Make, which calls QuoteCloud's API from a scenario.
How does a Zap know which Zendesk Sell deal a quote belongs to?
It searches. The quote Zap writes the deal's name into the document's title and its ID into a data item; a later Zap runs Zendesk Sell's Find Deal on that name, or on the ID if your test data shows the data item. Keep deal names unique.
Can I test the Zaps without emailing real clients?
Yes. Use a test deal whose contact has an @example.com email, sign test quotes yourself, in person or online, and check what lands in Zendesk Sell before you switch each Zap on. Delete the test deal and document afterwards.
Which Zendesk Sell events can I use?
Its Zapier app triggers on new and updated deals, deals entering a stage, new and updated leads and contacts, new notes, tasks and catalogue products. Its actions and searches create or update deals, leads, people, companies, notes and tasks, and find deals, contacts, leads and users.
More on QuoteCloud and Zendesk Sell
Four use cases with the exact Zapier steps, then the limits and the cost.
- Quote from a Zendesk Sell deal on the moveMove a deal to your quote stage from the site and a Zap drafts the quote, with a task waiting for the rep.
- Sign on site, won in Zendesk SellThe client signs in person on the rep's device; a Zap moves the Zendesk Sell deal to won and books the next step.
- Zendesk Sell tasks from quote activityFirst views, expired quotes and lost quotes become tasks, notes and stage changes in the rep's Zendesk Sell list.
- Hand a signed deal from Zendesk Sell to supportWhen the quote is signed, one Zap marks the deal won and opens a Zendesk Support ticket with the signed PDF.
- What QuoteCloud with Zendesk Sell can and can't doWhat the Zaps do, where they stop, Zapier or Make, and what we haven't confirmed yet.
- What the Zendesk Sell connection costsEssentials and up for Zapier, plus a fee per document a Zap or the API creates.
- FAQAnswers to the questions sales teams ask before connecting QuoteCloud and Zendesk Sell.
Connected, mapped, tested.
Start a free 14-day trial of QuoteCloud, connect Zendesk Sell in Zapier and run your first Zap with a test deal.