Processes define suites: which tests to include (tags), schedules, and triggers.
With an API key, reading processes and their triggers needs the execution:read scope. Creating or changing a process, its triggers or its automation needs platform:manage.
Custom process payload
When creating a custom process (isSystem: false), send:
name(required)kind(suiteoragent)goal(required)configuration.testCaseTags(optional)
Custom processes are manual-only today:
- server ignores custom schedule/triggers and stores manual behavior
- memory is disabled and not configurable
List processes
GET
/api/projects/{projectId}/processesBearer TokenOverview (UI)
GET
/api/projects/{projectId}/processes/overviewBearer TokenCreate process
POST
/api/projects/{projectId}/processesBearer TokenGet process
GET
/api/projects/{projectId}/processes/{idOrSlug}Bearer TokenUpdate process
PUT
/api/projects/{projectId}/processes/{idOrSlug}Bearer TokenTriggers
GET
/api/projects/{projectId}/processes/{processId}/triggersBearer TokenPUT
/api/projects/{projectId}/processes/{processId}/triggersBearer TokenExecute process (create a run)
POST
/api/projects/{projectId}/processes/{processSlug}/execute?environmentId=...Bearer TokenenvironmentId is a query parameter and is required. The response has processRunId, itemCount and message. If the process already runs in that environment, you get 409. With an API key, this needs the process:execute scope.