For the complete documentation index, see llms.txt. This page is also available as Markdown.

Actions

What an automation can do to a user: send an email, change segment membership, push to a feed, or run a custom action.

What an action is

An action node does something to or for the user travelling through it. Actions are found in the Automation Components drawer on the right of the builder: drag the one you want into the path of your automation, and you are asked to configure it. Click it later to edit its configuration or remove it.

Once a user goes through an action node, the action is triggered asynchronously and the user moves on to the next node.

The catalogue

Action
What it does
Maturity

Sends an email to the user.

-

Adds the user to a list segment.

-

Removes the user from a list segment.

-

Pushes the user into a feed.

Alpha

Triggers a customised action - a push notification, a read or write in a CRM.

-

Send email

The configuration comes in these parts.

1

The campaign and its provider

  • Campaign name. The name for the campaign.

  • Provider. The opt-in provider, which helps you target users who gave explicit consent to email targeting. Contact your Account Manager to update your list of providers.

2

The email itself

Basic information: subject, from email, from name, and so on.

3

The template

Choose one among your email templates.

Frequency capping

That default is deliberately conservative, and it is the single most common cause of "my automation is not sending". Do not leave it unexamined.

The settings live on the email_blast resource created by the automation, and are updated by API through the capping, capping_period and min_period_between_shoots properties:

Property
What it controls

capping

The maximum number of emails sent in this blast during the capping period.

capping_period

The period considered for capping, as an ISO 8601 duration.

min_period_between_shoots

The minimum time between two emails in the same capping period, as an ISO 8601 duration.

ISO 8601 durations read as P plus the quantity: P1D is 1 day, P7D is 7 days, P2M is 2 months. So a capping of 1 with a capping_period of P7D means at most one email per user per week from this blast.

Ask your Account Manager to update the settings, or do it yourself through the API.

Add to segment

Adding an Add to segment node causes users going through the automation to be added to a segment.

The configuration lets you choose a segment name and a time to live (TTL) - the time after which the user should leave the segment, used mainly for regulatory reasons. You can optionally link the segment to user choices.

The resulting segment is a List segment with a scenario subtype.

Delete from segment

Adding a Delete from segment node removes users going through the automation from a segment. The picker only shows list segments.

If the user does not belong to the segment, the automation moves on to the next component with no action - it does not fail or branch.

Feed

A Feed node pushes the user going through the automation into a feed. The configuration works in the same way as all other presets.

Feed nodes are only visible once you have presets configured - if the component is missing from the drawer, that is why.

Custom action

A Custom action node triggers a customised action involving the users going through the automation: sending a push notification, reading or writing information in a CRM, and so on.

If you need an action beyond the standard ones, your Account Manager can help you get started on building a custom action component.

Last updated

Was this helpful?