Skip to content

Settings and activity

1 result found

  1. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    noelh commented  · 

    Hi! Thanks for reaching out.

    We use the Salesforce>PD integration.

    We create opportunities in SF and then use the integration to create documents in PD that pre-fill with the data from the fields on the Opportunity like project dates, descriptions, user counts, and much more. We typically use 20-30 tokens per document. We also use those same tokens to update salesforce when the document is sent. We trigger the Pandadoc API and have a Zapier zap that then updates those values back in Salesforce. This keeps the ability to update within PandaDoc and not having to edit in Salesforce and resync.

    Pricing Tables have always allows us to include the tokens (e.g. User counts, rates, and quantities). This is detailed information that our customers require in their PandaDoc contracts. If we cannot use tokens in the pricing tables, we then have to manually add them in and update them when field change elsewhere in the document or Salesforce.

    The salesforce integration is a costly add-on and this is core functionality that needs to stay present, otherwise the add-on is not worth it.