Get Ready! Salesforce Outbound Message changes could disrupt DocGen packages
Published: 10th December 2025
Update 12th December 2025 - see bottom of page
Office Hours are being offered.
Update to recommended approaches in yellow.
Do you use Salesforce Outbound Messages (OBMs) to automate your DocGen packages?
Beginning February 16, Salesforce will remove the ability to send Session IDs from Outbound Messages. This change will cause document generations using these OBMs to fail. The Nintex team is here to help.
Actions Required
The following should be done by a Salesforce administrator in your organization:
1.Review Impact. Check your Salesforce settings for Outbound Messages that are used for document generation with Nintex.
To do this, go to Salesforce Setup, then search for “Outbound” You will find your list of Outbound Messages in Process Automation -> Workflow Actions -> Outbound Messages. You can then find messages with the “Endpoint URL” like:
- https://*.docgen.nintex.io/package/111 (where * could be api, gov, na1 etc)
- https://*.drawloop.com/package/111 (where * could be api, gov, na1 etc)
These messages will all have the Send Session ID turned on. After February 16 this field will no longer be available and these messages will fail. Once these messages are all identified you can move to step 2.
2.Check User to Run as. For each OBM identified in step 1 , you’ll need to look at the User to run as. Does this OBM need to run as a specific user? Or is it acceptable to run as the current user (e.g. Flow context user). We recommend different approaches for each:
- Run as the current user and does not require Impersonation
- In January, we will have an update of Nintex DocGen for Salesforce in the AppExchange that will allow you to continue to use OBMs, securing them with certificates. The expected process will be to create a TLS Certificate in Salesforce Setup, then configure Nintex to point to this certificate, and finally update each of your OBM configurations to use the certificate. This means the DocGen packages run in this way will use the DocGen Integration user.
- Using the DocGen Integration User, and will ignore the "user to send as" configured in the OBM.
- The Integration user may have more or less access to the Salesforce Objects being merged into documents.
- User Tags in generated documents will use the integration user's name. (including formula fields)
- Emails targeting the running user of the DocGen package will get sent to the integration user.
- Run as a specific user by Impersonation of a Specific User
- We are working on an approach similar to the Certificate approach above for January to accommodate this need. Please check back here regularly.
What’s next?
This post will be updated!
Update 12th December
Office hours are being offered starting 5th January 2026 through 20th February 2026
We do not yet have solutions for every impact of this change, but we can review your specific use cases together to identify the best available approach.
Monday, Wednesday, Friday. 8:00AM PST Click to join.
Monday, Wednesday, Friday. 3:00PM PST Click to join.
