> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/release-notes/2025/august-25-2025.md).

# August 25, 2025

### Revamped Contact Discovery Node

The Contact Discovery node in workflows is now smarter and more accurate. You can filter results based on whether people recently joined, were promoted, or if they were previously customers at another company. This makes finding the right contacts easier than ever.

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FDGEVT660eYdZxQmDfkuk%2FScreenshot%202025-09-01%20at%203.35.23%E2%80%AFPM%20(1).png?alt=media&amp;token=355f09c3-f077-4d02-a67d-973f34a2f320" alt=""><figcaption></figcaption></figure>

### Email Sequencer Node

You can now create **emails and sequences of emails directly within workflows**. For each contact being processed, you can:

* Write a single email or a full sequence.
* Configure instructions and add samples.
* Adjust sequence length.
* Preview drafts before sending.

### Person-Level Views

Views aren’t just for companies anymore. You can now create **person-level views**, complete with their own filters as well as inherited filters from company-level views. This allows you to segment and work with lists of individual people, not only accounts.&#x20;

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FSaZoCNN44ojrB10i7kJQ%2FScreenshot%202025-09-01%20at%203.21.36%E2%80%AFPM%20(1).png?alt=media&amp;token=ab912f90-bd1b-4611-8de3-53b5f9a8b4ff" alt=""><figcaption></figcaption></figure>


---

# 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.hockeystack.com/release-notes/2025/august-25-2025.md?ask=<question>&goal=<user_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.