> 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/advanced-crm-actions.md).

# Advanced CRM Actions

Push results to your CRM, review sync history, and export mapped institutions.

### What you can do

Use advanced CRM actions when you need tighter control over what gets pushed, how it is tracked, and what gets exported.

You can:

* take CRM actions from **Signals**
* push automation output into your CRM
* review CRM push history
* export CRM-mapped institutions for audit or handoff

### Part A — CRM actions from Signals

Click here to watch [video](https://screen.studio/share/V9h4l6v5).

{% embed url="<https://screen.studio/share/V9h4l6v5>" %}
CRM actions from Signals
{% endembed %}

Use this flow when a live signal is ready for follow-up.

{% stepper %}
{% step %}

#### Link the institution first

Open the signal and link the institution before you push anything.

Search your CRM first to avoid duplicates.

Check by account name and by domain when you have it.
{% endstep %}

{% step %}

#### Create net-new accounts when needed

If the institution does not exist, create it from NationGraph.

Set a custom **NationGraph Sourced By** field, or map an existing field, so your team knows where the account came from.

Assign an owner before you save.
{% endstep %}

{% step %}

#### Choose the right CRM action

In **HubSpot**, you can:

* create a **Note**
* create a **Task**
* push **Contacts**

In **Salesforce**, you can:

* create a **Note**
* create a **Task**
* create a **Post**
* **Generate Lead**
* sync **Contacts**
  {% endstep %}

{% step %}

#### Finish with contacts or dual CRM pushes

If your team uses both HubSpot and Salesforce, you can multi-link the institution to both.

You can also route the same action through Zapier.

Push contacts from the **Contacts** tab as the last CRM action, inside or outside the opportunity.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
When you search for an existing account, check the name first, then the domain. This is the safest anti-duplicate pattern.
{% endhint %}

### Part B — CRM actions from Automations

Click here to watch [video](https://screen.studio/share/33LO57k2).

{% embed url="<https://screen.studio/share/33LO57k2>" %}
CRM actions from Automations
{% endembed %}

Use this flow when you want to push structured automation output at scale.

{% stepper %}
{% step %}

#### Vendor Contracts automation

Filter the contracts you want first, such as **completed** contracts.

The institution must already be linked to your CRM.

You can mass-link in **Settings** or link one by one.

From there, you can:

* create a **Note** with total **ACV** and contract dates
* create a **Task** for follow-up
* push **custom mappings** such as vendor product, ACV totals, and end dates
* push contract data as **custom objects** in HubSpot after the schema is set up

Use [How to Push Contracts to Your CRM](/nationgraph/help-center/readme/integration-overview/crm-integrations/push-contracts-to-your-crm.md) for the HubSpot custom object setup guide.
{% endstep %}

{% step %}

#### Ranked automation

Connect HubSpot or Salesforce, then push ranked opportunities into the CRM.

You can create notes, tasks, and custom mappings.

You can also push signal data as a note or task so reps keep the ranking context.
{% endstep %}

{% step %}

#### Generate Outreach Sequence

Use this workflow when your team runs outbound through Zapier.

Select the accounts and emails, then sync them to Zapier.

Build a Zap that routes contacts, emails, and titles into tools like **Outreach** or **Apollo**.
{% endstep %}
{% endstepper %}

### Review CRM push history

Open CRM push history when you need to confirm what synced and what still needs review.

You can review history from:

* the automation run
* **Settings → Integrations** for a broader view

Use this to verify timing, follow-up, and push status.

### Export CRM-mapped institutions

Export CRM-mapped institutions when you want to review mapped records outside NationGraph.

This is useful when:

* an ops team needs a clean export
* you want to compare mapped versus unmapped institutions
* you need to validate the result before the next sync

### Common workflow

{% stepper %}
{% step %}

#### Open the signal, automation, or mapped account set

Start from the workflow you want to act on.
{% endstep %}

{% step %}

#### Push the right action

Choose whether the result should land as a **Task**, **Note**, **Post**, **Lead**, contact sync, or mapped field update.
{% endstep %}

{% step %}

#### Check push history

Confirm the push completed and review any rows that need follow-up.
{% endstep %}

{% step %}

#### Export mapped institutions

Export the mapped result set when you need review, reporting, or a handoff.
{% endstep %}
{% endstepper %}

### Related pages

* [CRM Integrations](/nationgraph/help-center/readme/integration-overview/crm-integrations.md)
* [Sync automation results to your CRM](/nationgraph/help-center/readme/automations-overview/sync-automation-results-to-your-crm.md)
* [Map accounts from CSV or CRM](/nationgraph/help-center/readme/workspaces/map-accounts-from-csv-or-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/advanced-crm-actions.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.