Skip to main content

NTX PowerShell Action - Stable Release

 

Features

  • Robust security features based on Windows Remote Management.
  • Ability to execute PowerShell scripts from any machine allowing Remote Management from your SharePoint servers.
  • PowerShell exceptions are handled so workflows are unaffected.
  • OpenSource
  • Actively Developed
  • Automated Installation Routine

Planned Features

  • Async PowerShell script execution
  • Script Repository
  • Run worker as a centralized SharePoint service instead of in Workflow Infrastructure
  • Pass SPServer object to PowerShell session for determining executing server.

 

Current roadmap/planned features can be found here.

 

Downloads

Disclaimer: As stated in our Terms of Use, Nintex is not responsible for any third-party content made available for download on Nintex Connect, whether or not this content has been reviewed and/or moderated by Nintex and regardless of who originated that content (including, but not limited to, Nintex employees, partners, affiliates, or moderators).  Users shall assume all risks associated with applications and other content provided on Nintex Connect.  Nintex does not provide support for any content and plugins provided for download at communities.nintex.com.

 

NTX - Home

 

Source Code

 

Source Code (Archive)

Source Code on Github

 

Screen Shots

 

NTXPS_Screenshot.png

screenshot.jpg

For anyone needing the source or release files, they are now located here: GitHub - modembug/NTX: NTX is a set of custom actions that extend functionality of Nintex Workflow. 

I have updated the post to reflect the new location as well.

Aaron

I am using latest version of Nintex 2016 workflows. You have any idea if this is part of this release or when is Nintex going to release as part of the package?

Thanks

Selvi

For anyone else looking  for a powershell action for Sharepoint 2016, please have a look at the solution provided by DataOne:

Data One: Data One 4 PowerShell 

how can I install this extension feature in Nintex Workflow.

Any known issues using the PowerShell Action with 2019 on prem?



 



Thanks

Has anyone had success using the PowerShell action while using a Workflow Constant in the Computer Name field? When I try to set the Computer Name using either a Workflow Constant or a string variable I receive the error listed below. When I hard code the server name in the Computer Name field, the PowerShell runs fine.



 









































System.UriFormatException: Invalid URI: The hostname could not be parsed.
   at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
   at System.UriBuilder.get_Uri()














Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings