Nintex DocGen for Salesforce

Nintex DocGen for Salesforce is a no-code solution that automates your document generation and delivery process from data stored in your Salesforce org. This easy-to-use solution allows you to create compliant and consistent documents while reducing human error from manual document generation.

By integrating with Nintex DocGen, you can use templates created in Nintex eSign to generate a documents from Salesforce record for quick and easy signing. You can navigate to a Salesforce record, such as an Opportunity, and quickly generate a document using a Nintex eSign template when selecting Nintex eSign as a delivery option.

Important: The webhook functionality for Nintex eSign does not support Salesforce GovCloud orgs for use with Nintex DocGen.

Integration Requirements

In order to integrate with Nintex DocGen, you will need the following:

  • A Salesforce account

  • A Nintex DocGen license

  • Install Nintex DocGen

  • Set up of the Nintex eSign integration option through Nintex DocGen

For more information on how to set up and use Nintex eSign with Nintex DocGen, refer to the Nintex eSign Delivery Option help topic.

Important information and troubleshooting

The integration with Nintex DocGen works by using templates created in your instance of Nintex eSign and syncing that data to Nintex DocGen. However, there is some important information and possible troubleshooting that needs to be done if you see any issues with your templates or template syncing.

  • If a Nintex eSign delivery option was created prior to Nintex DocGen version 18.2, then you will need to re-sync the templates on the eSign Delivery Option to use the new DocGen eSign Envelope (see Nintex eSign Envelopes). If the Templates are not re-synced, the Nintex eSign Delivery Option will continue to create records for the Envelope Object from the eSign Lightning Application.

  • if you alter a template in Nintex eSign, you must click Refresh Inputs so that the changes you made are reflected in the Nintex eSign delivery method.

  • If you alter the default Signer Identifier in Nintex eSign, special characters are not supported. Use only alphanumeric characters, spaces, and underscores, but do not use consecutive spaces and underscores. For example, Signer_1 or Signer 1 are supported, but Signer-1, Signer__1, and Signer _1 are not.)