Skip to main content

​
Automation setup

Connect JumpCloud with an API key to use JumpCloud user, system, group, policy, alert, and device actions in Flow automations. The API key and JumpCloud organization ID decide which organization Flow can reach. Flow checks setup with a bounded system users request. That check proves the key can read directory users in the selected organization. It doesn’t prove every device command, user write, policy, group, or alert permission.

​
Prerequisites

  • A Flow admin who can manage integrations.
  • A JumpCloud administrator API key.
  • The JumpCloud organization ID for the organization that owns the API key.
  • Permission to read system users.
  • Extra JumpCloud permissions for each write or device action your automation uses.
Use a key created for Flow. Don’t reuse a personal administrator key that also supports unrelated scripts.

​
Provider setup

Prepare the JumpCloud key and organization ID before you connect Flow.
1

Open JumpCloud API settings.

In JumpCloud, open the admin console area where your organization manages administrator API keys.
2

Create or choose an API key.

Use a key from an administrator account that has the least access required for the automations you plan to run.
3

Record the organization ID.

Copy the JumpCloud organization ID for the same organization that owns the key. Multi-tenant administrators must use the organization ID that matches the target tenant.
4

Grant directory read access.

Confirm that the key can call GET /api/systemusers for the selected organization.
5

Grant action-specific permissions.

Add only the permissions needed by the actions your automations run. Device commands and destructive system actions need extra review.

​
Connect in Flow

1

Open Integrations.

Search for JumpCloud. This connection is available to organizations with Preview access.
2

Select Connect.

Name the connection and choose which teams can access it.
3

Enter the JumpCloud organization ID.

Enter the 24-character organization ID for the target JumpCloud organization.
4

Enter the API key.

Paste the JumpCloud API key. Flow stores the key securely and uses the organization ID as trusted connection context.
5

Complete setup.

Flow checks GET /api/systemusers?limit=1&skip=0&sort=&fields= with the organization ID. If JumpCloud rejects the key or denies directory reads, correct the JumpCloud access and reconnect.
6

Enable Automations for the intended team.

Open the connection and enable Automations for each team that needs it. Sharing a connection does not enable automations.
7

Select the permitted actions.

Review action access and approval requirements before you use the connection in an automation.

​
Capabilities

Use the connection to read and manage JumpCloud users, systems, groups, policies, alerts, and supported device actions. Each action still depends on the connected administrator key’s JumpCloud permissions. Treat command and device actions as high impact. Test them against a non-production target before you allow production automations to run them.

​
Automation connector reference

Use the generated JumpCloud action reference for action inputs, outputs, risk tiers, and release stage.

​
Sync and behavior

This connection runs actions when an automation requests them. It does not sync Knowledge or Assets, and it does not receive JumpCloud webhooks. Flow sends the saved organization ID with JumpCloud action requests. Automation authors cannot override the organization ID in an action input. To rotate the key, create a replacement key for the same JumpCloud organization and reconnect in Flow. Test the read-only system user action before you run write or device actions with the replacement key.

​
Troubleshooting