Add to list

Adds a value to an account list, optionally with an expiration.

Configuration	Content
List	list existing in the account
Source: Value	an event field (Field) or an expression (Expression)
Setting: Expires in	30m, 12h, 1d; minimum 5m, maximum 2 years; blank = permanent

In Field mode, the value comes from a text, list, numeric, boolean, or date and time field. In Expression mode, the value follows the action syntax: a field, a temporary variable, a concat, a split, a join, or a fixed value. The expression can build, for example, a composite key:

Add to list → concat($user_id, "-", $merchant_id) to @blocked_pairs, expires in 1d

The added value is a single value, converted to text. A set, such as %bot.triggered_cells, is rejected when the rule is saved, as is a fixed value outside the format the list accepts.

With this action the rule incorporates what it has already observed. A condition detects the behavior and writes to the list, and the following events check that list with an ordinary condition:

Event 1, condition:  "email_velocity" in %bot.triggered_cells
         action:     Add to list → $user_email to @blocked_emails, expires in 1d

Event 2, condition:  $user_email in @blocked_emails
         action:     Set field → blocked = "true"

With an expiration, recovery becomes an explicit policy: the entry leaves the list when it expires, instead of depending on the window of the analysis that originated it.

Points to consider:

• A repeat does not duplicate: adding a value that is already on the list only renews its expiration.
• Invalid values are ignored: a blank value, or one outside the format the list accepts, is not added and does not interrupt processing.
• Removal is periodic: sweeps every few minutes remove expired entries. An entry may keep counting a little past its expiration, and that is why the minimum expiration is 5 minutes.
• Full lists stop growing: once the item limit is reached, new values stop being added, but existing ones keep being renewed. See limits and parameters.

Because it changes data outside the event, this action is skipped during a simulation: the simulator does not write to the list.