The LinkedIn Automation mode lets you automate LinkedIn connection requests and messages directly from your Outreach sequences using Yess.
Only users with the Admin (Tenant) role have permission to configure the Outreach integration and manage its settings.
Go to the Integrations page in your Yess admin settings.
To use tags, first create the tag in Outreach and assign it to your relevent sequences. You can update the tag at any time, and Yess will include all sequences with that tag in the automation.
Toggle “Schedule”: This switch enables or disables the automatic scheduling.
Choose how often the integration runs by setting a number and a time unit—for example, “Run every 1 day” means the integration will run once a day.
Save your selected schedule by clicking the Checkmark icon
If you need to sync outside of the regular schedule, you can trigger it manually:
Sync Now:
Click Sync Now to immediately sync your data based on the current sync criteria.
New Data Only:
Enable the New Data Only toggle to pull only records that were created or updated since the last sync.(If disabled, the system will perform a full sync based on the selected filters.)
Once you’ve defined your data sync, move to the Field Mapping tab.
If you’re importing data from Outreach and certain fields don’t have a matching default field in Yess, you now have two options for retaining that information:
You can now create custom fields in Yess and map any Outreach field directly to them. This allows you to preserve important data in a structured, searchable format and use it throughout the platform.
If you prefer not to create a custom field, you can still capture values using the Tags field:
Use “Tag” field to add the field’s value only to the Tags column.
Use “Tag with Prefix” to include both the field name and value in the format:
Field Name: Value ( Industry: Finance).
This allows you to retain important data even when a direct field mapping isn’t available.
When using Outreach’s LinkedIn automation through Yess, it’s important to ensure that every engagement step has valid content. To prevent automation from failing, Yess provides a content fallback mechanism that automatically fills in message content when needed.
Why Is Content Fallback Needed?
LinkedIn automation steps rely on having content that is both present and valid. Sometimes, a step may not have any content defined, or it may include variables that are missing or invalid .
In these cases, instead of letting the step fail, Yess uses a fallback template so the message can still be sent smoothly.
You can define a separate fallback message for each LinkedIn engagement type:
Connection Request
Linkedin Message
InMail
By default Yess will assign its built-in AI-generated LinkedIn content. These default templates are short, professional, and tailored to the engagement type, taking into account past engagements with the lead to ensure continuity, avoid repetition, and keep the outreach feeling natural.
Fallback templates cannot currently be edited. If you’d like to make changes, please go to the Templates → Content page in Yess and create a new template that can be used based on engagement type.
This setting controls how the system handles errors or issues during sequence steps that require user attention — such as missing data or invalid configurations.
You can choose between two modes:
Skip – Set by default. The sequence will automatically skip any step that encounters an issue, and no notification will be shown.
Block – The sequence will pause at the step with an issue and trigger an “Attention Required” notification so the user can take action. For a detailed explanation of how these notifications work, see the Outreach Integration Error Handling documentation.
Fine-tune your integration for your needs:
Discover what the integration looks like in action, with step-by-step examples and usage tips.
Learn how Yess alerts you to issues, how to manage notifications, and what to do when something needs your attention.
Setting Up Outreach Escalation Sequences
Looking for a different type of integration? Check out our guide on configuring Outreach escalation sequences in Yess.