> 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/features/ai-properties/ai-properties-examples/extract-tech-stack-from-emails-and-notes.md).

# Extract Tech Stack from Emails and Notes

## **Use case**

Search emails and notes for information about the Company’s current tech stack.

**Note**: This property works best if you create a Multi-select list and list all the potential tools as options (see screenshot below).

<details>

<summary><strong>Prompt</strong></summary>

Search through all emails and notes saved related to <mark style="color:red;background-color:orange;">**Company**</mark> identify mentions of GTM tools currently used by the prospect. Focus on tools related to CRM, lead generation, sales enablement, and marketing automation (e.g., HubSpot, Attio, Pipedrive, Clay, Apollo, Lemlist, Unify).

**Requirements:**

1. **Scope:** Search only the content of emails and notes. Do not include information from external sources like the company website.
2. **Tool Mentions:** Extract the names of GTM tools explicitly mentioned in the emails or notes. Exclude tools discussed as potential solutions or competitors, focusing only on tools the prospect is confirmed to use.
3. **Concise Format:** Select the explicitly mentioned tools from the list of options
4. **Fallback for Missing Data:** If no GTM tools are identified in the emails or notes, leave the response empty.

</details>

<figure><img src="/files/Nar7rhRZFfVHWDVSRJVF" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/uelNRWuzatKk9oKqg7ne" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/At8ha2FfWoXvrFzNhJMt" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zero.inc/features/ai-properties/ai-properties-examples/extract-tech-stack-from-emails-and-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.