triggers (automation)

Property description

The trigger asset configures what activates an automation rule. Triggers can be

• In-app and user actions (such as creating or modifying an object) or
• A scheduled event (specifying when and how often the rule should run).

Minimal JSON: Trigger

Minimal JSON

{
  "key": "",
  "type": "",
  "": [
    ""
  ]
}

Example JSON

{
  "key": "attribute_changed",
  "type": "attributeChanged",
  "attributeTypeKeys": [
    "core_summary",
    "core_description"
  ]
}

JSON 3

{
  "key": "work\uFB02ow_state_changed",
  "type": "workflowStateChanged",
  "work\uFB02owStateKeys": [
    "core_draft"
  ]
}

Nested properties

Property	Description	Values	Mandatory
key	Unique key of the trigger.	string	Yes
type	Type of the trigger. See the list of all supported trigger types.	string	Yes
“	Keys of the changed properties. The second mandatory property depends on the selected trigger type.	array of strings	Yes

Minimal JSON: Schedule

Minimal JSON

{
  "key": "",
  "type": "",
  "cronPattern": "* * * * *"
}

Example JSON

{
  "key":"schedule",
  "type":"schedule",
  "cronPattern":"1 * * * *"//Runseveryhouratminute1
}

Nested properties

Property	Description	Values	Mandatory
key	Unique key of the trigger.	string	Yes
type	schedule	string	Yes
cronPattern	Schedule of the trigger, defined by a cron pattern.	string	Yes

CRON pattern definition

The pattern is defined using the following format:

* * * * * = minute (0–59) - hour (0–23) - day of month (1–31) - month (1–12) - day of week (0–6, Sunday = 0)

• Use * to match any value (e.g., every day, every hour)
• Use */N for “every N units” (e.g., */75 = every 75 minutes)
• Use ranges like:
  • 1-5 for weekdays (Monday to Friday)
  • 1,15 for specific days (the 1st and 15th)
• Time is in 24-hour format (e.g., 14 = 2 PM)

For more information, see UNIX cron format.