Subscribe to Help Center RSS FeedWith JumpCloud's Workflows you can automate common identity, device, and access tasks using a no-code/low-code workflow builder UI instead of complex scripts. This is a list of frequently asked asked questions related to Workflows.
No. Each workflow is initiated by a single entry point (a Schedule, Event, or Webhook). To run similar logic from different triggers, you should create separate workflows.
Most commonly, the workflow is still set to Disabled. Check the toggle at the top of the canvas. Additionally, ensure the Execution Role has the correct permissions; if the role is too narrow, the workflow may fail to complete the action.
The workflow will stop at the failed step, and the error will be logged in the Execution History. You can view the specific API error to troubleshoot the failure.
Click the Run workflow icon (Play button) on the top right to manually trigger the flow with mock data before toggling the status to Enabled. See Running the Workflow Manually to learn more.
Changes to workflow configurations are logged in JumpCloud Directory Insights.
Use the Visual Builder for standard administrative tasks (onboarding, group management). You can make use of the predefined templates to configure workflows quickly.
The Public API is intended for developers who need to programmatically create hundreds of workflows or integrate JumpCloud logic into external custom applications.
In this Article