Getting started with QuoteCloud

Connect Zendesk to QuoteCloud, step by step

Zendesk connects to QuoteCloud through Zapier, one Zap per job. Here's how to set up the first one, find the ticket again from QuoteCloud, choose internal or public, and where Make fits.

Start free 14-day trial Book a demo

Zendesk connects to QuoteCloud through QuoteCloud's Zapier app, on Essentials and up. In Zapier, create a Zap, pick a trigger such as QuoteCloud's Document Signing Complete or Zendesk's New Tag Added to Ticket, sign in to both apps, add the steps and map the fields, choosing public or internal for each comment. Test on a test ticket, then turn 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 TT-Q-3317, signed by Sofia Marchetti. Step 2: Zendesk's Find Tickets, searching on the recipient's email, the tag quote_sent and not solved; it found ticket 9073. Step 3: Zendesk's Update Ticket, adding a public comment and setting the status to Solved.

How do I connect Zendesk to QuoteCloud?

Through Zapier, one Zap per job. Here's the signed-and-solved Zap; every recipe on this site is built the same way.

  1. Check your plans

    QuoteCloud's Zapier app is on Essentials and up. You also need a Zendesk account and a Zapier plan that covers the tasks your Zaps will run.

  2. Create a Zap, pick the trigger

    Choose the app the event happens in, such as QuoteCloud's Document Signing Complete or Zendesk's New Tag Added to Ticket.

  3. Sign in to both apps

    Zapier asks you to connect QuoteCloud and Zendesk the first time you use each. Use accounts that can see the tickets and documents.

  4. Add steps, map fields

    Add each step, such as Find Tickets then Update Ticket, map fields from earlier steps and set public or internal. The field map lists them.

  5. Test, then turn it on

    Test each step on a test ticket with an @example.com requester, check both apps, then switch the Zap on.

Step 1: the trigger, and its test data

Choose QuoteCloud, then Document Signing Complete. Zapier fetches a recently signed document as test data.

Check it has what you plan to use: the reference, the recipient's email, and the Zendesk ticket data item if your quote Zap fills it. If a field is missing, sign a complete test document and load fresh data.

The full recipe: status on the ticket
Zap editorTanbark Trade Supply Illustration · sample data

1QuoteCloudTrigger

Document Signing Complete

Account
Tanbark Trade Supply (QuoteCloud)
Trigger event
Document Signing Complete

Test: Found a document: TT-Q-3317, signed by Sofia Marchetti

Illustration with sample data, not Zapier’s screen.

Step 3: public reply or internal note?

Every Zendesk action that writes a comment asks the same question. Update Ticket calls it "Should the new Comment be public?", Add Comment to Ticket and Attach File to Ticket call it "Should the comment be public?", and Create Ticket asks it for the first comment.

Yes is a reply the requester sees, and Zendesk emails it to them as usual. No is an internal note for agents only. Decide per step: a view is usually internal, a signature is often worth a public thank-you.

  • Update Ticket also sets the status, group, assignee and tags in the same step.
  • Attach File to Ticket adds the signed PDF with its own comment.
  • A Zap never ticks options or chooses content blocks in QuoteCloud documents.
What Zapier and the fee come to
Zap editorTanbark Trade Supply Illustration · sample data

3ZendeskAction

Add Comment to Ticket

Ticket
2. ID
Comment body
1. Document reference first viewed by 1. Recipient name
Should the Comment be public?
False (internal note)

Test: Internal note added to ticket 9073

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 build your first Zendesk Zap on a test ticket.

Start free 14-day trial Book a demo

How does a Zap find the ticket again?

Zaps that start in QuoteCloud have to find the ticket. When the quote Zap drafted the quote, the ticket number is in a data item: if your trigger's test data shows it, map it straight into the Ticket field.

Otherwise, Find Tickets searches with something both apps know, such as the requester's email plus a tag your agents add when they send a quote, and "not solved". Test with a customer who has more than one ticket.

When the Zap finds no ticket
Zap editorTanbark Trade Supply Illustration · sample data

2ZendeskSearch

Find Tickets

Search
requester:1. Recipient email tags:quote_sent status<solved
If nothing is found
Stop the Zap and show it as halted

Test: Found ticket 9073: Price for a monthly cup order, four cafés

Illustration with sample data, not Zapier’s screen.

Can I connect Zendesk through Make instead?

Yes, if your team builds its own. Make is a bring-your-own route: you add a connection to QuoteCloud with Make's built-in OAuth, then call QuoteCloud's API or Zapier endpoints from a scenario, beside Make's own Zendesk modules.

There is no ready-made QuoteCloud app or list of modules on Make, so you design each step yourself. The recipes on this site are shown as Zaps; the same QuoteCloud events and actions are there when you build them in Make.

Before you start

  • Essentials for Zapier

    QuoteCloud's Zapier app and API, custom data items and the product library are on Essentials and up.

  • A Zapier plan

    Zapier bills separately: choose a plan that covers the tasks your Zaps will run each month.

  • Tags your agents use

    Agree one tag to ask for a quote and one to mark a quote sent, so Zaps can start and search on them.

  • Test tickets only

    A test requester at an @example.com address and a test template, so no public reply reaches a real customer.

Set-up questions

Is there a native Zendesk connection in QuoteCloud?

No. QuoteCloud connects to Zendesk through Zapier, with QuoteCloud's Zapier app on the Essentials plan and up, or through Make as a bring-your-own setup with QuoteCloud's API. There's no Zendesk setting inside QuoteCloud: each job, such as drafting quotes or solving tickets, is a Zap you build.

Do I need a developer to connect Zendesk?

No. Zapier is built for people who aren't developers: you pick a trigger, steps and the fields to map. A developer who wants more control can call QuoteCloud's API from their own code or from a Make scenario instead; it's on the same Essentials plan as the Zapier app.

Which accounts should I connect in Zapier?

Connect QuoteCloud and Zendesk with accounts that can see the documents and update the tickets the Zap uses. Many teams use a shared admin account so Zaps keep running when someone leaves. Comments a Zap adds may show that account as their author unless you set the author field.

How do I test without emailing a real customer?

Use a test ticket with a requester at an @example.com address and a test template. Zapier tests run against your real apps: a public comment in a test really is sent to the requester, so keep tests on test tickets and set comments to internal until you're sure.

More Zendesk questions

More on QuoteCloud and Zendesk

Five use cases with the exact Zapier steps, then how to connect, test and what it costs.

Your first Zap, this afternoon.

Start a free 14-day trial of QuoteCloud, connect Zendesk in Zapier and build your first Zap on a test ticket.

Start free 14-day trial Book a demo

See pricingQuoteCloud on ZapierAll integrations