> 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/account-intelligence/workflows/nodes/source-node.md).
# Source Node
### The Source Node
The Source Node queries and filters accounts or contacts from your views to create targeted lists. It supports both saved views and custom filters, allowing you to precisely define which accounts or contacts should flow into your workflow. This node acts as the entry point, pulling in data directly from your CRM.
{% hint style="info" %}
The number of records allowed in the Source node depends on your workflow configuration:
* If your workflow includes a **Contact Discovery** or **Contact Enrichment** node, the Source node is limited to **2,000 records**.
* If your workflow includes an **AI** node, the Source node can contain up to **1,000 records**.
* If none of the above nodes is included, the Source node can contain up to **10,000 records**.
{% endhint %}
***
### When to Use It
Every workflow must have source node to:
* Automatically pull in accounts or contacts that meet certain criteria (e.g., exists in CRM, belongs to a saved view).
* Ensure downstream nodes only process the most relevant and qualified records.
* Keep your workflow synced with CRM changes by running on a schedule or triggering based on events.
***
### Configuration Overview
Here’s how it works:
**Source Scope**
* **Accounts** – Query companies
* **Contacts** – Query contacts
**Source Type**
* **View** – Pulls records from an existing saved [view](/account-intelligence/views.md).
* **Custom** – Allows you to define filters (such as “Exists in CRM is true”) for more flexible targeting.
**Execution Mode**
* **Scheduled** – Runs the query on a regular schedule (e.g., every day).
* **Triggered** – Runs when a specific condition occurs, such as when a record enters a view or when a defined goal occurs.
**Scheduling & Triggers**
* **Scheduled** – Choose a frequency (daily, weekly, etc.).
* **When Goal Occurs** – Triggered when a workflow goal is met.
* **When Record Enters View** – Triggered when new records meet your defined criteria.
---
# 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/account-intelligence/workflows/nodes/source-node.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.
