AUTO: Automation
A workflow automation rule with trigger event, target object type, filters, and actions.
Default definition. This article describes the default
AUTO definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches AUTO.Entity properties
| Property | Value |
|---|---|
| Entity code | AUTO |
| Display name | Automation |
| Plural | Automations |
| Level | 11000 |
Use cases
System entity for defining automation rules. Three-column layout: left (20%) has basics (name, description, active checkbox, event trigger indexedSelect for approval/new/update/delete, target object type via entityList-enabled indexedSelect), middle (40%) has filters displayed via autofilterarray row type linking to AUTOFILTER entity, right (40%) has actions displayed via autoactionarray row type linking to AUTOACTION entity. The entityList: true flag on the object field dynamically populates options from all available entity types. Supports bulk actions.
Fields
General: Basics
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Automation name. |
description | text (multi-line) | Description. | |
active | boolean | Active. | |
event | enum | Yes | Event. Valid ids: approval (Approve new object), new (Create new object), update (Update object), delete (Delete object). |
object | enum | Yes | Object. |
Relationships
- No declared relationships in the default definition.
Creating a Automation via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "AUTO",
"level": 11000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Automation name",
"event": "approval",
"object": "Object",
"description": "Description"
}Listing Automations records
GET /v1/entities/AUTO/SUB