A desktop app to interact with the Adobe Cloud Manager API — list and manage programs, pipelines, and pipeline executions across multiple organizations.
- Multi-organization support — Add and switch between different Adobe organizations
- Programs — List and view program details
- Pipelines — List pipelines per program, view details, start pipelines
- Executions — List execution history, view current execution, advance/cancel steps
npm install
npm startTo use this app, you need to set up API credentials in Adobe. Here’s what to configure.
Who can create integrations
You need either:
- System Administrator for your organization, OR
- API Developer role for Cloud Manager product profiles
Assign API Developer access
- Go to Adobe Admin Console
- Open Users → Developers
- Click Add Developer
- Enter the user’s email
- Under Assign Products, add Cloud Manager and the desired product profile(s):
- Cloud Manager - Developer — read-only (GET)
- Cloud Manager - Deployment Manager — pipeline start, advance, cancel, edit pipelines, etc.
- Cloud Manager - Program Manager — pipeline start, advance, cancel
- Cloud Manager - Business Owner — full access including
deleteProgram
- Save
- Go to Adobe Developer Console
- Create new project (or open an existing one)
- Add to Project → API
- Under Experience Cloud, select Cloud Manager → Next
- Choose OAuth Server-to-Server (not JWT)
- Select the Product Profile(s) that match the permissions you need:
- Developer: read (programs, pipelines, executions)
- Deployment Manager or higher: start pipeline, advance/cancel steps
- Click Save configured API
From your Cloud Manager API integration:
- Client ID — used in the app as “Client ID (API Key)”
- Client Secret — used as “Client Secret”
- Organization ID — shown in the credential details (format like
xxxxxxxx@AdobeOrg)
Optional: If your integration uses custom scopes, copy the Scopes value. Otherwise leave the app’s Scope field blank; it will use the default Cloud Manager scope.
- Run the app:
npm start - Click + Add Org
- Enter:
- Display Name — e.g. “Production Org”
- Organization ID — from Developer Console
- Client ID — from Developer Console
- Client Secret — from Developer Console
- Click Save
| Action | Product profile(s) |
|---|---|
| Read programs, pipelines | Developer |
| Start pipeline | Deployment Manager, Program Manager, Business Owner |
| Advance/cancel steps | Deployment Manager, Program Manager, Business Owner |
| Edit pipeline | Deployment Manager |
| Delete program | Business Owner |
- Cloud Manager API – Create API integration
- Cloud Manager API – Authentication
- Cloud Manager API – Permissions
- Cloud Manager users and roles
npm testRuns tests for the API layer and store. Use npm run test:watch for watch mode or npm run test:coverage for coverage.
First install the Cypress binary (one-time):
npx cypress installThen run the UI tests:
npm run test:e2eOr open the Cypress UI for interactive testing:
npm run test:serve # In one terminal - serves app at http://localhost:8080
npm run cypress:open # In another - opens CypressThe E2E tests use a mock electronAPI so they run in a browser without Electron. Tests verify navigation, modals, and data loading flows.
- Credentials are stored locally via
electron-store. - Client Secret is stored in plain text in the app config. Use this only on trusted machines.
- Tokens are cached in memory and refreshed automatically (tokens are valid ~24 hours).