Delete Automation

Delete Automation

Permanently delete an automation from your project. This removes the automation, its trigger, all associated actions, and cleans up any scheduled jobs or caches. This action cannot be undone.

Basic Example

mutation DeleteAutomation {
  deleteAutomation(id: "automation_abc123")
}

Advanced Example

mutation DeleteAutomationWithAlias {
  removeWorkflow: deleteAutomation(id: "automation_abc123")
  removeNotifier: deleteAutomation(id: "automation_def456")
}

Input Parameters

Response Fields

Required Permissions

Only owners and admins of an active project can delete automations.

Error Responses

Authentication Required

{
  "errors": [{
    "message": "You must be logged in",
    "extensions": {
      "code": "UNAUTHENTICATED"
    }
  }]
}

When: No valid authentication token is provided.

Unauthorized

{
  "errors": [{
    "message": "Unauthorized",
    "extensions": {
      "code": "UNAUTHORIZED"
    }
  }]
}

When: The authenticated user does not have OWNER or ADMIN access to the project, or the project is archived.

Automation Not Found

{
  "errors": [{
    "message": "Automation not found",
    "extensions": {
      "code": "NOT_FOUND"
    }
  }]
}

When: The specified id does not exist or belongs to a different project.

Important Notes

• Permanent Action: Deletion is irreversible – the automation and all its configuration are permanently removed
• Schedule Cleanup: If the automation has an active schedule, it is automatically unscheduled before deletion
• Due Date Cleanup: For DUE_DATE_EXPIRED triggers, all associated monitoring jobs are removed for both regular todo due dates and custom field due dates
• Cache Cleanup: For CONDITIONAL automations, the evaluation cache is invalidated upon deletion
• Batch Deletion: You can delete multiple automations in a single request using GraphQL aliases as shown in the advanced example
• Subscription Notification: A deletion event is published to subscribers, notifying any connected clients