AUTOACTION: Automation
An automation action (email, update, create object, approval) with type-specific configuration.
Default definition. This article describes the default
AUTOACTION 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 AUTOACTION.Entity properties
| Property | Value |
|---|---|
| Entity code | AUTOACTION |
| Display name | Automation |
| Plural | Automations |
| Level | 11000 |
Use cases
System entity for automation actions within the AUTO workflow system. Three-column layout: left (25%) has action name and type indexedSelect (emailAddress/emailUser/emailFieldSingle/emailApprovalUser/updateProperty/updatePropertyCount/updateRelated/createObject/updateObject/approval/updateStory/hubspotCreate), middle (25%) has type-dependent configuration fields with extensive visibility conditions (email fields, property/value fields, related object fields, JSON config), right (50%) has createobjectconfig row type for object creation setup.
Fields
General: Action
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name. |
type | enum | Yes | Type. Valid ids: emailAddress (Send email to an supplied address), emailUser (Send email to a user), emailFieldSingle (Email user from field), emailFieldAddress (Send email to field address), emailApprovalUser (Send approval email to user), updateProperty (Update an object property), updatePropertyCount (Update an object property to a count), updateRelated (Update related object), createObject (Create a new object), updateObject (Update an object), approval (Create approval workflow), updateStory (Update story status and assignees), hubspotCreate (Create a HubSpot record), triggerFlow (Trigger an integration flow). |
General: Configuration
| Field | Type | Required | Notes |
|---|---|---|---|
address | text | Email address. | |
flowId | reference → INTFLOW | Yes | Flow to trigger when this automation fires. Receives full before/after object snapshots. reference them in steps via {{trigger.after.field}}, {{trigger.objectId}}, {{trigger.entity}}, {{trigger.eventType}}. |
user | reference → user | Recipient user. | |
userField | text | Object field (eg. user) or related object field (eg. prRequest.ownerId) | |
subject | text | Email subject. | |
message | text (HTML) | Email message. | |
related | entityObjectLookups | Related field. | |
p | text | Property. | |
v | text | Fixed Value. | |
vprop | text | Property Value. | |
objectId | text | The ID of the object to update (leave blank to use Object field instead) | |
objectField | text | Field on the trigger object that contains the target object ID (e.g. projectId) | |
hubspotObject | enum | HubSpot object type. Valid ids: companies (Companies), contacts (Contacts), deals (Deals). | |
object | text (multi-line) | JSON object of fixed field values, e.g. {"entity":"TASK","status":"open"} | |
properties | text (multi-line) | JSON object of fixed HubSpot property values, e.g. {"lifecyclestage":"customer"} | |
values | text (multi-line) | JSON object of fixed field values to set, e.g. {"status":"approved"} | |
variable | text (multi-line) | JSON array of property mappings from trigger object, e.g. ["name", {"from":"ownerId","to":"assignee"}] |
Relationships
- Lookups:
flowIdpoints at aINTFLOWrecord.
Creating a Automation via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "AUTOACTION",
"level": 11000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Name",
"type": "emailAddress",
"flowId": "",
"address": "Email address"
} Listing Automations records
GET /v1/entities/AUTOACTION/SUB