Get Ready! Salesforce Outbound Message changes could disrupt DocGen packages
Originally Published: 10th December 2025
Update 24th February 2026
- Released! the ability to secure connections between Nintex and Salesforce with certificates (with the DocGen integration account). Check the updated help steps to complete your transition.
January 2026 Updates
- Nintex and Salesforce have worked together to get an extension for known affected Orgs until May 31st, 2026. Your Nintex contact will be in touch.
- Added the Nintex help link to the newly published steps for setting up secure communication with Nintex with Outbound messages.
- Salesforce have moved the deprecation by one week to Feb 23rd.
Updates December 2025
- Some customers have successfully requested and received a three-month extension on Session ID usage from Salesforce.
- Office Hours are being offered.
Do you use Salesforce Outbound Messages (OBMs) to automate your DocGen packages?
Beginning February 23, 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 outbound 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 23 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
- You can now secure these connections with certificates. These connections will use the DocGen Integration user to run your DocGen Packages. This approach does not require a appExchange package update**. Follow the updated help steps to implement this today.
- This uses 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.
- ** If your organization has a signed certificate already in use for other OBMs, check our documentation for “adding an existing certificate”, this specific scenario may require a package update.
- Run as a specific user by Impersonation of a Specific User
- We are building an approach to allow impersonation (using the “User to send as” OBM setting). This is not ready yet, so check back here regularly. If you have specific use cases for this, please attend our office hours, detailed below.
What’s next?
- Read through the instructions to secure Outbound messages with certificates, and start your internal process to make these changes from test through to production.
- Extensions - Nintex have worked with Salesforce on an extension until May 31st, for Org IDs identified as using Outbound messages to call Nintex DocGen for Salesforce. Your Nintex contact will be in touch with these IDs. If you have additional Orgs (sandboxes, dev orgs, etc) that need an exception, continue to ask Salesforce directly for an extension for these Orgs.
This will not change how the DocGen package works; it will only affect the authentication between Salesforce and our service.
Office Hours
Office hours are being offered starting 5th January 2026 through 13th March 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.
Note: This post will be updated!