> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to get notified when records change
- URL: https://blog.jestor.com/get-notified-when-records-change/
- Published: 2026-09-16T18:50:19.000Z
- Updated: 2026-09-16T18:50:19.000Z
- Author: Bruno Bannach

Setting up **notifications when records change** does not require an automation. In **Jestor**, you can follow an entire table, which subscribes you to every record in it, and you are notified whenever someone else makes a change.

## Why managers end up refreshing screens

Someone responsible for a process wants to know when things move: when a ticket is reopened, when a status flips, when a value is edited. Without a mechanism, they check manually, or they ask people to tell them.

Building an automation for each case works, but it is a lot of configuration for what is essentially the question "tell me what happened".

What following a table solves:

- Refreshing a board to see whether anything changed
- Asking the team for status updates
- Building a separate automation per field you care about
- Missing a change that mattered because nobody flagged it

## What you get notified about

| Event                                | Notified                       | Reason                               |
| ------------------------------------ | ------------------------------ | ------------------------------------ |
| Another person changes a record      | Yes                            | This is the purpose of following     |
| You change a record yourself         | No                             | You already know                     |
| A status moves between values        | Yes, with the before and after | Context in the notification          |
| Any field on any record in the table | Yes                            | Following applies to the whole table |

## Step by step to enable it

1. **Open the table** you want to monitor.
2. **Turn on follow table updates**, which subscribes you to every record in it.
3. **Continue working normally**, since your own edits will not notify you.
4. **Watch the notifications**, which show what changed, including the previous value.
5. **Turn it off** for tables where the volume becomes noise.

## When to use this and when to use an automation

Following is the right tool when a person wants awareness. An automation is the right tool when a system needs to act. If the answer to a change is "someone should know", follow the table. If the answer is "something should happen", build the rule.

- **No configuration required:** a single toggle on the table
- **Whole table coverage:** every record, without listing them
- **Own changes excluded:** no notifications about your own edits
- **Before and after shown:** the notification carries context

## Frequently Asked Questions

### Will I be notified about my own changes?

No. Following is designed to tell you what other people did. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Do I need to build an automation for this?

No. Following a table is a setting, not an automation.

### Does it cover every record in the table?

Yes. Enabling it subscribes you to all records in that table.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.