Skip to main content

Outreach

This integration enables Orbb to connect with Outreach, allowing event invitees to be enrolled into your sequences from the right rep's mailbox, with engagement outcomes flowing back into Orbb automatically. The integration uses OAuth2 authentication to securely connect to your Outreach instance.

Prerequisites​

  • An Outreach account with administrative access
  • Permission to authorize OAuth2 applications in your Outreach instance
  • At least one enabled sequence, and a connected mailbox for each rep who will be sending
caution

Only users with admin privileges can perform these actions. Ensure you have the necessary permissions before proceeding.

OAuth Scopes​

The following OAuth scopes are required for the integration to function properly:

prospects.all
sequences.read
sequenceStates.all
mailboxes.read
users.read
mailings.read
webhooks.all
OAuth Scopes Explanation

Here's what each scope enables:

  • Prospect-related scopes:

    • prospects.all: Look up prospects by email address and create them when no match exists

  • Sequence-related scopes:

    • sequences.read: List the sequences in your instance so one can be selected for an event
    • sequenceStates.all: Enroll prospects into a sequence, read enrollment progress, and remove an enrollment when someone should stop receiving it
    • mailings.read: Read the delivery details behind an enrollment's progress

  • Sender-related scopes:

    • mailboxes.read: Match each Orbb owner to their Outreach mailbox so messages send from the correct rep
    • users.read: View basic information about users in your Outreach instance

  • Outcome-related scopes:

    • webhooks.all: Register the webhook Orbb uses to receive engagement updates
note

Outreach scopes are non-additive — granting prospects.write does not also grant read access — so every capability is requested explicitly.

Integration Steps​

1. Start OAuth2 Authorization​

  1. In your Orbb dashboard, navigate to Admin Center → Calls Integrations → Outreach
  2. Click Connect
  3. You will be redirected to Outreach's authorization page

2. Authorize Orbb​

  1. Review the requested permissions (scopes)
  2. Approve the requested access to authorize Orbb
  3. You will be redirected back to Orbb with the integration configured
tip

After authorization is complete, click the Test button to verify the connection. A green icon will appear if everything is working correctly.

3. Webhook Registration​

No manual setup is required. When the connection succeeds, Orbb automatically registers a webhook inside your Outreach instance to receive engagement updates. The registration is scoped to Orbb's application, so it does not affect any other webhooks you have configured, and reconnecting replaces the existing registration rather than adding a duplicate.

What Orbb Does With It​

Once connected, Outreach becomes available as a sequencing destination for your event invitees:

  • Prospect matching — invitees are matched to existing Outreach prospects by email address, and created only when no match exists
  • Sender mapping — each invitee's Orbb owner is matched to their Outreach mailbox, so messages send from the rep who owns the relationship rather than from a shared sender
  • Enrollment — approved invitees are enrolled into the sequence chosen for the event. Re-pushing the same invitee is safe: Orbb reuses the existing enrollment instead of creating a duplicate
  • Outcome sync — replies, bounces, opt-outs, pauses and completions appear on the event's invite list as they happen. A background reconciliation runs on a schedule as well, so statuses stay correct even if a webhook delivery is missed
  • Withdrawal — removing an invitee, for example when an event fills up, removes their enrollment in Outreach
note

Opt-outs are always respected. A prospect that Outreach reports as opted out is never enrolled, and the invitee is flagged in Orbb instead.

Security Considerations​

  • The OAuth2 connection is secure and can be revoked at any time from your Outreach instance settings
  • Access and refresh tokens are encrypted at rest and isolated per organization
  • Access tokens are short-lived and refreshed automatically; refresh tokens rotate on every use
  • Every inbound webhook is verified with an HMAC-SHA256 signature against a secret unique to your connection — unsigned or mismatched payloads are rejected
  • Orbb uses token-based authentication and does not store your Outreach user credentials

Troubleshooting​

If you encounter any issues:

  1. Verify that the OAuth2 authorization was successful and that the required scopes were granted
  2. Ensure your Outreach account has the necessary administrative privileges
  3. A sequence is missing from the picker — confirm the sequence exists and is enabled in Outreach
  4. A rep's invitees fail to send — confirm that rep has a connected, sending-enabled mailbox in Outreach whose email address matches their email in Orbb
  5. Statuses appear out of date — the scheduled reconciliation will correct them shortly; if the problem persists, reconnect the integration to re-register the webhook
  6. Try disconnecting and reconnecting the integration if issues persist