Get an automation rule
Retrieve a single automation rule. Requires administrator access to the project. Use it when you need the full definition of one rule, for example before changing it.
Retrieve a single automation rule. Requires administrator access to the project. Use it when you need the full definition of one rule, for example before changing it.
Authenticate as a user with a personal access token.
Send it as a bearer token in the Authorization header:
Authorization: Bearer <personal-access-token>Personal access tokens act on behalf of the user that created them and are required by endpoints that perform user actions, such as reviewing builds and posting comments.
In: header
Path Parameters
1 <= length1 <= lengthIdentifier of the automation rule.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/projects/string/string/automation-rules/string"{ "id": "string", "name": "string", "active": true, "events": [ "build.completed" ], "conditions": [ { "type": "build-branch", "value": "string" } ], "actions": [ { "action": "string", "actionPayload": { "property1": null, "property2": null } } ], "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z"}Create an automation rule POST
Create an automation rule on a project. Requires administrator access to the project. Action targets must belong to the project's account. Use it when the user wants a project to react automatically to build events, for example by posting to Slack.
Update an automation rule PUT
Replace an automation rule's definition. Requires administrator access to the project. The whole definition is replaced, so send the events, conditions and actions you want the rule to end up with. Use it when an existing rule should fire on different events, conditions or actions.