# How to integrate the Salesforce Connector on Bird?
The **Salesforce Connector** is a powerful integration feature within the Bird platform that allows you to seamlessly sync data between **Salesforce** and **Bird**. This connector simplifies workflows and ensures your customer and sales data remains consistent across both platforms.
### **What is the Salesforce Connector?**
The Salesforce Connector enables a **bi-directional sync** between Salesforce and Bird, keeping your data up-to-date in real time or on a defined schedule. With this integration, you can automatically **fetch and update changes** to key Salesforce objects:
* Contacts
* Accounts
* Leads
* Opportunities
Changes made in either system can be reflected in the other based on your mapping and configuration, helping streamline communication, campaigns, and CRM workflows.
### **Key Features**
#### **Scheduled Data Sync**
You can configure how frequently Bird should fetch updates from Salesforce. The sync intervals can be defined based on your operational needs—whether that’s every few minutes, hourly, daily, etc.
**Example:**\
Sync all new or updated Salesforce contacts and leads to Bird every 15 minutes.
#### **Attribute Mapping with the Dataflows Attribute Mapper**
Bird’s **Dataflows** section includes an **Attribute Mapper**, a configuration tool that lets you:
* **Map Salesforce fields** to **Bird attributes** for Contacts and Accounts.
* **Filter and sync** only specific events and not all.
**Example:**\
The same SF account is used by different teams, but only the marketing team is using Bird. Then you may want to filter SF events specific to the marketing team using Bird, ensuring Bird isn’t populated with unnecessary data or your team doesn’t have access to act on data that’s not specific to them.
* **Ensure consistency** in names, values, and formatting across platforms.
#### **Two-Way Sync**
Once the attribute mapping is complete:
* Updates made in **Salesforce** will automatically reflect in **Bird**.
* Updates made in **Bird** will push back to the corresponding **Salesforce** fields.
This ensures that the systems remain **synchronized** and eliminates manual data entry and inconsistency errors.
### **Known Limitation: Deletions**
Currently, the Salesforce Connector **does not support deletion sync**. If a **Contact, Account, Lead, or Opportunity** is deleted in Salesforce, **it will not be automatically removed from Bird**.
* This is a **planned enhancement** for future updates.
* Until then, such deletions must be manually/periodically handled in Bird if needed.
### **How to Set It Up**
1. Navigate to **Admin console → Integrations → Add new integration → Salesforce** on Bird.
2. Select **Salesforce Connector** and **authenticate** with your Salesforce account.
3. Now you’d be able to see your connector instance under the Salesforce connector.
4. On selecting the connector instance, you’d be able to see 3 tabs - Overview, Config and Health.
* **Overview** - helps you see all the available **actions** and **triggers** to build a flow.
* **Config** - helps you manage the sync between Salesforce and Bird. Also, helps reauthenticate in case of failures, permissions issues, etc.
* **Health** - verify the status
### **How to Filter and Sync Attributes/Properties**
#### Navigation
Select the Config tab on the connector instance and choose configure attributes against the object of your choice - Contacts/Accounts/Opportunities/Leads.
In this case, let’s take a look at the Contact object.
#### **Dataflows > Attribute Mapper**:
#### Options to configure here:
**Salesforce filters:You can apply a filter or filters of your choice using the following protocol (SOQL):**\
[**https://developer.salesforce.com/docs/atlas.en-us.soql\_sosl.meta/soql\_sosl/sforce\_api\_calls\_soql\_select\_conditionexpression.htm**](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_select_conditionexpression.htm)
Hit save and you should already see the preview on the right hand side to only show filtered data.
Example\
**Before filtering:**
**After filtering:**
**Start date:**
Give a date from which you want the data to be fetched and synced. Any date before the provided data will not be fetched. This can help you fetch data after a certain change in Salesforce you applied on a specific date.
**Identifiers:**
Here, you’d map your contact identifier from Salesforce onto Bird’s identifiers. In the screenshot above, we’ve not mapped phone as in the example above contact records can have the same phone across users.
**Important Note:** Please choose only the unique identifiers in your system to map here.\
In the use case where you could have different contact records with the same email or phone number, please don’t map the phone or email in the identifier section, as that will ensure uniqueness and merge contacts in Bird.
**Attribute Group:**
\
Consider the case where you could have multiple integrations with different systems of yours like - Salesforce, Hubsport, ActiveCampaign, etc. The idea is to be able to view the different attributes from each systems within Bird with ease as it’d be clubbed within a group.
**Attribute mapping:**
This is where you’d map your salesforce contact properties/attributes with Bird contact attributes.
By default Bird would create attributes that don’t exist from Salesforce within Bird for you and map them on the Bird.
**Consideration:** Map the attributes you need and not everything as that could potentially be time consuming and stale data residing in Bird.
**Note:** You could also choose to map certain fields like Name from Salesforce to Bird’s Display Name rather than a new attribute that’s groups within the Saleforce Attribute. You could do so with other attributes too only if needed.
#### **Save** the Configuration
Ensure you hit save and then just refresh the tab or page once to verify if the preview shows the right data based on the configurations you applied.
#### **Enable** Dataflow
Now that you’ve verified all the configurations just enable the Dataflow.
**Note:** The dataflow may take upto 10-15mins to fetch the data. This depends on the size of your initial fetch. If you still don’t see any run after an hour do reach out to us.
#### Set the **sync frequency**
\
\
\
Define your schedule as 5m, 10m, 15m, 1h, 24h, etc
#### View your Runs
Select your Data Flow from\
a) Admin Settings >> Workflows >> Data Flows\
b) Admin Settings >> Integrations >> Salesforce Connector >> Config >> View configuration >> Navigate the bread crumb to Data Flows
You’ll be able to view your Runs once your select your Data Flow and navigate over to the **Runs** tab.
Now if you don’t see any values - select Filters and apply the data filter to max\
### **Best Practices**
* **Start with syncing only specific test events using the filters** during testing to validate mappings.
* Regularly **review your mappings** when Salesforce schemas change.
* Sync only the necessary fields rather than all fields for better control over the data flow across systems.
* Use clear and consistent naming in Bird attributes for better traceability.
By integrating Salesforce with Bird through this connector, you can build a single source of truth across your CRM and engagement platform, streamlining your workflows and boosting your team's efficiency.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.bird.com/applications/integrations/integrations/how-to/how-to-integrate-the-salesforce-connector-on-bird.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.