Collection Item Event Trigger
Trigger workflows when a collection item is created, updated, or deleted
The Collection Item Event trigger runs workflows when a collection item (a row in a bucket collection) is created, updated, or deleted. Use it to react to habit logs, form submissions, or any collection data changes within a bucket.
Trigger Type
collection_item_eventWhen It Fires
The trigger fires on collection item lifecycle events:
- Create — A new item (row) was added to the collection.
- Update — An existing item's values were changed.
- Delete — An item was removed from the collection.
You can filter by:
- Collection ID — If set, only triggers for this collection. Leave empty to trigger for any collection in the bucket.
- Events — Choose which events to listen to: Create only, Update only, Delete only, or combinations (e.g. Create & Update, or Create, Update, Delete).
The workflow runs in the context of the bucket that contains the collection. bucketId is provided in the payload.
Outputs (Reference in Downstream Blocks)
Use <block_id.output_name> to pass trigger data to the next blocks.
| Output | Type | Description |
|---|---|---|
event | string | Event type: create, update, or delete |
collectionId | string | Collection ID |
itemId | string | Item ID |
item | object | Item data (current state). For create/update this is the new state; for delete it may be the last state. |
previousItem | object | Previous item state (on update or delete). Omitted on create. |
actorUserId | string | User ID who performed the action (create/update/delete) |
bucketId | string | Bucket ID containing the collection |
Common Use Cases
Run a workflow when a habit log row is created
- Add the Collection Item Event trigger.
- Set Collection ID to your habit log collection.
- Set Events to Create only.
- Downstream, use
<collection_item_event_1.item>to read the new row's values (e.g. date, habit name, done).
Sync on update or delete
Set Events to Update & Delete. Use item for the current state and previousItem (on update/delete) to compare or sync changes to an external system.
Branch by event type
Use a Condition block on <collection_item_event_1.event> (e.g. === "create" vs === "delete") to run different logic for create, update, and delete.
Referencing Trigger Outputs
# Use the item's values in a block
itemId: "<collection_item_event_1.itemId>"
item: "<collection_item_event_1.item>"
actorUserId: "<collection_item_event_1.actorUserId>"For triggers, use <block_id.outputName> syntax. The workflow runs in the bucket context; bucketId is available if you need to pass it to other blocks.