> For the complete documentation index, see [llms.txt](https://nationgraph.gitbook.io/nationgraph/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nationgraph.gitbook.io/nationgraph/help-center/readme/automations-overview/create-and-run-an-automation.md).

# Create & run an automation

A repeatable flow for setting scope, running, and taking action on results.

{% hint style="info" %}

## For full breakdowns, refer to [Ranked Institutions](/nationgraph/help-center/readme/automations-overview/ranked-automations.md), [Request vendor/competitor contracts (FOIA)](/nationgraph/help-center/readme/automations-overview/foia-automations.md), [Email Automation](/nationgraph/help-center/readme/automations-overview/outreach-automations.md), and [Find Contacts](/nationgraph/help-center/readme/automations-overview/contacts-automation.md).

{% endhint %}

{% hint style="info" %}
**Compass guides you through Deep Research.** Select **Deep Research** from the new Automation menu, then tell Compass what you want to learn. It will help you choose the questions and accounts, show the estimated cost, and ask for your approval before starting. Find the report under **Automations**. See [Deep Research](/nationgraph/help-center/readme/compass/deep-research.md).
{% endhint %}

### Before you start

Make sure you’re clear on the scope you want to run against. Decide territory, institution types, and the time window (if relevant).

### Create an automation

{% stepper %}
{% step %}

#### Open Automations

From the left nav, go to **Automations**.
{% endstep %}

{% step %}

#### Choose an automation type

Pick one:

* **Ranked Institutions**
* **Request Vendor/Competitor Contracts (FOIA)**
* **Email Automation**
* **Find Contacts**
  {% endstep %}

{% step %}

#### Configure scope

Set the geography, institution types, and any required filters. Use a tight scope for your first run.
{% endstep %}

{% step %}

#### Configure the automation

* For **Ranked Institutions**: define scoring criteria and weights.
* For **FOIA contracts**: define territory and the contract date range.
* For **Email Automation**: define filters, contact criteria, and the message flow you want to generate.
* For **Find Contacts**: select at least one territory and title, then configure any similar-title, excluded-title, email, or phone requirements.
  {% endstep %}

{% step %}

#### Run it

Start the run and let it process in the background. You can navigate away.
{% endstep %}

{% step %}

#### Review results

Open the results table. Filter, sort, and inspect outliers.
{% endstep %}

{% step %}

#### Take action

* Export as CSV.
* Sync to your CRM.
* Save targets for outreach.
* Review CRM push history when you need an audit trail for sync activity.
  {% endstep %}
  {% endstepper %}

### Tips for better results

* Start with a **small territory**. Validate output quality first.
* Tune one variable at a time. Change scoring criteria or filters, then re-run.
* Use CRM sync when you need **trackable follow-up**. Use CSV when you need **analysis**.

{% hint style="warning" %}
If you change automation configuration, treat it like a new version. Keep notes on what you changed and why.
{% endhint %}


---

# 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://nationgraph.gitbook.io/nationgraph/help-center/readme/automations-overview/create-and-run-an-automation.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.