> ## Documentation Index
> Fetch the complete documentation index at: https://docs.avina.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Salesforce Integration

> Overview of the integration between Avina and Salesforce

## Overview

The Salesforce integration is a full bi-directional sync between Avina and your CRM. It ensures Accounts and Contacts are always enriched with Avina signals, while pulling in Salesforce context to power high-impact signals, account insights, and drafting.

## Purpose

* Create and update **Accounts** and **Contacts** in Salesforce automatically
* Write Avina signals to the **`AvinaSignals__c` custom object** linked to Accounts and Contacts
* Pull Salesforce data (contacts, opportunities, activities, campaigns) into Avina to enrich signals and context
* Give sellers deeper signal visibility directly in Salesforce, while feeding Salesforce context back into Avina

## How It Works

* **Write:**
  * Accounts → created or enriched when Avina detects new companies
  * Contacts → created or enriched when Avina identifies new prospects
  * Custom Object → Avina writes signals (e.g., job changes, web visits, engagement surges) as structured `AvinaSignals__c` records with lookup relationships to Account, Contact, and Lead

* **Read:**
  * Avina pulls Accounts, Contacts, Opportunities, Campaigns, and Activities from Salesforce
  * This context strengthens Avina's ability to generate signals, prioritize accounts, and draft personalized messaging

## Setup

1. Go to **Settings → Integrations** in Avina.
2. Select **Salesforce**.
3. Authenticate with your Salesforce account and approve access.
4. Save and test the connection.

Before Avina can write signals to your Salesforce org, you'll need to create the `AvinaSignals__c` custom object. See [Push to Salesforce](/integrations/salesforce/push-salesforce) for the step-by-step setup, tag schema, and Flow Builder examples.

## Use Cases

### Signal visibility in your CRM

Every Avina signal is written as a record in the `AvinaSignals__c` custom object and linked to the relevant Account, Contact, and (optionally) Lead. Your team can report on signals, build list views, and trigger Flows without leaving Salesforce.

### Flow Builder automations

Because signals are structured records with standardized tags (e.g., `avina_new_hire_signal`, `avina_web_visit_signal`), you can trigger Flows on record creation with tag-based entry conditions. Common Flows: Slack/email alerts to the AE, auto-tasks on Opportunity, sequence enrollment. See [Push to Salesforce](/integrations/salesforce/push-salesforce) for complete examples.

### Enriched Account prioritization

Avina pulls opportunity history, activity, and campaign data from Salesforce to produce more accurate account fit scores and signal rankings.

### Automated CRM updates

When Avina surfaces a new prospect via a signal, the corresponding Account and Contact are automatically created or updated in Salesforce. No manual data entry required.

## Supported Actions in Automations

When building [automations](/features/automations), Salesforce supports the following destination types:

* **Create lead/contact:** add new contacts discovered by signals
* **Create account/company:** add new companies to Salesforce
* **Add signals to contacts/accounts:** write signal records to the `AvinaSignals__c` custom object

## Sync Behavior

* **Initial sync:** Avina pulls historical CRM data (accounts, contacts, opportunities, activities, campaigns) when first connected.
* **Ongoing sync:** new data syncs bi-directionally in near real-time.
* **De-duplication:** Avina matches contacts by email and accounts by domain to prevent duplicates.