Automations

atlas_automations_create

Automations: create an audit-event automation rule with one trigger and one or more validated actions.

Scope

automations:write

Calls

POST /v1/automations

Example prompt

Create an automation that notifies me when a task becomes overdue.

Arguments

atlas_automations_delete

Automations: delete an automation rule by id.

Scope

automations:write

Calls

DELETE /v1/automations/{id}

Example prompt

Delete automation auto_123.

Arguments

atlas_automations_disable

Automations: disable an automation rule without deleting its configuration.

Scope

automations:write

Calls

POST /v1/automations/{id}/disable

Example prompt

Disable the stale task escalation automation.

Arguments

atlas_automations_enable

Automations: enable an automation rule so matching events can trigger it.

Scope

automations:write

Calls

POST /v1/automations/{id}/enable

Example prompt

Enable the onboarding reminder automation.

Arguments

atlas_automations_get

Automations: fetch a single automation rule by id.

Scope

automations:read

Calls

GET /v1/automations/{id}

Example prompt

Show automation auto_123.

Arguments

atlas_automations_list

Automations: list tenant automation rules, including their trigger, actions, enabled state, and operational metadata.

Scope

automations:read

Calls

GET /v1/automations

Example prompt

List our automations.

Arguments

This tool takes no arguments.

atlas_automations_run

Run one automation rule now, once, without waiting for its trigger event. The rule runs its actions in order and the run is recorded in the run history. Returns the new run id and its outcome: succeeded, partial or failed. Use this when a person asks to test a rule or to apply it immediately.

Scope

automations:write

Calls

POST /v1/automations/{id}/run

Example prompt

Run the Overdue task alert automation now.

Arguments

atlas_automations_runs_get

Read one run of an automation rule: its outcome, the event that triggered it, the result of each action step with any error, and when it started and finished. Use this after atlas_automations_runs_list to explain why a particular run failed or only partly succeeded.

Scope

automations:read

Calls

GET /automations/{id}/runs/{runId}

Example prompt

Why did the last run of the Escalate blockers automation fail?

Arguments

atlas_automations_runs_list

Automations: list recent runs for one automation rule, optionally filtered by succeeded, partial, or failed status.

Scope

automations:read

Calls

GET /v1/automations/{id}/runs

Example prompt

Show failed runs for automation auto_123.

Arguments

atlas_automations_scripts_create

Automations: create a JavaScript or Python script automation with cron, event, or webhook trigger configuration.

Scope

automations:write

Calls

POST /v1/automations/scripts

Example prompt

Create a nightly JavaScript hygiene automation.

Arguments

This tool takes no arguments.

atlas_automations_scripts_disable

Automations: deactivate a script automation without calling its public webhook.

Scope

automations:write

Calls

DELETE /v1/automations/scripts/{id}

Example prompt

Deactivate script automation script_123.

Arguments

atlas_automations_scripts_get

Automations: fetch one script automation by id.

Scope

automations:read

Calls

GET /v1/automations/scripts/{id}

Example prompt

Show script automation script_123.

Arguments

atlas_automations_scripts_list

Automations: list tenant script automations and their trigger configuration.

Scope

automations:read

Calls

GET /v1/automations/scripts

Example prompt

List script automations.

Arguments

This tool takes no arguments.

atlas_automations_scripts_run

Automations: manually run a script automation and return the accepted run receipt.

Scope

automations:write

Calls

POST /v1/automations/scripts/{id}/run

Example prompt

Run script automation script_123 now.

Arguments

atlas_automations_scripts_runs_list

Automations: list recent script automation runs, optionally filtered by queued, running, success, failed, or timeout status.

Scope

automations:read

Calls

GET /v1/automations/scripts/{id}/runs

Example prompt

Show timeout runs for script automation script_123.

Arguments

atlas_automations_scripts_update

Automations: update a script automation source, runtime settings, active state, or trigger configuration.

Scope

automations:write

Calls

PUT /v1/automations/scripts/{id}

Example prompt

Set script automation script_123 to inactive.

Arguments

atlas_automations_templates_apply

Automations: expand a workflow template into a concrete automation and install it. Pass the templateId and a params map (keyed by template param ids). Returns the new automation.

Scope

automations:write

Calls

POST /v1/automations/from-template

Example prompt

Install the late-task-escalation workflow with my manager + exec.

Arguments

atlas_automations_templates_list

Automations: list every workflow template available to install. Returns the catalog (linear + branching templates), the trigger catalog used by the custom builder, and the enum values for status/priority pickers.

Scope

automations:read

Calls

GET /v1/automations/builder/catalog

Example prompt

Show me every workflow template I can install.

Arguments

This tool takes no arguments.

atlas_automations_update

Automations: update an automation rule name, trigger, or action list. At least one mutable field is required.

Scope

automations:write

Calls

PATCH /v1/automations/{id}

Example prompt

Rename automation auto_123 to Team escalation.

Arguments

atlas_automations_versions_list

List the saved versions of one automation rule, newest first. Each version carries its number, a snapshot of the name, trigger, actions and enabled state at that point, who saved it and when. Use this to see what changed in a rule or to choose a version to restore.

Scope

automations:read

Calls

GET /v1/automations/{id}/versions

Example prompt

Show me the version history of the Weekly digest automation.

Arguments

atlas_automations_versions_restore

Restore the name, trigger and actions of an automation rule from an earlier saved version; whether the rule is enabled is left as it is. The restore is applied as a new change, so it adds a version rather than deleting any, and it can be reversed by restoring the version that was current before it. Returns the rule as it now stands.

Scope

automations:write

Calls

POST /v1/automations/{id}/revert/{version}

Example prompt

Put the Weekly digest automation back to version 3.

Arguments