Empower Your Workflow with the Nintex Community | Resources, Tips, and Collaboration

Updated 12/15

Get Ready! Salesforce Outbound Message changes could disrupt DocGen packages Published: 10th December 2025 Update 12th December 2025 - see bottom of pageOffice Hours are being offered.Update to recommended approaches in yellow. Update 15th December 2025Some customers have successfully requested and received a three-month extension on Session ID usage from Salesforce. 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 DecemberOffice hours are being offered starting 5th January 2026 through 20th February 2026We 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.

News

Prepare now: Salesforce OAuth updates may affect DocGen package generation Do you have Connected Apps and OAuth enabled in Salesforce? In January 2026, all new Nintex DocGen for Salesforce releases will require OAuth authentication. Older authentication methods will no longer be supported.Switch now to our supported authentication method, Connected Apps and OAuth, so you won’t experience service interruptions or last-minute issues during a future app upgrades. What Customers Should Do Now Go to Nintex Admin → Settings in Salesforce Check the status of the Connected Apps and OAuth setting If the setting is already ON, no further action is needed. You’re already using Connected Apps and OAuth and are ready for future updates. If the setting is OFF, we recommend turning it ON at your earliest convenience Follow these simple steps to turn it on. After OAuth Is Enabled: What’s Different?Manual runsUsers will see an Authorize and Run button the first time they generate a document.Automated runsWill continue to work if the automation user has already completed OAuth authorization. If not, these runs may fail until authorization happens. How can users authorize?You can manage how users authorize Nintex DocGen in Salesforce by adjusting the Permitted Users OAuth Policy for the Connected App.There are two optionAll users may self-authorize (Default)Each user will be prompted to authorize the first time they run a DocGen PackageAdmin approved users are pre-authorizedOnly users with a specific Salesforce profile or permission set can run DocGen without needing to authorize manuallyThis video reviews the process to manage these settings. Tip: To avoid large numbers of users seeing authorization prompts, many customers choose Admin approved users are pre-authorized and then manage user access via Salesforce Profiles or Permission Sets.For more specifics, see Salesforce Help: Manage OAuth Access Policies for a Connected App Avoid last minute issues. Test the change in sandbox now, then roll it out to production. Next Steps:Turn on Connected Apps and OAuth in Nintex Admin. Review and set your preferred Salesforce OAuth Policy for the Nintex DocGen Connected App. Have users (or automation accounts) complete OAuth authorization.Doing this now ensures your DocGen for Salesforce processes keep running smoothly—even after your 2026 upgrade. Here are some more helpful links related to OAuth Community articles:User Authorization Options via Salesforce Connected AppsConnected Apps and OAuth Nintex Admin Tab

We're excited to introduce the Organization Portal, a new portal to help organization admins manage their Nintex organization more effectively.Many Nintex customers have more than one tenant, but what you might not be aware of is that those tenants are part of the same organization. Some settings are shared between all tenants in the organization, such as SSO or SCIM. Until now, those features have been configured from within a tenant, but they affect all tenants, leading to potentially unexpected impacts.The Organization Portal is our first step in exposing the concept of an organization to all customers and making it easier and clearer the impact of changing organization-level features.Who has access to the Organization Portal?To access the Org Portal, you need to be assigned a new role: Organization Admin. The Organization Admin role will replace domain verification as a method for getting additional permission to manage SSO or SCIM.All existing domain verifiers have been assigned the Organization Admin role as part of the release of the Org Portal. If you don’t know who your Organization Admin is, please contact support.How do I find the Organization Portal?For customers with the new navigation the Organization Portal can be accessed by clicking “Settings” in the left menu bar to expand the full settings menu and then clicking “Organization” in the expanded menu. For customers with the old navigation the Organization Portal can be accessed by clicking “Settings” in the top menu bar and then clicking “More settings” under “Organization Settings”. How do I add more Org Admins?New Organization Admins can be assigned from within the Org Portal using the following steps:Open the Org Portal Click the users page Find the user you want to assign as an Org Admin and click the ‘...’ and select edit Check the “Organization Admin” checkbox and they will now have access to the org portal and all associated functionality What can I do in the Org Portal?To start with the following features are available in the org portal:Users – View all the users in your organization in one place. Directories – Configure and manage identity providers at the organization level. SCIM – Automate user lifecycle management across your environment. Domain Management – Manage the verified domains for your organization.What’s next?We’ll be continuing to migrate org-level features into the organization portal. We’ll also be adding new features such as support for multiple SSO and tenant-level auth configuration, and full user lifecycle management from the org portal, including adding and removing users and assigning roles.The Org Portal is the foundation for more powerful organization-level management and governance features to come and we’d love your feedback as you begin using it.Share your thoughts and questions in the comments below.

