Outreach.io Opted out mapping

Developer Support APIs & Integrations
1

Hi

I’ve configured the Outreach.io integration with Hubspot. I’ve set this integration up many times, and last year, everything worked as expected. Lately, we’ve noticed that with all my customers, the Opted Out field of Outreach does not sync bidirectionally with Hubspot Opt-out (one-to-one). Here is the link to Outreach’s API for the prospect. What I’ve understood is that Outreach doesn’t specify the filetype and therefore it will only sync from Hubspot to Outreach and not in both ways.

On top of that, I’m encountering that a custom-created boolean named “opted out” in Hubspot is bi-directionally synced to Outreach. So I’m wondering what’s blocking standard fields from syncing both ways.

Any help would be appreciated!

2

Hi, @NR-Smith :waving_hand: Thanks for your question. It’s a challenge to find related posts for your topic (not your fault, just not that common), I’d like to invite some of our community members to the conversation who’ve answered similar questions. Hey @danmoyle @franksteiner79 @TomM2 do you have any experience with this integration?

Thank you! — Jaycee
Please note, due to the US holiday this week, there may be a delay in getting responses from our US-based community members.

3

I can answer this one myself as I’ve just discovered some things.

The Hubspot opt-out field does not allow external manipulation. Therefore, if you have an external platform that manages opt-out, that platform can only send data to Hubspot through a custom field. That custom field can trigger a workflow configured to address this limitation and complete the Opt-Out field in Hubspot.

4

Thanks for the tag @Jaycee_Lewis . Hey there @NR-Smith and welcome to the Community.

In a little research I did, as I’m not an expert on Outreach or APIs, I found that it seems like maybe this is issue with the Outreach.io and HubSpot integration (and the Opted Out field not syncing bidirectionally) is somehat of a known problem. I’ll share a couple of links I found below.

I think the problem revolves around a limitation in how Outreach specifies field types for standard fields. Your observation about the custom-created boolean field “opted out” in HubSpot syncing bidirectionally with Outreach seems right. Custom fields are often handled differently in integrations, allowing for more flexible mapping.

A few options that may help include:

  • Continue using the custom boolean field as a workaround for bidirectional syncing of opt-out status.
  • Contact Outreach.io support to inquire about updates or fixes for standard field syncing issues.
  • Review and adjust the integration settings in both HubSpot and Outreach to ensure proper field mapping.

I’d also keep in mind that software changes and check for any recent updates to either platform that might have affected the integration. Then I’d verify that you have the necessary permissions and settings enabled for bidirectional syncing in both systems. Sometimes that simple step can fix something - kind of like “turn it off and back on again” :joy:

If this doesn’t fix it, I’d contact both sides of the integrastion with HubSpot and Outreach.io support teams for further assistance, as they may have more recent information or specific solutions for this syncing problem.

Here are a few resources I pulled from:

Outreach.io syncing tasks

Syncing Outreach Changes

Can I connect Outreach and HubSpot via data sync by HubSpot?

Hopefully that helps a bit.