> For the complete documentation index, see [llms.txt](https://docs.withorbital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.withorbital.com/integrations/overview-push-to-crm.md).

# Overview: Push to CRM

## Overview

Orbital currently supports two sync methods for Salesforce, Hubspot, and Attio:

* **Push to CRM:** sync a specific workflow or table of data back to your CRM (Hubspot and Salesforce only)
* **Bidirectional sync:** Auto-update records in your CRM and sync new records based on rules, so you can set it and forget it

Continue reading this article for **Push to CRM**. Read more about bidirectional sync here: [Overview: Bidirectional CRM Sync](/integrations/overview-bidirectional-crm-sync.md). 

## Auth

Navigate to **Settings > Integrations** and select **Connect** next to the CRM you want to connect. Follow the OAuth instructions to authenticate your CRM account.

## Triggering Push to CRM

A push to CRM can be triggered from Discover, Workflows, and Universe. Either with a click or as part of an automated workflow.

To set up, add an **Action** to your table. Salesforce and Hubspot both have two actions:

* **Salesforce/Hubspot Sync:** Push record to CRM.
* **Find Salesforce/Hubspot Record:** Look up record in your CRM.

<figure><img src="https://3556389590-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRgu04knFALZ4wMaHQxSu%2Fuploads%2F71q2jAGrLLYQnme193Et%2Fimage.png?alt=media&amp;token=dfb5618c-f4e0-43e0-bbee-5c7192b9da35" alt=""><figcaption></figcaption></figure>

When that action is triggered – either as part of an automation or manual click – the sync to CRM will initiate and run.

## Mapping Orbital <> CRM Fields

Select which **integration** you want (if you have multiple) and then select the **CRM Object** you want to sync the data to.

Next, map the **Destination** fields in your CRM to the fields in your Orbital Table. Type /slash to view all column names in your table.

<figure><img src="https://3556389590-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRgu04knFALZ4wMaHQxSu%2Fuploads%2FKAWY7GGeQ174t10Q0Qhc%2Fimage.png?alt=media&amp;token=5cbd2551-f44f-4246-9ebf-02f5edb07e2c" alt=""><figcaption></figcaption></figure>

## Matching Logic

You can match a row in your Orbital table to a record in your CRM two different ways:

* **Update By Object ID:** Checks the object ID to see if it matches the field you've selected as the input.
* **Update By Match:** Checks whether the Destination Field matches the Condition. You can combine multiple rules with **and/or** statements.

## Additional Configuration

* **Update:** When this is selected, Orbital will also update this specific field rather than only run when a new record is created.
* **Skip If Empty:** If Orbital has an empty value, then it won't try to override this specific CRM field.
* **Skip Update:** Orbital will not update any CRM records whenever a record is matched. It will only run when a new record needs to be created.