> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/tracking-context/activity-feed.md). # Activity feed The **Activity** tab is the record's timeline, and the answer to "what has actually happened with this account". Almost all of it arrives on its own: once your mailbox, calendar and other channels are connected, Zero matches each interaction to the people and accounts it concerns and files it on every record it touches. Only comments and logged activities are typed in by hand. Entries are grouped by when they happened — **Upcoming**, **Today**, **Yesterday**, **This week**, **Last week**, **This month**, **Last month**, then by year — newest first, so the next scheduled touchpoint is the first thing you see. ## What Zero tracks automatically | Entry | What it shows | | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Emails** | One entry per thread: who took part, the subject, and the latest snippet. Click it to open the thread. Threads you have kept private are marked **Private**, unsent ones **Draft**. | | **Meetings** | Calendar events with the people invited, the start time, and the meeting link or location. An event that has meeting notes shows a **Notes** flag; click through to read them. | | **LinkedIn** | Message threads with their participants, and connection requests marked **Accepted** or **Pending**. | | **WhatsApp** | Synced conversations, one entry per thread, with the latest message. | | **Slack** | Threads from synced channels, with the channel name, whether it is a public or private channel, and how many messages it holds. Click to expand the thread inline and **Hide thread** to collapse it again. | | **Comments** | What you and your teammates wrote on the record. | | **Activities** | Activities logged by hand — calls, demos, lunches, whatever types your workspace defines — with their title, notes, custom fields, and who took part. | | **Luma** | With Luma connected, event registrations and check-ins, showing the event, its description, the RSVP status, and the location. | | **Changelog** | Property changes on the record, and the tasks created and completed against it. | Two things stay off the feed: emails and meetings involving only your own colleagues, and anything a teammate marked private — where you get a note asking them to share it instead. Notes and tasks are not part of the feed; they have their own tabs on the record. See [Notes](/tracking-context/notes.md) and [Tasks](/features/tasks.md). ## Filtering the feed **Filter** above the feed decides what shows. The menu has a search box and four groups: * **Messages** — **Comments**, **Emails**, **LinkedIn**, **WhatsApp**, and **Slack** (Slack appears once the record has Slack activity). * **Calendar** — with a **With notes only** toggle to show just the meetings that have notes. * **Activities** — one entry per activity type in your workspace, plus any connected activity sources such as Luma. * **Changelog**. **Select all** and **Clear all** sit at the bottom, and your selection follows you from record to record. ## Adding to the feed yourself **Log activity** at the top right opens a menu with **Comment** (shortcut `C`), every activity type your workspace has defined with its own shortcut, and **Manage activity types**. Shortcuts work anywhere on the record page, as long as you are not typing in a field. See [Custom Activities](/tracking-context/custom-activities.md). **Comment** opens a rich-text composer where `@` mentions a teammate, contact, company or deal and links to it. **Add comment** posts it. Comments take emoji reactions and replies, and clicking your own lets you edit it in place or delete it. ## Changelog Changelog entries read as a sentence — who changed what, and to what. Two changes at once show side by side; more than two show the most significant plus **and \ others**, with the rest on hover. Zero records changes to: * **Deals** — **Name**, **Owners**, **Pipeline**, **Stage**, **Deal value**, **Close date**, **Confidence**, and custom properties. * **Companies** — **Name**, **Website Domain**, **All Domains**, **Owners**, **Churned**, and custom properties. * **Contacts** — **Name**, **Owners**, **Email**, **All Emails**, **Title**, **Phone number**, **LinkedIn**, and custom properties. * **Tasks** — created, completed, reopened, renamed, reassigned, or rescheduled. Creation and archiving are recorded too, with how it happened: imported, created by an agent, or picked up from your mail and calendar. Every entry names its author, whether that is a teammate, an agent, or Zero itself. ## Touchpoints The **Touchpoints** chart at the top of the properties panel is the same activity counted over time — **Emails**, **Meetings**, **Activities**, **LinkedIn** and **Slack** — so you can see the shape of a relationship without reading the feed. See [Record view](/tracking-context/record-view.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zero.inc/tracking-context/activity-feed.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.