Platform Automations: triggers, actions, and pipeline steps reference
Use this reference to understand the fields you set when creating or editing a platform automation and its pipeline steps, which fields are required, and which cannot be changed.
Automation fields
Automation Name: a descriptive name for the automation. Required.
Trigger Type: the event that starts the automation, chosen in Select Trigger Type. Set at creation and read-only afterwards (Trigger type cannot be changed after creation).
Enabled: turns the automation on or off. A disabled automation is never triggered.
Fields of single-action triggers
These fields appear only for the triggers that use them:
Add to Groups: the groups new users (New User) or new team managers (User promoted Team Manager) are added to.
Groups to Remove: the groups demoted team managers lose (User demoted Team Manager).
When assigned to any of the Group(s): the groups that start the automation when a user is added to any of them (User assigned to Group).
Assign to Career and Career Category: the career and category assigned by User assigned to Group. Both are required. Shown when the Evaluation module is enabled.
Assigned to Team(s): the teams that start the automation when a user is added to any of them (User assigned to Team). Required. Shown when the Teams module is enabled.
Assign to Group(s): the groups a user is added to when they join one of those teams.
Older onboarding automations created before the onboarding trigger became multi-step may still show Delay (in days) (days after the user hire date, 0 or more) and Select Onboarding Form.
Pipeline step fields
Multi-step triggers have a Pipeline Steps section in the automation form. Each step has a Step Type: Delay, Send Email, or Push Notification. A trigger only offers the steps it allows.
Delay
Duration: how long to wait. Required, at least 1.
Unit: Seconds, Minutes, Hours, or Days. Required.
Relative to: an optional reference offered by the trigger, such as the user hire date. Choose Not relative (absolute delay) to simply wait the duration.
Send Email
Recipient: who receives the email, chosen from the recipients the trigger offers. Required.
Subject and Body: written per language on the language tabs. Required for the first (default) language.
Allowed variables: template variables you can insert into the subject or body. They are replaced with real values when the email is sent.
Add linked content: inserts a link to an article, community, or form into the body.
Push Notification
Recipient: who receives the notification. Required.
Title and Body: written per language. Required for the first (default) language.
Show in in-app notifications center: when on, the notification also appears in the user's in-app notifications center.
Linked content: an optional link to an item of Articles & News, Communities, or Forms. Tapping the notification opens it in the app. Each option appears only when its module is enabled.
How validation works
Required fields are checked when you save. If a field is missing or invalid, a message is shown next to it; complete it and save again. In email and push steps, a variable the trigger does not offer is flagged as Unknown variable, and unbalanced braces as Malformed tag detected. If you leave some languages empty, you are asked Do you want to proceed?, and the default language text is used for the missing languages. Steps are saved when you save the automation with Create or Update. You can review the result any time in Automation Details, where the trigger, the pipeline, and the status are shown together.