Getting started with QuoteCloud

Test and troubleshoot the Pipedrive Zaps

Test every Zap with a sample deal before it meets a real client, then fix the handful of problems that come up most: no deal found, blank data items, Zaps that echo, links that expire.

Test each QuoteCloud and Pipedrive Zap with a test deal, a test template and @example.com contacts, then check its runs in Zapier's history. The usual fixes: match the deal's title or ID so Find Deals finds it, match data item names to the template, filter Zaps that echo, and use PDF links in the same Zap.

Last reviewed by the QuoteCloud team

How do I test the Pipedrive Zaps?

  1. Make test records

    A test deal in Pipedrive named so it's obviously a test, a test template in QuoteCloud and contacts at @example.com addresses.

  2. Draft from the test deal

    Move the test deal to the stage your quote Zap watches and check the draft's data items and recipient in QuoteCloud.

  3. Send, open and sign it

    Send it to your @example.com address, open it and sign it, and check the notes, status and file on the test deal.

  4. Test each Zap step

    Zapier tests each step against the real apps: a test of Update Deal changes the test deal for real.

  5. Turn Zaps on and watch

    Switch each Zap on and check its first runs in Zapier's history before you rely on it.

The usual problems, and the fix

  • Find Deals finds nothing

    The document's title must match the deal's title, or keep the deal ID in a data item and use Get Deal. Check the trigger's test data shows the value.

  • A Zap's data items are blank

    Data item names must match the template exactly, and each must be mapped from a step that has the value.

  • Two Zaps trigger each other

    Match people on email so the second Zap finds instead of creating, and add a Filter by Zapier step where it helps.

  • The PDF link stopped working

    Generate or Fetch Document PDF Link is short-lived. Attach or upload the file in the same Zap; never store the link.

  • The deal was won after one signature

    Use Document Signing Complete, which waits for every signer, not Recipient Signed Document.

  • Nothing shows on the deal

    Only Zaps write to Pipedrive. Check the Zap is on, then open its run in Zapier's history: a filter may have stopped it, or Find Deals found nothing.

What a good test leaves behind

After a test of the won Zap, the test deal should be won, with the signed PDF attached if you added that step.

If anything is missing, open the Zap's run in Zapier's history: each step shows the data it received and what it sent.

Check every field against the field map
CRM · DealQuillfield IT Illustration · sample data

Deal · ID 2240Calder Physio Group · Managed ITOrganization: Calder Physio Group

  1. Qualified
  2. Discovery
  3. Proposal made
  4. Negotiation
Value
$16,800.00
Owner
Nina Castell
Person
Jake Calder
Status
Won Updated by a Zap

Activity timeline

  1. Status changed to WonQF-4122 signed by Jake CalderThu 22 Oct · 9:42 am · Added by a Zap
  2. Stage changed to NegotiationBy Nina CastellMon 19 Oct · 2:12 pm
  3. Deal createdBy Nina CastellMon 5 Oct · 1:40 pm

Illustration with sample data: a generic CRM record, not Pipedrive’s screen.

Test it with a free trial

Start a free 14-day trial of QuoteCloud and test your Pipedrive Zaps with a sample deal before they touch a real one.

Why keep test data fictional?

Tests talk to the real apps. A test of Create Document makes a real document in QuoteCloud, and a test of a Pipedrive action creates or changes a real record, so test with records made for testing.

Use a test template, a deal named so it's obviously a test, and contacts at @example.com addresses. Keep tests of Create Document few, since documents created through Zapier carry the per-document fee, and archive test documents afterwards.

  • QuoteCloud's Archive Document action can tidy test documents in a Zap of their own.
  • What the fee comes to for your volume.

Troubleshooting questions

Why did my Zap find no Pipedrive deal?

Find Deals searched for a value that isn't on any deal. Check the QuoteCloud trigger's test data shows the document's title, that it matches the deal's title exactly, and that Find Deals searches the title. If you keep the deal ID in a data item, Get Deal on that ID is surer.

Why doesn't anything show on the Pipedrive deal after a quote is viewed?

Because only a Zap writes it there. QuoteCloud has no direct connection to Pipedrive, so check the first-view Zap is switched on, then open its run in Zapier's history. A Filter by Zapier step may have stopped it, or Find Deals may have found no deal with that title.

My signed PDF link doesn't open any more. Why?

Generate or Fetch Document PDF Link returns a short-lived link on purpose. Use it in the next step of the same Zap, for example Pipedrive's Attach File or Google Drive's Upload File, rather than saving the link on the deal, where it will stop working.

Can testing create real documents or change real deals?

Yes. Zapier tests run against your real apps, so a test of Create Document makes a document in QuoteCloud and a test of Update Deal changes a deal in Pipedrive. Use test records and @example.com contacts, and keep Create Document tests few.

More Pipedrive questions

More on QuoteCloud and Pipedrive

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

Tested, then trusted.

Start a free 14-day trial and test QuoteCloud's Pipedrive Zaps with a sample deal.