This article dives into how to integrate Salesforce with your Postal account.
Note: You will need to have Admin access in both Postal & Salesforce to complete the integrations setup.
To connect your Salesforce account, you'll need to start in Postal and finish Salesforce.
Start in Postal
Go to the Profile Settings section of your account
Click on 'Integrations' and select 'Connect to Salesforce'
If you haven't already please create the API User (follow this Salesforce help article)
If you already have an API user, use those credentials to connect your integration
Please note! the SFDC user used to integrate Postal to your SFDC instance needs to have read/write access to the following fields to ensure the Managed Package works properly:
Account.Total_Postal_Spend__c Activity.Postal_Name__c Activity.Postal_Total_Cost__c Contact.Postal_Cost__c Contact.Postal_Cost_Per_Touch__c Contact.Postal_Created__c Contact.Postal_Touches_Count__c Lead.Postal_Cost__c Lead.Postal_Cost_Per_Touch__c Lead.Postal_Created__c Lead.Postal_Touches_Count__c
Next, authenticate Salesforce & approve the Integration when prompted
Select which objects are the most applicable to you and your team you want to map between the two platforms.
Now in Salesforce:
Make sure the Marketing User checkbox is checked so the campaign integration works
You will need to select the object "Task" and in the "Type" field, enter "Postal" as an active value in the picklist
Salesforce sends the following contact information to Postal:
First Name, Last Name
Objects & Access
Our application has visibility to your SFDC based on the user that integrates to SFDC. You can use any profile restrictions in SFDC in an integration user account to restrict Postal’s visibility to data you have in SFDC.
What fields get set automatically during Task creation?
With the standard integration, the fields on the Task Object that are set automatically when a Task gets created to indicate an Item was sent are:
We read leads to load in the lead's profile data. We update custom fields on the lead to help with ROI reporting.
We read contacts to load in the contact's profile data. We update custom fields on the contact to help with ROI reporting.
We read accounts so we can associate the account name with your contacts in Postal. We update custom fields on the account to help with ROI reporting.
We create tasks when actions occur in Postal.
Our UI needs to load a list of campaigns so we can allow a user to select which campaign to map an item to.
We need to be able to associate and update campaign member statuses when items are sent
We read opportunities to help report on ROI and for trigger filters
We read events to allow triggering off the event object
We query SFDC every 15 minutes for contacts/lead/accounts updates which results in 384 API calls per day. If more than 2,000 records change there will be an additional API call to SFDC for each block of 2,000 records.
In addition, we send tasks based on activity in Postal as well as update the contact and account records with spending data for reporting in SFDC. Using campaign mappings also adds additional SFDC API calls.
We have no limits on these API calls to SFDC but many customers do have an SFDC limit. To limit API calls we can extend the 15 minute to any number of minutes as well as limit which activities in Postal create tasks in SFDC.
SFDC Managed Package
The SFDC Managed Package can be added to Salesforce to create a deeper integration experience and is required to use Triggers with Postal. This app can be found in the AppExchange and will cost $1. For more information on the Salesforce Managed Package, check out this article!
Note: the SFDC Managed Package supports Enterprise, Performance, Unlimited, Developer, and Database.com Editions.
For additional assistance, please reach out to our Support Team!