# 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 **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.

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


---

# Agent Instructions: 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:

```
GET https://docs.hockeystack.com/account-intelligence/workflows/nodes/source-node.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.