# Note content updated

Source: https://neondeerdata.com/docs/platform/automations/triggers/note-content-updated/

Trigger · Notes

Starts a run when a note’s text is edited, at most once every 5 minutes per note.

**Attio events:** `note-content.updated`

## Inputs

No configuration.

## Outputs

| Label         | Key                 | Type      | Always set | Notes                                                                                                               |
| ------------- | ------------------- | --------- | ---------- | ------------------------------------------------------------------------------------------------------------------- |
| Note ID       | `note_id`           | Text      | Yes        |                                                                                                                     |
| Triggered at  | `triggered_at`      | Timestamp | Yes        |                                                                                                                     |
| Updated by    | `updated_by`        | Actor     | No         | Present only when Attio sends an actor of a recognized type (workspace member, API token, system, app or workflow). |
| Content       | `content_plaintext` | Text      | Yes        | The note’s plain text at the time the app reads it.                                                                 |
| Parent record | `parent`            | Record    | Yes        |                                                                                                                     |
| Title         | `title`             | Text      | Yes        |                                                                                                                     |

## How it behaves

- The first edit fires; further edits to the same note within 300 seconds are dropped. The cooldown is per note, and starts fresh each time the workflow is turned on.
- This is not a trailing debounce: an edit made during the cooldown is reported only if another edit arrives after the cooldown ends.
- Repeated deliveries of the same event are detected with Attio’s `Idempotency-Key` header. A delivery without that header is not deduplicated.
- If the app cannot check whether it already handled the event or whether the cooldown applies, it starts the run anyway rather than drop the event, so a run can repeat. If it cannot confirm that the event came from Attio, the event is dropped and no run starts.

## Limits and constraints

- Cooldown: 300 seconds per note.

## Errors

Triggers have no error branch. When something goes wrong inside a trigger, no run starts. See [Troubleshooting](https://neondeerdata.com/docs/platform/automations/troubleshooting/).

## Notes

- The previous content is not available.

## Example

Re-run a summary when someone edits the text of a meeting note.

**Example inputs**

| Event                  | Value                                                           |
| ---------------------- | --------------------------------------------------------------- |
| `note-content.updated` | Maya Chen edits the body of the note "Intro call" on Acme Corp. |

**Example outputs**

| Output        | Value                                                                    |
| ------------- | ------------------------------------------------------------------------ |
| Note ID       | 5c1e9a42-7d0b-4f3e-9b8a-2f6d1c4e8a10                                     |
| Triggered at  | 2026-10-07T15:02:11Z                                                     |
| Updated by    | Maya Chen (workspace member)                                             |
| Content       | Spoke with the CFO. Budget approved for Q1\. Next step: security review. |
| Parent record | Acme Corp (companies)                                                    |
| Title         | Intro call                                                               |

If Maya edits the note again within 300 seconds, that edit starts no run. The previous content is not available.