The Salesforce Task <> Outreach Task mapping will create a generic task on the lead or contact profile in Salesforce. Based on the plugin settings (outlined below), when the generic task is marked as complete in Outreach the corresponding task will also be marked as complete in Salesforce.
In the Salesforce Task <> Outreach task object mapping you’ll want to have the following options toggled ON and include the listed conditions under "Outbound Create".
Note: Make sure you change the outbound create conditions from the default "Any" to "All". This can be accomplished by clicking on the word "any" on the conditions so that it changes to "all".
When you've enabled the appropriate toggles in the Salesforce plugin, you'll be able to map new fields on the task object in Salesforce. The new mappings that are available include:
| Field Name | For In Person or Action Item Tasks | Description |
| ID | 26 | Task index |
| Action | in_person/action_item | Is the task an in person meeting or action item? |
| Completed | TRUE | Is this task completed? |
| Completer ID | 7 | User ID of the Outreach user that completed the task |
| Completed at | 2016-10-22T08:09:27+00:00 | Time the task was completed |
| Completer name | Rachael Siegel | Name of the Outreach user that completed the task |
| Due at | 2016-10-26T00:20:06+00:00 | Due date of the task |
| Note | Reach out on LinkedIn with press release | Mirror of the note text |
| Task type | Manual, Sequence | Was the task created by a sequence or was it created manually? |
| Task priority | Low | The priority assigned to the task (low, medium, or high) |
| User | Rachael Siegel | Name of the task owner |
| Prospect | Donald Duck | Name of the prospect associated with the task |
| Sequence name | Test Call Sequence | Name of the sequence that generated the task |
| Sequence step number | 1 | The step of the sequence that created the task |
| Template | Outbound Prospect Template | The name of the template if used to send an email |
| Owner | Rachael Siegel | Task Owner |
Unless noted otherwise, you should not alter any advanced field options for any particular field. We have already added the necessary advanced field options for you! If you have questions about adjusting these fields, we recommend reaching out to support@outreach.io to confirm the changes will not impact your Salesforce sync.
It is important to turn off the toggle on the Lead and Contact Sync Settings for tasks within the "messages and events" settings. This will prevent the duplicate tasks from logging in Salesforce.
Additional Settings for LinkedIn Task Mapping
If you're syncing LinkedIn tasks using the Advanced Task Mapping plugin settings, you'll also need to do the following:
- Have your Salesforce Admin create a new custom field labeled "Outreach Task Type". Make sure the field level security is set to "visible" and is visible on the layout for all Salesforce profiles.
- Click into the "fields" tab on the top of the generic task page.
- Click "Add" on the top right hand side of the page and map the "Outreach Task Type" Salesforce custom field you just created to "Action" on the Outreach task field.
- Check the "updates out" checkbox to allow Outreach updates to sync to Salesforce.
- Click "Add" again on the top right hand side of the page. This time, map the "Subject" Salesforce field to the "Custom Template" Outreach field.
- When you hover over the new mapping, you'll see an arrow appear on the right hand side of the page. Click on the arrow and a dropdown menu will appear. Select "Advanced". In the compose window, copy and paste {{task_type_name}} into the box. You can add any other customization here, such as text indicating the activity was from Outreach. This let's us add a custom description to the Salesforce activity, letting you know which LinkedIn activity was completed. Check the "updates out" checkbox to allow updates from Outreach to Salesforce.
- Save your changes. Your LinkedIn tasks will sync to Salesforce with your custom activity title.
© 2019 Outreach.io
Comments
0 comments
Please sign in to leave a comment.