---
title: Record Event Triggers (Classic)
slug: record-event-triggers-classic
docTags: 
createdAt: 2025-08-11T11:13:46.000Z
---

A record event trigger initiates a playbook whenever a record is created and/or updated within a specific application.

:::hint{type="info"}
You do not need to select a trigger before adding and configuring actions and conditions.
:::

## Record Event Triggers

Create a new playbook or upload an existing playbook, then follow the steps below:

1. On the playbook, click **Add a trigger**.
2. Click **Record Event**.
3. On **TRIGGER**, click the **Application** drop-down menu and select the desired application.
4. Select one or both of the **Record Created** or **Record Updated** check boxes.
   **Record Created** — triggers the playbook whenever a record is *created* in the specified application.
   **Record Updated** — triggers the playbook whenever a record is *updated* in the specified application.
   **Both** — triggers the playbook whenever a record is *created* and/or *updated* in the specified application.

   ::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/0z4rZQNwhXROpCKp9bNVM_record-event-trigger.png" size="30" width="400" height="700" darkWidth="800" darkHeight="1400" position="center" showCaption="false"}
5. If needed, click **Configure** to map available playbook inputs to the created and/or updated record.
6. Open the **Filter** tab to set conditions for your trigger.
7. Click **CREATE YOUR FIRST CONDITION** and select the property type from the **Record Event Trigger**.
8. Select the type of condition from the drop-down next to **MATCHES**.
9. Enter the property type or select a property.
10. Click **Apply**.

    ::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/eu8_OMHFnwqujt7ePujsH_filteringrecords.png" size="50" width="1091" height="635" darkWidth="800" darkHeight="465" position="center" showCaption="false"}

:::hint{type="info"}
**Note:** In Record Updated event triggers, the `user.userName` field currently returns the user’s email address instead of the configured Username value. This is a known issue and is currently expected behavior.
:::

##