System Manager 2.0 delivers on our promise of an intuitive, GUI-driven experience that simplifies server administration. In previous releases (RPA versions prior to 25.11), uninstalling a server required manual intervention via PowerShell or CLI commands—a process we know most teams prefer to avoid. With this release, uninstalling your RPA server is entirely visual. No scripts. No command-line complexity. Just a clean, guided workflow that lets you focus on automation. Important: The graphical uninstall feature is available only for RPA version 25.11 or later.To uninstall your Nintex RPA server:Navigate to the Actions tab. Select Uninstall. Wait a few minutes for the process to complete. Click Finish. Restart Windows to finalize the uninstall.Explore everything you need in our help documentation and release notes – your complete guide to getting the most out of your RPA 25.11 system.

Nintex Automation K2 (5.9) is now available to download on Nintex Customer Central (filter for "Nintex Automation" in the products drop-down menu) or on Nintex Partner Central (under the Products > Product Downloads menu). This release introduces customization capabilities, accessibility improvements, and platform optimizations, including:Custom Control Framework. Build and manage custom form controls directly within K2. Create purpose-built interface components that match your specific UI requirements, manage them centrally, and deploy consistently across your applications. Accessibility improvements. Runtime SmartForms now include enhanced support for assistive technologies, helping ensure your workflow applications are accessible to all users. Enhanced error codes in the REST broker. Integration troubleshooting gets easier with descriptive error responses that help you identify and resolve issues faster across your RESTful connected systems. Direct file handling. JSSP endpoints now support direct file operations, eliminating the need for base64 encoding and simplifying file management in your JavaScript based integrations. OData v4 enhancements. Improved support for complex data relationships and better integration capabilities to support Microsoft Dynamics 365 and Business Central environments. Performance optimizations. Authorization framework improvements deliver significant performance gains in large-scale Active Directory environments. Add external links to applications. New organizational tools, including the ability to add hyperlinks to K2 categories, keep design teams productive. Improved license reporting. Export usage reports directly to CSV format for easier analysis and license management. SharePoint migration support. New user interface for the Nintex for SharePoint workflow importer simplifies bulk migrations from legacy Nintex for SharePoint solutions.K2 release 5.9 is a Long-Term Support (LTS) release, providing 2 years of standard support and 2 years of extended support (4 years total). All stability and security fixes released since 5.8 are included in this release.For complete details on these features, check out the release notes available on help.nintex.com. Join us for the customer enablement webinar on December 3rd to see live demonstrations and implementation guidance from the product team.

Welcome!

Nintex Community

Nintex Community Connect: December Edition

Action required: Salesforce Outbound Message changes could disrupt DocGen packages

Salesforce OAuth updates may affect DocGen package generation

Introducing the New Organization Portal

A smarter way to unistall your RPA server

Now Available: Nintex Automation K2 (5.9)

Write a Review of Nintex

Join the Conversation

What’s New for You

Trending Discussions

Questions Awaiting Answers

Learn and Level Up

Forums

Articles

Events

User Groups

Explore Nintex Resources

Nintex Customer Central

Nintex Status

Nintex University

Nintex Help

Nintex Gallery

Nintex Ideas

Nintex Professional Services

Nintex Partner Portal