How can we help? 👋

View card history

See what’s happened on a card

Use card history to investigate a recorded change: what changed, when it happened, and which user or system source is shown. Use the related conversation to inspect the actual message. A history entry is not by itself proof of message delivery, and an absent entry does not prove that nothing happened.

💡

History is not a guaranteed lifetime audit trail. Available entries depend on retention, access and the selected source or filters. If an older event is missing, ask Support about the available records rather than assuming it never occurred.


Review communication context

If you want to review communication associated with a card (such as messages sent or received), you can access this directly from the card preview.

  1. Click on any card to open it in the right-side panel.
  1. Select the Related tab.

What you’ll see:

  • A timeline of communications related to the card
  • Messages that have been sent or received in connection with that card

This view is helpful when you want to understand the conversation history without reviewing every field-level change.


Open the card’s update history

To see a log of updates made to a card, you can access the History menu from the same right-side panel.

  1. Open a card so it appears on the right side of the board.
  1. Click the three-dot menu (⋯) on the card.
  1. Select History.

What you’ll see:

  • A chronological log of updates made to the card
  • Changes made by users or system actions

This option is useful for quickly reviewing what has changed on a card without leaving the board view.


Use the expanded History tab

For additional history controls, open the card in its expanded view. Available records depend on retention, access, and the selected history or activity source; this is not a guarantee of a complete lifetime audit trail.

  1. Double-click any card or click the Expand Card View icon.
  1. Navigate to the History tab.

What you’ll see:

  • Available recorded changes and activity, which may include:
    • Updates made by users
    • Updates made via sync (for Location cards)
    • Automation activity
    • Communications sent or received
  • Available timestamps and sources for recorded updates
The expanded History tab shows User and Update filters plus before-and-after values where recorded. This example contains only synthetic QA activity.
The expanded History tab shows User and Update filters plus before-and-after values where recorded. This example contains only synthetic QA activity.

Filter the history log

Within the History tab, you can filter the audit log to quickly find what you’re looking for:

  • Use User to filter by a recorded actor.
  • Use Update to filter by the recorded update type.

The current table shows User, Updated, Updated From, Updated to and Date. An update may describe a field change or an event such as record creation or archiving. Do not infer a time zone from a date without an explicit label; include your time zone when reporting an issue.

Use this view when troubleshooting unexpected changes. Compare the available history with related communications and automation logs rather than assuming every event is included.


Investigate an unexpected change

  1. Confirm the correct card, property or contact before reviewing its history.
  1. Identify the field or action and approximate time you are investigating. Apply relevant filters, then broaden or clear them if no matching entry appears.
  1. Compare the recorded timestamp, actor/source and any before-and-after values shown. A system or integration entry is not necessarily a manual user edit.
  1. Cross-check related conversations, tasks and automation diagnostics for the actual outcome. Do not immediately overwrite a value or rerun an automation without checking what already happened.
  1. If the cause is unclear, send Support the board/card link, field or action, approximate time and time zone, expected versus observed result, and a screenshot of the relevant entries. Do not include credentials or unrelated personal information.

Related articles

Did this answer your question?
😞
😐
🤩