Automations
Personal Access Token.
A successful response.
Automation represents a unit of executable code with associated metadata and dependencies. Automations can be in DRAFT or PUBLISHED state, where drafts can be modified and published automations are immutable and executable. Automation IDs are unique nano ID strings (21 characters, URL-safe: A-Za-z0-9_-).
Human-readable name of the automation for identification and display. Must be unique within the user's namespace.
User-facing English description code that explains what the automation does. This is a human-readable representation of the automation's purpose and logic.
SPy (Subset-of Python) executable code that defines the automation logic. This code is executed when the automation is invoked with inputs.
Timestamp when the automation was originally created. This value never changes after creation.
Timestamp when the automation was last updated. Updated whenever the automation metadata, code, or dependencies change.
The ID of the user who last updated this automation.
Timestamp when the automation was deleted.
Timestamp when the automation will be purged.
Provides additional context and documentation about the automation's purpose and behavior.
The ID of the user who created this automation.
Timestamp when the automation was restored from a previous version. Only populated if the automation has been restored.
The version string this automation was restored from (e.g., "1.0", "2.1"). Only populated if the automation has been restored.
The ID of the user who restored this automation. Only populated if the automation has been restored.
Timestamp when the automation was last published. Only populated if the automation has been published.
The ID of the user who last published this automation. Only populated if the automation has been published.
Activation state of a published automation. Controls whether the automation can execute published runs.
- AUTOMATION_ACTIVATION_STATE_UNSPECIFIED: Unspecified state. Used when automation has no published version. Activation state is only meaningful after publishing.
- AUTOMATION_ACTIVATION_STATE_ACTIVE: Automation is active and can execute published runs.
- AUTOMATION_ACTIVATION_STATE_DEACTIVATED: Automation is deactivated and cannot execute published runs. Events will be logged but not executed.
AUTOMATION_ACTIVATION_STATE_UNSPECIFIEDPossible values: List of output keys that have been marked by the user. These keys identify specific outputs from the automation execution.
An unexpected error response.
Personal Access Token.
The publication stage of the automation to retrieve. Determines which version of the automation to return:
-
AUTOMATION_STAGE_DRAFT: Returns the latest draft version
-
AUTOMATION_STAGE_PUBLISHED: Returns the latest published version
-
AUTOMATION_STAGE_UNSPECIFIED: Automation stage is not specified.
-
AUTOMATION_STAGE_DRAFT: Automation is in draft stage and can be modified.
-
AUTOMATION_STAGE_PUBLISHED: Automation is published and immutable, ready for execution.
AUTOMATION_STAGE_UNSPECIFIEDPossible values: A successful response.
Automation represents a unit of executable code with associated metadata and dependencies. Automations can be in DRAFT or PUBLISHED state, where drafts can be modified and published automations are immutable and executable. Automation IDs are unique nano ID strings (21 characters, URL-safe: A-Za-z0-9_-).
Human-readable name of the automation for identification and display. Must be unique within the user's namespace.
User-facing English description code that explains what the automation does. This is a human-readable representation of the automation's purpose and logic.
SPy (Subset-of Python) executable code that defines the automation logic. This code is executed when the automation is invoked with inputs.
Timestamp when the automation was originally created. This value never changes after creation.
Timestamp when the automation was last updated. Updated whenever the automation metadata, code, or dependencies change.
The ID of the user who last updated this automation.
Timestamp when the automation was deleted.
Timestamp when the automation will be purged.
Provides additional context and documentation about the automation's purpose and behavior.
The ID of the user who created this automation.
Timestamp when the automation was restored from a previous version. Only populated if the automation has been restored.
The version string this automation was restored from (e.g., "1.0", "2.1"). Only populated if the automation has been restored.
The ID of the user who restored this automation. Only populated if the automation has been restored.
Timestamp when the automation was last published. Only populated if the automation has been published.
The ID of the user who last published this automation. Only populated if the automation has been published.
Activation state of a published automation. Controls whether the automation can execute published runs.
- AUTOMATION_ACTIVATION_STATE_UNSPECIFIED: Unspecified state. Used when automation has no published version. Activation state is only meaningful after publishing.
- AUTOMATION_ACTIVATION_STATE_ACTIVE: Automation is active and can execute published runs.
- AUTOMATION_ACTIVATION_STATE_DEACTIVATED: Automation is deactivated and cannot execute published runs. Events will be logged but not executed.
AUTOMATION_ACTIVATION_STATE_UNSPECIFIEDPossible values: List of output keys that have been marked by the user. These keys identify specific outputs from the automation execution.
An unexpected error response.
Personal Access Token.
A successful response.
AutomationRevision represents a historical revision (version) of an automation. Revisions are immutable snapshots created each time an automation is updated. Per AIP-162, this resource contains the complete state via a snapshot field.
The name of the automation revision. Format: organizations/{organization}/workspaces/{workspace}/automations/{automation}/revisions/{revision} The revision ID is the semantic version string (e.g., "0.1", "1.0", "2.0").
Timestamp when this revision was created.
Other revision IDs that reference the same snapshot (e.g., "latest"). Per AIP-162, this allows aliases for revisions.
An unexpected error response.
Personal Access Token.
The maximum number of revisions to return in a single response. The service may return fewer than this value. If unspecified, at most 50 revisions will be returned. The maximum value is 1000; values above 1000 will be coerced to 1000.
A page token received from a previous ListAutomationRevisions call.
Provide this to retrieve the subsequent page of results.
Filter expression to restrict results. Per AIP-160, this should be a filtering expression following the Common Expression Language (CEL) syntax.
Supported fields for filtering:
stage: The automation revision stage (e.g., DRAFT, PUBLISHED)
Example filters:
stage = "DRAFT"- Returns only draft revisionsstage = "PUBLISHED"- Returns only published revisions
If not specified or passed null, all revisions will be returned for that automation.
A successful response.
ListAutomationRevisionsResponse returns a page of automation revisions and pagination information.
A token that can be sent as page_token to retrieve the next page.
If this field is omitted, there are no subsequent pages.
An unexpected error response.
Personal Access Token.
The maximum number of automations to return in a single response. The service may return fewer than this value. If unspecified, at most 10 automations will be returned. The maximum value is 1000; values above 1000 will be coerced to 1000. If negative, an INVALID_ARGUMENT error will be returned.
A page token received from a previous ListAutomations call.
Provide this to retrieve the subsequent page of results.
When paginating, all other parameters provided to ListAutomations must match
the call that provided the page token.
Filter to show/hide deleted automations. Deleted automations will be hidden by default.
Filter expression to restrict results. Per AIP-160, this should be a filtering expression following the Common Expression Language (CEL) syntax.
Supported fields for filtering:
state: The automation state (e.g., DRAFT, PUBLISHED)
Example filters:
state = "PUBLISHED"
Reserved for future use. Comma-separated list of fields to order results by. Per AIP-132, this should be a string containing one or more field names, each optionally followed by "asc" or "desc" to specify sort direction.
Currently not implemented. Results are always ordered by update_time desc
(most recently updated first).
A successful response.
ListAutomationsResponse returns a page of automations and pagination information.
A token that can be sent as page_token to retrieve the next page.
If this field is omitted, there are no subsequent pages.
An unexpected error response.
Personal Access Token.
InvokeAutomationRequest contains the automation ID and inputs needed to execute an automation.
AutomationStage represents the publication stage of an automation. This enum is shared across services that manage or execute automations.
- AUTOMATION_STAGE_UNSPECIFIED: Automation stage is not specified.
- AUTOMATION_STAGE_DRAFT: Automation is in draft stage and can be modified.
- AUTOMATION_STAGE_PUBLISHED: Automation is published and immutable, ready for execution.
AUTOMATION_STAGE_UNSPECIFIEDPossible values: A successful response.
InvokeAutomationResponse returns the run ID for tracking the automation execution.
Unique identifier of the run created to execute the automation. Use this ID to track execution status and retrieve results.
An unexpected error response.
Personal Access Token.
Maximum number of entries to return. Defaults to 50 if not specified.
Page token for pagination, from a previous ListDefaultInputsHistoryResponse.
A successful response.
ListDefaultInputsHistoryResponse contains a paginated list of default input history entries.
Token for retrieving the next page. Empty if no more results.
An unexpected error response.
Personal Access Token.
CountConnectionUsageRequest specifies connection IDs to count automation usage for.
List of connection IDs to count automation usage for. Each connection ID will have a corresponding entry in the response.
A successful response.
CountConnectionUsageResponse returns automation counts for each requested connection ID.
An unexpected error response.
Personal Access Token.
TraceConnectionUsageRequest specifies which connection to trace usage for.
The connection ID to trace usage for. Returns all automations that use this connection.
A successful response.
TraceConnectionUsageResponse returns automations that use the specified connection.
An unexpected error response.
Personal Access Token.
Filter expression to restrict results. Per AIP-160, this should be a filtering expression following the Common Expression Language (CEL) syntax.
Supported fields for filtering:
stage: The automation stage to extract connections from (e.g., DRAFT, PUBLISHED)
Example filters:
stage = "DRAFT"stage = "PUBLISHED"
A successful response.
ExtractAutomationCodeConnectionsResponse returns connection information from the automation's SPy code.
An unexpected error response.
Personal Access Token.
UpgradeAutomationConnectionsRequest specifies which connections to upgrade in a draft automation.
A successful response.
UpgradeAutomationConnectionsResponse returns the updated automation.
An unexpected error response.
Personal Access Token.
SwitchAutomationConnectionsRequest specifies which connections to switch in a draft automation.
A successful response.
SwitchAutomationConnectionsResponse returns the updated automation.
An unexpected error response.
Personal Access Token.
RemoveAutomationConnectionsRequest specifies which connections to remove from a draft automation.
A successful response.
RemoveAutomationConnectionsResponse returns the updated automation.
An unexpected error response.
Personal Access Token.
AddAutomationConnectionsRequest specifies which connections to add to a draft automation.
A successful response.
AddAutomationConnectionsResponse returns the updated automation.
An unexpected error response.
Personal Access Token.
A successful response.
AutomationVisualization represents a visual representation of an automation's execution flow. Visualizations are generated for published automation versions and stored as configurations for rendering in the UI. This is a singleton resource - each automation has exactly one visualization representing its latest published version.
The semantic version of the automation this visualization represents. Format: "major.0" (e.g., "1.0", "2.0", "3.0") - always a published version. This corresponds to the automation's published version at the time of generation.
VisualizationState indicates the current state of visualization generation.
- VISUALIZATION_STATE_UNSPECIFIED: Unspecified state.
- VISUALIZATION_STATE_PENDING: Visualization generation is in progress.
- VISUALIZATION_STATE_COMPLETED: Visualization generation completed successfully.
- VISUALIZATION_STATE_FAILED: Visualization generation failed.
VISUALIZATION_STATE_UNSPECIFIEDPossible values: Error message describing why generation failed. Only populated when state is VISUALIZATION_STATE_FAILED.
An unexpected error response.
Personal Access Token.
A successful response.
AutomationSchedule represents a schedule for invoking an automation. Each automation can have at most one schedule. Kestra is the source of truth.
Whether the schedule is currently enabled. Disabled schedules do not trigger automation invocations.
List of the next scheduled execution times. Useful for preview and verification. Backend generates these.
Number of remaining occurrences if the schedule has an end condition. Only populated when config.end.end_type is SCHEDULE_END_TYPE_AFTER_OCCURRENCES.
An unexpected error response.
Personal Access Token.
AutomationSchedule represents a schedule for invoking an automation. Each automation can have at most one schedule. Kestra is the source of truth.
Whether the schedule is currently enabled. Disabled schedules do not trigger automation invocations.
List of the next scheduled execution times. Useful for preview and verification. Backend generates these.
Number of remaining occurrences if the schedule has an end condition. Only populated when config.end.end_type is SCHEDULE_END_TYPE_AFTER_OCCURRENCES.
A successful response.
AutomationSchedule represents a schedule for invoking an automation. Each automation can have at most one schedule. Kestra is the source of truth.
Whether the schedule is currently enabled. Disabled schedules do not trigger automation invocations.
List of the next scheduled execution times. Useful for preview and verification. Backend generates these.
Number of remaining occurrences if the schedule has an end condition. Only populated when config.end.end_type is SCHEDULE_END_TYPE_AFTER_OCCURRENCES.
An unexpected error response.
Personal Access Token.
A successful response.
An unexpected error response.
Personal Access Token.
Whether the schedule is currently enabled. Disabled schedules do not trigger automation invocations.
List of the next scheduled execution times. Useful for preview and verification. Backend generates these.
Number of remaining occurrences if the schedule has an end condition. Only populated when config.end.end_type is SCHEDULE_END_TYPE_AFTER_OCCURRENCES.
A successful response.
AutomationSchedule represents a schedule for invoking an automation. Each automation can have at most one schedule. Kestra is the source of truth.
Whether the schedule is currently enabled. Disabled schedules do not trigger automation invocations.
List of the next scheduled execution times. Useful for preview and verification. Backend generates these.
Number of remaining occurrences if the schedule has an end condition. Only populated when config.end.end_type is SCHEDULE_END_TYPE_AFTER_OCCURRENCES.
An unexpected error response.
Personal Access Token.
DisableAutomationScheduleRequest is the request to disable a schedule (pause without deleting).
A successful response.
DisableAutomationScheduleResponse contains the disabled schedule.
An unexpected error response.
Personal Access Token.
EnableAutomationScheduleRequest is the request to enable a previously disabled schedule.
A successful response.
EnableAutomationScheduleResponse contains the enabled schedule.
An unexpected error response.
Personal Access Token.
The connection ID to delete.
A successful response.
DeleteWorkspaceConnectionResponse returns information about affected automations.
An unexpected error response.
Personal Access Token.
The maximum number of triggers to return in a single response. The service may return fewer than this value. If unspecified, a default page size will be used.
A page token received from a previous ListAutomationTriggers call.
Provide this to retrieve the subsequent page of results.
A filter expression to apply to the list of triggers.
A successful response.
Response containing the list of active triggers for an automation.
A token that can be sent as page_token to retrieve the next page.
If this field is omitted, there are no subsequent pages.
An unexpected error response.
Personal Access Token.
AutomationTrigger represents phase configuration metadata for an external trigger. The trigger itself is created and managed by another service; this message stores additional metadata about how the trigger relates to automation phases.
The external trigger ID created by another service. This ID uniquely identifies the trigger in the external system.
PhaseType defines the type of phase for an automation trigger.
- PHASE_TYPE_UNSPECIFIED: Unspecified phase type.
- PHASE_TYPE_PRE: Pre-processing phase.
- PHASE_TYPE_MAIN: Main processing phase.
- PHASE_TYPE_POST: Post-processing phase.
PHASE_TYPE_UNSPECIFIEDPossible values: PhaseSubType defines the sub-type within a phase for an automation trigger.
- PHASE_SUB_TYPE_UNSPECIFIED: Unspecified phase sub-type.
- PHASE_SUB_TYPE_EMAIL: Email trigger sub-type.
- PHASE_SUB_TYPE_SCHEDULE: Schedule-based trigger sub-type.
- PHASE_SUB_TYPE_WEBHOOK: Webhook trigger sub-type.
- PHASE_SUB_TYPE_API: API trigger sub-type.
PHASE_SUB_TYPE_UNSPECIFIEDPossible values: Whether this trigger is currently active.
A successful response.
AutomationTrigger represents phase configuration metadata for an external trigger. The trigger itself is created and managed by another service; this message stores additional metadata about how the trigger relates to automation phases.
The external trigger ID created by another service. This ID uniquely identifies the trigger in the external system.
PhaseType defines the type of phase for an automation trigger.
- PHASE_TYPE_UNSPECIFIED: Unspecified phase type.
- PHASE_TYPE_PRE: Pre-processing phase.
- PHASE_TYPE_MAIN: Main processing phase.
- PHASE_TYPE_POST: Post-processing phase.
PHASE_TYPE_UNSPECIFIEDPossible values: PhaseSubType defines the sub-type within a phase for an automation trigger.
- PHASE_SUB_TYPE_UNSPECIFIED: Unspecified phase sub-type.
- PHASE_SUB_TYPE_EMAIL: Email trigger sub-type.
- PHASE_SUB_TYPE_SCHEDULE: Schedule-based trigger sub-type.
- PHASE_SUB_TYPE_WEBHOOK: Webhook trigger sub-type.
- PHASE_SUB_TYPE_API: API trigger sub-type.
PHASE_SUB_TYPE_UNSPECIFIEDPossible values: Whether this trigger is currently active.
An unexpected error response.
Last updated
Was this helpful?

