Skip to main content

Timeline Event sources and icons

In this article, we'll describe exactly which sources appear in the timeline

Timeline Event sources and icons

When you build processes in NetHunt CRM, the activity history in a contact or deal card is the primary source of truth. Previously, if an action was performed automatically using Automations, we marked that event with a lightning bolt icon. This made it clear at a glance that the change occurred automatically and allowed you to quickly navigate to the specific run in the automation history to view the details.

In this update, we’ve expanded this logic. Now, the CRM tracks many more event sources so you know exactly which system, integration, or tool made changes to a card. In addition, we’ve refreshed the design to make the interface even more intuitive.

Understanding Event Sources in the Activity History

Now, in addition to automations, the activity history displays unique markers for the following actions and sources:

Record Merges - when two cards are merged into one:

Copying a record - when duplicating a card:

Moving a record - when changing a folder or entity:

Synchronization with Google Contacts - changes made through two-way synchronization.

Rollback of bulk updates - restoring fields to their previous state after a bulk edit.

Import - creating or updating by uploading a file.

Data enrichment - automatically populating a record with information from open sources.

API - changes submitted via external API integrations.

Model Context Protocol (MCP) - actions performed using artificial intelligence. We've added distinct, recognizable icons for popular solutions - Claude and ChatGPT.

If you hover over an event or click on it, a pop-up window will open with a detailed description of the source and a button to quickly navigate to the corresponding integration or settings.

Icon for “Field Updates”

To avoid visual confusion between the “Undo Changes” icon and regular data editing, we’ve updated the icon for “Field updates”

The new icon better matches the design of the steps in the automation builder and makes the activity feed more consistent. You'll see it both in the general list of events and in the filters for the activity history.


Haven’t found the answers you’re looking for? Ask our User's Community.

Did this answer your question?