Getting started with QuoteCloud

Test and troubleshoot QuoteCloud Zaps

Test every Zap with records only you will see, then use the fixes below when a search finds nothing, a link has expired or a row lands in the wrong place.

Test each QuoteCloud Zap with a test document sent to yourself and a test record in the other app, so nothing reaches a client. Most problems come from exact matching (searches match whole values, including capitals), short-lived PDF links that must be used in the same Zap, and price tables without API mode and a Table API Link Id.

Last reviewed by the QuoteCloud team

How to test without reaching a client

  1. Use test records

    Make a test document addressed to your own email, and a test row, deal or ticket in the other app.

  2. Create the event

    Open, sign or pay the test document yourself so the trigger has a recent sample to pull in.

  3. Test each step

    Test step by step in the Zap editor and check the result in both apps before moving on.

  4. Keep sending off

    Leave Auto Send Document off while testing, so a created document stays a draft.

  5. Clean up and turn on

    Archive the test documents with Archive Document or in QuoteCloud, then publish the Zap.

Why isn't my QuoteCloud Zap working?

The usual causes, and the fix for each.

  • A search finds nothing

    Find Document by Field and Find Contact match the whole value exactly, including capitals. Map the stored value itself, such as a deal ID kept in a custom field, rather than a name someone may retype.

  • The wrong document is found

    When several documents match, Find Document by Field returns the newest. Use a unique value, such as the document number or an ID, as the search key.

  • The PDF link no longer works

    Generate or Fetch Document PDF Link returns a short-lived link. Upload or attach the file in the very next step of the same Zap. Fetch Current Only fails when there's no current PDF: use Use Current PDF.

  • Rows don't reach the price table

    Turn on API mode in the price table's settings, set its link ID and use the same value in Table API Link Id. Each row needs Row Type 'pricing' or 'heading'.

  • A recipient can't be added

    Add Document Recipient works on an editable document, such as a fresh draft. To change a recipient, use Update Document Recipient with the Recipient Reference from Find Document.

  • The view trigger doesn't fire

    Recipient First Viewed Document fires for identified private recipients. Test it by opening the document as the recipient, from the link in their own email, not as its owner.

  • It fires once per signer

    That's Recipient Signed Document, which fires for each signer. Use Document Signing Complete when the Zap should run once, after the last signature.

  • Update Contact changes nothing

    Update Contact never creates a contact; when the email or ID doesn't match, nothing is updated. Use Find or Create Contact when the contact may be new.

  • The image doesn't appear

    Upsert Document Image needs the image block's API Link ID set on the template, and a Cell ID for a gallery with several cells. Files must be PNG, JPEG, WebP or GIF.

  • An email bounced

    Document Delivery Failed fires on bounces. Fix the address with Update Document Recipient, then run Retry Document Delivery.

Habits that prevent most problems

  • Store a key

    Keep the other app's record ID in a QuoteCloud custom field, and the QuoteCloud document number on the other record. Searches then match first time.

  • Use exact step names

    Older names such as Generate PDF Link or Update Status are out of date. Use the names in the reference.

  • Watch the Zap history

    Zapier keeps a history of every run. Check it after the first real runs, and give someone the job of looking at errors.

Test it before your clients do

Start a free 14-day trial and run every Zap against test documents first.

Troubleshooting, answered

How do I test a QuoteCloud Zap without emailing a client?

Use a test document addressed to your own email and leave Auto Send Document off. Open, sign or pay that document yourself to create the trigger's sample, then test each step in Zapier and check the result before turning the Zap on.

Why does Find Document by Field return the wrong document?

It returns the newest document whose field matches the value exactly. If several documents share the value, such as a client name, the newest wins. Search on something unique, such as a deal ID stored in a custom field.

Why did my Zap stop after Generate or Fetch Document PDF Link?

Usually because the link was used too late or the PDF mode was Fetch Current Only with no current PDF. Use Use Current PDF, and upload or attach the file in the very next step of the same Zap, since the link is short-lived.

More automation questions

Test once. Trust it after.

Start a free 14-day trial and build your Zaps against test documents first.