StitchOps + JumpCloud
JumpCloud decides. StitchOps executes.
JumpCloud governs your cloud apps and devices. Legacy and on-prem apps without SCIM still need manual tickets when a user changes.
What the rest of the stack cannot reach.
In the joint go-to-market, JumpCloud owns the directory and the trigger. StitchOps owns execution inside the closed apps. The hand-off is a connector operation that calls the StitchOps workflow execute API, and the receipt returns to the JumpCloud audit trail.
Offboarding in legacy apps
When JumpCloud suspends a user, StitchOps removes them from the vendor portals and thick clients JumpCloud cannot reach.
Provisioning beyond SCIM
Roles and entitlements the app's SCIM connector does not expose, set the way an admin would set them.
Receipts back to JumpCloud
Step-level evidence from each closed app returns to the JumpCloud audit trail against the original event.
On-prem directory steps
LDAP and Active Directory changes run from the worker VM inside your network in the same workflow.
How it works with JumpCloud.
Step 1
JumpCloud decides
A user is suspended, moved, or created in JumpCloud. The JumpCloud connector calls the StitchOps workflow execute API with the user as a typed input.
Step 2
StitchOps executes
The agent on your worker VM logs into each closed app with a vaulted credential and makes the change, step by step, with confirmation gates where you set them.
Step 3
The receipt returns
Status, timing, and evidence references go back to JumpCloud, so the audit trail shows the closed apps too.
How it runs
Described once. Replayed every time.
Tell Stitch the task, review the typed steps, and save it. The agent runs it on a worker VM in your environment with a vaulted credential, and logs every step.
See the platform →What you can finally automate.
Offboard a suspended JumpCloud user from the apps without SCIM
Provision a role in a legacy app when a JumpCloud group changes
Verify access was removed and return the evidence to JumpCloud
Rotate a shared portal password and update the vault
Governance
Ask for it in plain language.
Claude, ChatGPT or Copilot can run these from your existing assistant. The model picks from typed tools; the agent owns the credentials and stops for confirmation on anything destructive.
Connect your assistant →I found a saved workflow for this. Running it on worker-01.
tool call
workflow_offboard_closed_apps
{ "email": "j.doe@example.com" }
Confirmation required
Step 5 deactivates the user in vendor-portal. This cannot be undone by the workflow.
completed in 5.2s
3 portals · 6 steps · evidence: step_05.png, step_11.png, step_17.png
Done. The user is removed from all three portals. Evidence is attached to run_01j8k.
The SCIM tax
JumpCloud provisions every app that offers SCIM, and many apps offer it only on their most expensive plan. The SCIM tax calculator shows what that costs across your stack, and what you keep when StitchOps extends JumpCloud to those apps on the plans you have.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.