Getting started with QuoteCloud

Test and troubleshoot the Salesforce connection

Test every Zap with fictional records before it touches a real Opportunity, then fix the problems teams usually hit, on the Zapier route and the add-on.

Test each Zap with a test Opportunity, a test template and @example.com contacts, step by step in Zapier, and check both apps before turning it on. Most problems are a Find Record that finds nothing, Updated Field on Record not set to a value, a Zap firing on the first signature, or a PDF link used too late.

Last reviewed by the QuoteCloud team

How do I test a Salesforce Zap safely?

  1. Create test records

    A test Opportunity, a test template and contacts at @example.com addresses, named so they're obviously tests.

  2. Test the trigger

    Let Zapier fetch test data, and check it has every field you plan to map, the Opportunity ID above all.

  3. Test each step

    Run each action's test in order. A test of Create Document makes a real document, so keep tests few.

  4. Check both apps

    Open the test Opportunity and the QuoteCloud document and compare them with the field map.

  5. Turn it on and watch

    Switch the Zap on and check its history after the first few real runs.

The usual problems, and the fix

  • Find Record finds nothing

    The document has no Opportunity ID data item, or it's empty. Keep the ID when a Zap creates the document, or search on the Opportunity Name, and tell Zapier what to do when nothing is found.

  • The stage trigger doesn't fire

    Updated Field on Record needs 'Field updated to' set, and suits objects with fewer than 104,000 records. Larger orgs can use New Outbound Message, per Zapier.

  • Data items are blank

    The data item names in Create Document must match the template's, and the trigger's test data must carry the field.

  • Two Zaps trigger each other

    A contact one Zap creates fires the other once. Use Find or Create steps, so the echo finds the same email and stops.

  • The PDF link stopped working

    Generate or Fetch Document PDF Link is short-lived. Upload the file in the same Zap, with Create File or Google Drive's Upload File; never store the link.

  • Closed Won after one signature

    The Zap uses Recipient Signed Document. Switch the trigger to Document Signing Complete, which waits for every signer.

With the add-on: is the document linked?

The Salesforce Sync add-on sends status back for documents linked to an Opportunity. If a document's status isn't on the Opportunity, check it was started from that Opportunity.

If nothing comes back at all, check the org is still connected from QuoteCloud, then contact QuoteCloud support.

Set up the add-on
CRM · OpportunityTallwire Communications Illustration · sample data

Opportunity · ID 0065g00000NcTr8Saltmarsh Freight Co. · Port Ellery depot

QuoteCloud New QuoteCloud document

  • TW-3152 Fibre, voice and 5G for the Port Ellery depot
    1. Draft
    2. Sent
    3. Viewed
    4. Signed
    Priya Nair · Tue 27 Oct, 11:52 am

Linked documents, status from Salesforce Sync

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

Test it with a free trial

Start a free 14-day trial, connect Salesforce with test records and build your first Zap safely.

Keep test data fictional

Tests talk to the real apps. A test of Create Document makes a real document in QuoteCloud, a test of Update Record changes a real Opportunity, and Find or Create Record can create real accounts and contacts.

Use a test template, an Opportunity named so it's obviously a test, and contacts at @example.com addresses. Archive the test documents afterwards; QuoteCloud's Archive Document action can do it in a Zap.

Troubleshooting questions

Why did my Zap say Find Record found no Opportunity?

Usually the search value is empty or doesn't match. Check that the QuoteCloud trigger's test data carries the Salesforce Opportunity ID data item, and that Find Record searches the Opportunity object on that ID. Documents a Zap didn't create may not have the data item.

Why doesn't Updated Field on Record trigger my Zap?

Check that 'Field updated to' is set to the stage value, spelled exactly as in your org. Zapier notes the trigger suits objects with fewer than 104,000 records; for larger orgs it suggests Salesforce's New Outbound Message trigger instead. Then test again with a fresh stage change.

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

Because Generate or Fetch Document PDF Link gives a short-lived link. Use it straight away in the same Zap, for example with Salesforce's Create File or Google Drive's Upload File, and never save the link itself in a Salesforce field.

Can testing create real documents or records?

Yes. A Zapier test of Create Document makes a real QuoteCloud document, and tests of Update Record or Find or Create Record change real Salesforce records. Test with fictional records and @example.com contacts, name them so they're obviously tests, and archive test documents afterwards.

More Salesforce questions

More on QuoteCloud and Salesforce

Six use cases, each marked add-on or Zapier, then how to set up both routes and what they cost.

Tested, then trusted.

Start a free 14-day trial and test the Salesforce connection with sample records before it touches a real deal.