Skip to main content
Automations let you define rules that execute actions automatically in response to events or on a schedule. Each automation belongs to a project and consists of a trigger (what starts it) and one or more actions (what it does). Use the endpoints below to manage automations and inspect their run history. All requests require your API key in the Authorization header as Bearer <your_api_key>.

List automations

GET https://api.chevre.io/v1/automations Returns a paginated list of all automations accessible to the authenticated API key, across all projects the key has access to. Results are ordered by creation date, newest first. To retrieve automations scoped to a specific project, use the List automations in a project endpoint.

Query parameters

integer
default:"1"
The page number to retrieve. Must be a positive integer.
integer
default:"20"
The number of automations to return per page. Minimum is 1, maximum is 100.
string
Filter results to only automations belonging to the specified project (e.g. proj_01ABC). Optional.

Example request

Example response

200

Response fields

array
An array of automation objects.
object
Pagination metadata for the response.

List automations in a project

GET https://api.chevre.io/v1/projects/{project_id}/automations Returns all automations defined in the specified project. Results are ordered by creation date, newest first.

Path parameters

string
required
The unique identifier of the project whose automations you want to list (e.g. proj_01ABC).

Example request

Example response

200

Response fields

array
An array of automation objects for the project.

Create an automation

POST https://api.chevre.io/v1/automations Creates a new automation in the specified project. You can create both event-driven and scheduled automations. An automation must have at least one action defined to be valid.

Request body

string
required
The ID of the project to create the automation in.
string
required
The display name for the automation. Must be between 1 and 255 characters.
string
required
The type of automation. Accepted values:
  • "event" — fires when a specified event occurs in the project.
  • "scheduled" — fires on a cron schedule.
boolean
default:"true"
Whether the automation should be active immediately after creation. Set to false to create the automation in a paused state.
object
required
The trigger configuration for the automation.
array
required
An ordered list of actions to execute when the automation fires. Each action must include a type and a config object specific to that action type.

Example request

Example response

201

Response fields

object
The newly created automation object.

Get an automation

GET https://api.chevre.io/v1/automations/{id} Retrieves a single automation by its ID, including its full trigger and actions configuration.

Path parameters

string
required
The unique identifier of the automation to retrieve (e.g. auto_01GHI).

Example request

Example response

200

Response fields

object
The requested automation object with full configuration.

Update an automation

PATCH https://api.chevre.io/v1/automations/{id} Updates one or more fields on an existing automation. Send only the fields you want to change. To pause an automation without deleting it, set enabled to false.

Path parameters

string
required
The unique identifier of the automation to update (e.g. auto_01GHI).

Request body

string
A new display name for the automation.
boolean
Set to false to pause the automation, or true to re-enable it.
object
A replacement trigger configuration. The entire trigger object is replaced — partial updates to trigger subfields are not supported.
array
A replacement list of actions. The entire actions array is replaced — partial updates to individual actions are not supported.

Example request

Example response

200

Response fields

object
The updated automation object, reflecting all applied changes.

Delete an automation

DELETE https://api.chevre.io/v1/automations/{id} Permanently deletes an automation and all of its run history. Disable the automation first if you want to stop it from running without losing its configuration and history.
This action is permanent and irreversible. The automation’s run history will also be deleted. If you only want to stop the automation from running, set enabled to false using the Update an automation endpoint instead.

Path parameters

string
required
The unique identifier of the automation to delete (e.g. auto_01GHI).

Example request

Example response

204
A successful deletion returns HTTP 204 No Content with an empty response body.

List automation runs

GET https://api.chevre.io/v1/automations/{id}/runs Returns the run history for a specific automation, ordered by start time with the most recent run first. Use this endpoint to debug automation failures or audit execution history.

Path parameters

string
required
The unique identifier of the automation whose run history you want to retrieve (e.g. auto_01GHI).

Query parameters

integer
default:"1"
The page number to retrieve.
integer
default:"20"
The number of runs to return per page. Maximum is 100.

Example request

Example response

200

Response fields

array
An array of run objects for the automation.
object
Pagination metadata.