> 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/integration-overview/crm-integrations/zapier-integration.md).

# Zapier Integration

Connect NationGraph to additional CRMs and downstream tools through Zapier.

Connect NationGraph to thousands of apps through Zapier, so your team can route signals, institutions, and automation output into the tools you already use.

Click here to watch [video](https://vimeo.com/1198617198).

{% embed url="<https://vimeo.com/1198617198>" %}

Use Zapier when your team works in a CRM or workflow tool beyond HubSpot or Salesforce.

This is the fastest way to route NationGraph data into the rest of your stack.

Common destinations include:

* Pipedrive
* Zoho CRM
* Email and workflow tools that support Zapier

{% hint style="info" %}
Zapier works best when you need broader tool coverage, not a deep native CRM setup.
{% endhint %}

### When to use Zapier

Use Zapier when you need to:

* send NationGraph data into another CRM
* hand off records to an outbound or ops workflow
* connect automation output to tools your team already uses

If you use HubSpot or Salesforce, use the native integrations first.

### Recommended setup pattern

{% stepper %}
{% step %}

#### Choose the NationGraph workflow

Start with the workflow that should trigger the handoff.

This is usually a Signal, a mapped institution, or an automation result.
{% endstep %}

{% step %}

#### Build the Zap

Create a Zap that receives the NationGraph data and sends it to the destination app.

Map only the fields your team will actually use.
{% endstep %}

{% step %}

#### Test with a small batch

Run a small test first.

Check field mapping, formatting, and duplicate behavior before scaling up.
{% endstep %}

{% step %}

#### Turn on the workflow

Once the test looks clean, enable the Zap for your full workflow.
{% endstep %}
{% endstepper %}

### Recommended fields

Start with a small, stable field set:

* **NationGraph ID**
* institution name
* owner or rep
* signal type or automation category
* date fields your downstream tool needs

{% hint style="warning" %}
Test dedupe rules before you send live data into a CRM. This helps avoid cleanup later.
{% endhint %}

### Best practices

* Keep the first Zap narrow.
* Use clear field names.
* Add more mappings only after the first sync works.

### Example Zaps

Each example follows the same setup pattern.

Start in **Settings → Integrations → Zapier → Connect**.

Accept the invite, then create the Zap in Zapier with the most recent **NationGraph** app version.

When you publish the Zap, NationGraph flips **Connect** to **Disconnect** and the push buttons go live.

#### Push an Institution → Google Sheets

Click here to watch [video](https://vimeo.com/1203900586).

{% embed url="<https://vimeo.com/1203900586>" %}

{% stepper %}
{% step %}

#### Create the trigger

In Zapier, click **Create** and choose **NationGraph**.

Pick the trigger event **Institution Push**.

Name the label that should appear on the NationGraph button.
{% endstep %}

{% step %}

#### Test the trigger

Select your NationGraph account and click **Test trigger**.

Confirm the test record includes institution name, ID, state, and city.
{% endstep %}

{% step %}

#### Map the Google Sheets action

Add **Google Sheets → Create Spreadsheet Row**.

Map:

* name
* ID
* state
* city
  {% endstep %}

{% step %}

#### Publish and push live data

Publish the Zap, then return to a signal in NationGraph.

Push the institution when a new account appears.
{% endstep %}
{% endstepper %}

#### Push Ranked Results → Google Sheets

Click here to watch [video](https://vimeo.com/1203900589).

{% embed url="<https://vimeo.com/1203900589>" %}

{% stepper %}
{% step %}

#### Create the trigger

Create a Zap with **NationGraph** as the trigger app.

Choose **Ranked Result Push** and set the button label.
{% endstep %}

{% step %}

#### Test the trigger

Run **Test trigger** and confirm the sample includes ranked result data.
{% endstep %}

{% step %}

#### Map the Google Sheets action

Add **Google Sheets → Create Spreadsheet Row**.

Map:

* institution name
* state
* ID
* rank
* score
* title
* summary
* significance
  {% endstep %}

{% step %}

#### Publish and push live data

Publish the Zap, refresh NationGraph, then push a ranked result from the list.
{% endstep %}
{% endstepper %}

#### Push Vendor Contracts → Google Sheets

Click here to watch [video](https://vimeo.com/1203900588).

{% embed url="<https://vimeo.com/1203900588>" %}

{% stepper %}
{% step %}

#### Create the trigger

Create a Zap and choose **NationGraph**.

Select **Vendor Contract Push** and name the label.
{% endstep %}

{% step %}

#### Test the trigger

Send a vendor contract test record into Zapier.

Confirm the sample data looks correct before you continue.
{% endstep %}

{% step %}

#### Map the Google Sheets action

Add **Google Sheets → Create Spreadsheet Row**.

Map:

* institution name
* institution state
* vendor product
* ACV
* ACV date
* summary
  {% endstep %}

{% step %}

#### Publish and push live data

Publish the Zap, refresh NationGraph, then push vendor contract rows as they appear.
{% endstep %}
{% endstepper %}

#### Push Contacts from Accounts or Signals → Google Sheets

Click here to watch [video](https://vimeo.com/1203900587).

{% embed url="<https://vimeo.com/1203900587>" %}

{% stepper %}
{% step %}

#### Create the trigger

Create a Zap with **NationGraph** as the trigger app.

Choose **Contact Push** and set the label.
{% endstep %}

{% step %}

#### Test the trigger

Select the test record and use the **contact ID** field.

Confirm the sample includes the core contact fields.
{% endstep %}

{% step %}

#### Map the Google Sheets action

Add **Google Sheets → Create Spreadsheet Row**.

Map:

* ID
* name
* contact name
* title
* email
* phone
  {% endstep %}

{% step %}

#### Publish and push live data

Publish the Zap, then open an account or signal in NationGraph.

Use **Match Contacts** on a signal when you want to push many contacts at once.
{% endstep %}
{% endstepper %}

#### Push Signals → Clay

Click here to watch [video](https://vimeo.com/1203900636).

{% embed url="<https://vimeo.com/1203900636>" %}

{% stepper %}
{% step %}

#### Connect Zapier

Connect Zapier in **Settings → Integrations** first.
{% endstep %}

{% step %}

#### Create the trigger

Create a Zap with **NationGraph** and choose **Signal Push**.

Name the label that should appear on the NationGraph button.

Run **Test trigger** and confirm the sample includes signal title, summary, significance, reason, created-at, and institution details.
{% endstep %}

{% step %}

#### Map the Clay action

Add **Clay → Create Record in Table**.

Enter the **workspace ID**, **table ID**, and **view**.

Map:

* signal ID
* institution name
* institution state
* title
* summary
* significance
* reason
* created-at
  {% endstep %}

{% step %}

#### Publish and push live data

Publish the Zap, turn it on, then push a signal with **Push to Zapier**.

The same pattern works for Sheets or another CRM.
{% endstep %}
{% endstepper %}

### Related pages

* [CRM Integrations](/nationgraph/help-center/readme/integration-overview/crm-integrations.md)
* [Advanced CRM Actions](/nationgraph/help-center/readme/integration-overview/crm-integrations/advanced-crm-actions.md)
* [Sync automation results to your CRM](/nationgraph/help-center/readme/automations-overview/sync-automation-results-to-your-crm.md)


---

# 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/integration-overview/crm-integrations/zapier-integration.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.