Update automation
PATCH /api/v3/automations/{id}
Request conventions
API key or OAuth2 access token. See Authentication.
Use your account domain and token in copied requests. Request values and conditional fields must satisfy your account’s validation rules.
URL settings
The part before .aha.io. Leave blank to use the example domain.
ID of the automation
Request fields
Send only the fields you want to change inside a JSON record object. This applies to both PUT and PATCH.
Only writable fields for this endpoint are listed. Required flags reflect the endpoint schema; record and workspace validation also applies.
| Field | Type | Response field |
|---|---|---|
Name of the record. | string | name |
Accepted value shape and constraintsType: | ||
Trigger kind of the automation. | string | trigger_kind |
Accepted value shape and constraintsType: Allowed values: "field_changed", "record_created", "delayed_field_changed" Allowed values: | ||
The field that will cause the automation to trigger for field_changed automations. | string | trigger_field |
Accepted value shape and constraintsType: Allowed values: "name", "status", "team_status", "type", "initiative", "assigned_to_user", "created_by_user", "epic", "end_date", "start_date", "tags", "goals", "key_results", "score", "release", "watchers", "team", "iteration", "record_risk", "progress", "initial_estimate", "detailed_estimate", "record_links", "custom_field", "owner", "release_date", "development_started_on", "external_release_date", "initiatives", "roll_up_initiative", "time_frame", "rollup_goals", "target_metric", "starting_metric", "current_metric", "duplicate_idea", "categories", "visibility", "num_endorsements", "num_organizations", "submitted_idea_portal", "parent", "collections", "task_status", "due_date", "approval_groups", "assignees" Allowed values: | ||
ID of the custom field definition id associated with the automation if trigger_field is custom_field. | string | custom_field_definition |
Accepted value shape and constraintsType: Submit | ||
Values that will be used to compare against the trigger field to determine if the automation should trigger. | array | values |
Accepted value shape and constraintsType: Array item shapeType: | ||
The operation to use to determine if the automation should trigger. | string | change_type |
Accepted value shape and constraintsType: Allowed values: "specific", "any", "=", "add", "remove", ">", "<", "current", "present", "blank", "present_with_comment", "parking_lot", "non_parking_lot" Allowed values: | ||
Additional field information when using the record_links trigger_field. | string | link_filter_type |
Accepted value shape and constraintsType: Allowed values: "link_type", "linked_record", "linked_record_status" Allowed values: | ||
The worksheet row of a worksheet custom field if applicable. | string | field_worksheet_row |
Accepted value shape and constraintsType: | ||
Whether the automation is enabled. | boolean | enabled |
Accepted value shape and constraintsType: | ||
A list of additional conditions that must be met for the automation to trigger. | array | trigger_conditions |
Accepted value shape and constraintsType: Array item shapeType: Supported shape 1Type: Supported shape 2Type: fieldType: valuesType: Array item shapeType: change_typeType: field_worksheet_rowType: custom_field_definitionCustomFieldDefinition Type: idType: nameType: internal_nameType: keyType: typeType: Allowed values: "text", "note", "number", "date", "url", "checkbox", "attachment", "predefined_choice_list", "editable_choice_list", "predefined_tags", "tags", "conditional_choice", "scorecard", "worksheet", "many_to_many_relationship", "many_to_one_relationship", "one_to_many_relationship", "users", "workspaces", "goals", "initiatives", "key_results", "releases", "epics", "features", "ideas", "idea_categories", "organizations", "idea_created_by", "competitors", "personas", "creative_briefs" record_typeType: Allowed values: "project", "feature", "epic", "requirement", "release", "release_phase", "initiative", "goal", "key_result", "idea", "idea_endorsement", "idea_organization", "idea_user", "creative_brief", "persona", "competitor", "capacity_investment", "team", "program_increment", "task", "document", "study", "interview", "custom_table" custom_tableCustomObjectDefinition Type: idType: nameType: keyType: created_atType: updated_atType: descriptionNote Type: idType: bodyType: editor_versionType: created_atType: updated_atType: prefixType: suffixType: use_delimitersType: labelType: displayType: Allowed values: "plain_text", "colored_labels" scopeType: Allowed values: "account", "project_line", "project", "related" supported_file_typesType: Array item shapeType: linked_custom_tableCustomObjectDefinition Type: idType: nameType: keyType: created_atType: updated_atType: project_scopeType: Allowed values: "account", "project" scoring_systemScoringSystem Type: idType: nameType: created_atType: updated_atType: | ||
Response fields
Choose which fields to include in the response. Expand a field for examples and associated fields. Collections can only be returned on the top-level resource, not inside an associated resource.
Default response fields are returned until you select specific fields.
| Field | Type | Returned by default |
|---|---|---|
Unique record ID. | integer | Yes |
Name of the record. | string | Yes |
Trigger kind of the automation. | string | No |
Allowed values: | ||
What record type the automation is for. | string | No |
Allowed values: | ||
The field that will cause the automation to trigger for field_changed automations. | string | No |
Allowed values: | ||
Custom field definition ID associated with the automation if trigger_field is custom_field. | CustomFieldDefinition | No |
Expand this association to browse its response fields. | ||
Custom table ID associated with the automation if trigger_record_type is custom_table. | CustomObjectDefinition | No |
Expand this association to browse its response fields. | ||
Values that will be used to compare against the trigger field to determine if the automation should trigger. | array | No |
The operation to use to determine if the automation should trigger. | string | No |
Allowed values: | ||
Additional field information when using the record_links trigger_field. | string | No |
Allowed values: | ||
The worksheet row of a worksheet custom field if applicable. | string | No |
Whether the automation is enabled. | boolean | No |
Run count of the automation. | integer | No |
Date and time when the record was created. | date-time | No |
Date and time when the record was last updated. | date-time | No |
Workspace on which the automation runs. | AutomationTarget | No |
Expand this association to browse its response fields. | ||
A list of additional conditions that must be met for the automation to trigger. Omitted by default. Request the field for inline records with default sub-fields, or choose sub-fields (e.g., ?fields=trigger_conditions[default]). Capped at 25 records. Only available on the top-level resource. | Collection | No |
Collection envelopeRecords use the associated fields below. Type: Required properties: records, has_more. urlType: has_moreType: next_urlType: Expand this association to browse its response fields. | ||
Logs associated with the automation. Omitted by default. Request the field for inline records with default sub-fields, or choose sub-fields (e.g., ?fields=logs[default]). Capped at 25 records. Only available on the top-level resource. | Collection | No |
Collection envelopeRecords use the associated fields below. Type: Required properties: records, has_more. urlType: has_moreType: next_urlType: Expand this association to browse its response fields. | ||
Search matches the start of a field path and includes matching associations’ subfields. Use a dotted path to search within a specific association.
Response field selection
Create and update responses also include fields submitted in the record body. Submitted association IDs return their associated response fields.
Return selected fields with a comma-separated fields parameter, or add a field to the defaults with fields=default,{field}. Expand an association above for its supported subfields and selection examples.
See field selection for details.
Response statuses
Error shape for 400, 401, 403, 404, 409
Type: object
error
Type: object
Required properties: status, code, message, request_id.
status
Type: integer
code
Type: string
message
Type: string
request_id
Type: string
Error shape for 422
Type: object
error
Type: object
Required properties: status, code, message, details, request_id.
status
Type: integer
Allowed values: 422
code
Type: string
Allowed values: "record.validation_failed", "record.cannot_delete"
message
Type: string
details
Type: array
Array item shape
Type: object
field
Type: string
message
Type: string
code
Type: string
request_id
Type: string
Response envelope and pagination
record: a single record. Fields are documented above.