The purpose of this article is to provide information to Outreach admins regarding the meaning of various toggles used for syncing data to a CRM.
- Outreach Admins
- CRM Admins
- The images used in this article may reference a CRM other than that configured for your organization. The access, definitions, and behavior are the same in all CRMs unless otherwise stated.
As you prepare to connect Outreach to your CRM account, there are a few terms that are important to understand. These toggles are found under each object (lead, contact, account, etc.) in the Plugin configuration settings. We've defined these settings below so you can configure your plugin in whichever way suits your workflow best!
The polling function allows for Outreach to automatically scan your CRM for any newly created objects or changes to existing Objects. Outreach will only notice a recently updated object if the change occurred to a mapped field.
Example: Let's say you have the first name, last name, and email address mapped on the lead Object in the Plugin. If the lead's last name updates in your CRM, Outreach would notice this change and attempt an inbound update, as long as the Inbound Update toggle is enabled (explained below). If the lead's phone number was updated, Outreach would not notice that change, since the phone number field is not mapped on the lead.
The polling frequency determines how often we poll your CRM for new and/or updated objects (see the polling feature described above).
Note: If you increase the time between polling cycles, less API calls will be used.
The pushing function will automatically push changes that occur in Outreach up to your CRM, assuming the change takes place on a mapped field. This toggle will also allow newly created objects in Outreach to push to the CRM, assuming Outbound Create is enabled (explained below).
Example: Let's say you have the Outbound Create toggle enabled for contacts. If a new contact is created in Outreach, and the pushing toggle is enabled, that contact would be created automatically in your CRM, assuming it passes all of the validation rules for contacts.
This function will create records in Outreach from your CRM.
Example: If you have the polling (explained above) and the inbound create toggles enabled on the account object, and a record is updated or created in your CRM system, a new account record will be created in Outreach.
This function allows records to update inbound from your CRM to Outreach.
Example: If you have the address mapped on the account object and their address changes in your CRM, the address will update inbound. This assumes the polling toggle is enabled and there is an existing mapped account in Outreach.
This function allows records to be created from Outreach and pushed up to your CRM.
Example: If a prospect is created in Outreach and the outbound create and pushing toggles are enabled on the lead object, a new lead will be created in your CRM. This assumes the lead passes all validation rules in your CRM.
This function allows records to update from Outreach up to the CRM.
Note: Only fields that are mapped in the 'fields' section of the plugin will be pushed up to your CRM.
Messages & Events
These are the activity postings that will be pushed up to your CRM after emails are delivered/received, tasks are completed, calls are made or opens/clicks occur on any email deliveries. These can be customized by clicking on the gear icon to the right of each specific function. Keep in mind that each of these toggles uses 1 API call each time a message or event is pushed to your CRM.