FAQ: Workflows

With 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.

Can I use multiple triggers in one workflow?

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.

Why did my workflow not run?

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.

What happens if a workflow fails or an action can’t be completed?

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.

How do I test a workflow before enabling it in production?

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.

Is there an audit trail or version history for workflow changes?

Changes to workflow configurations are logged in JumpCloud Directory Insights. 

Who should use the Public Facing API, and who should stick to the visual builder?

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.

What is a ‘workflow run’? How does it work? (Private Preview)

A workflow run is a single execution of an automated workflow or orchestration you've built in JumpCloud. Each time a workflow is triggered and runs (whether by a schedule, an event, or manually), that counts as one run. Designing and saving workflows does not consume runs; only executions do. Only successful workflow runs will be counted; any errors or failures will not be counted. On the workflow run meter, you can see your workflow usage relative to your monthly workflow allowance.

How many workflow runs can be performed? (Private Preview)

Every JumpCloud customer receives a base number of included workflow runs per month, depending on their plan. Runs reset at the beginning of each calendar month. Included runs reset monthly and do not carry over.

Can we purchase more runs if needed? (Private Preview)

Yes. Customers who anticipate higher usage can purchase additional run capacity. We want pricing to be as predictable as possible, so customers are encouraged to understand their usage patterns and work with their Account Manager.

Back to Top

List IconIn this Article

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case