Table History View

For instructions on how to access views or how to add one, see the Views page.

Capabilities

• View the complete change history of a table without leaving it
• Filter history by action type (update or delete)
• Filter history by the source of the change: user, API, or automation
• Filter history by date (today, yesterday, or earlier)
• Apply advanced custom filters to the history log
• Export the history log to a spreadsheet
• Compare the before and after state of each change in grouped entries

Use Cases and Examples

A support manager wants to audit what happened to tickets over the past week. They open the history view on the tickets table, filter by date, and instantly see every change — who made it and what was modified.

A developer debugging an integration filters the history by API as the source and checks whether the expected records were updated by their automation or not.

An operations team runs a monthly audit by exporting the history log to a spreadsheet, which they store as a record of all changes made during that period.

How to Access

Step 1

Open the table you want to review.

Step 2

Go to Views (Visões) in the table tools area, then select History. The history log appears with all recent changes for that table.

Step 3 (optional)

Apply filters to narrow down the results. You can filter by action type (update or delete), source (user, API, or automation), or date (today, yesterday, or before).

Step 4 (optional)

To add more specific conditions, use Add Filters to build advanced filter combinations.

Step 5 (optional)

To save the log externally, click Export to download a spreadsheet copy of the history.

The Before and After Format

Each history entry stores changes in a grouped format. If a single action modified five fields at once, those five changes are saved as one entry — showing the state before the action and the state after the action side by side.

This allows you to compare exactly what changed in a given moment, even when multiple fields were updated together.

Keep in Mind

• The history view shows changes to that table only — it does not include changes from connected tables.
• Filtering the history does not affect the records displayed in the table itself. The two are independent.
• The history view is read-only. You cannot edit records or revert changes from it.
• The before/after values are displayed in a structured format that may resemble code. This is intentional — it allows all field values to be stored and compared in a single entry regardless of field type.

FAQ

1- Is this the same history as the one inside the record card?

Yes. It shows the same change data available on the full account history, but scoped only to that table.

2- Can I filter by who made the change?

Yes. You can filter by user, API, or automation as the source of the change.

3- Can I export the history log?

Yes. There is an export option that lets you download a copy of the history as a spreadsheet, which you can use for auditing or external storage.

4- Why does the before/after format look like code?

Because Jestor groups all fields changed in a single action into one entry. This format allows the system to display all before and after values together in a compact, structured way — regardless of how many fields were changed at once.

5- Does the history view show changes made by automations?

Yes. Changes triggered by automations appear in the history and are attributed to the automation as the source.