# Outreach

![Outreach.svg](https://assets.relyanceuat.xyz/images/docs/34595124632717/34595124614029.svg)
Outreach is a Software as a Service (Saas) sales engagement tool that is designed for sales teams to connect other software and to make it easier to manage the team to increase sales. It is an intelligence platform that helps manage workflow, navigate the complex process, and instantly gain actionable insights.

In order to integrate Outreach with Relyance AI you will need to follow an **Oauth2** flow.

#### In the Relyance AI application:

1. Login to your Relyance AI account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **Outreach** integration card and click on it.
5. Click on the **Add Connection** button on the top right.
6. Provide a meaningful name for the integration and click on the **Add** button.
7. In the **Overview** section, review the **Scope and Permission**, **Additional Configurations** and **Endpoint** details and click on **Continue**. For more details, see [Integration Features](/docs/introduction-to-relyance-ai/integration-features/).
8. In the **Connection** section, provide the appropriate values and click on **Continue**,
    - **Connection Name**: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by **Discovery Source** across the **Inventory**, **Visual** **Maps**, **Assets**, and **Data Flow Analysis** pages.
    - **Rescan Frequency**: This property allows you to configure how often Relyance executes scans against this Vendor connection.
    - **Business Atlas Associations** (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the **Select Associations** dropdown — the wizard will not advance past this step without one. For more details, see [Business Atlas](/docs/other-settings/business-atlas-overview/).
9. In the **Authentication** section, Please choose the Oauth2 / App Token **Authentication Method,** click on **Authenticate**.
10. This step applies only if the **Data Inspection** check box was enabled in Step 7. In the Data Inspection section, provide the appropriate values and click on **Continue**,
    - **Minimum Confidence Level:** This property adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g., Very Low) offer more coverage but may produce false positives, while higher sensitivity (e.g., Very High) provides greater accuracy but less coverage.
11. Review the configuration summary from the **Completion** section and click on **Finish.**

![Screenshot 2025-02-27 at 6.13.43 PM.png](https://assets.relyanceuat.xyz/images/docs/34595124632717/34595092278797.png)

![Outreach_overview_20250224_202026.png](https://assets.relyanceuat.xyz/images/docs/34595124632717/34595092279437.png)

![Outreach_connection_20250224_202028.png](https://assets.relyanceuat.xyz/images/docs/34595124632717/34595124626061.png)

![Screenshot 2025-11-14 132512.png](https://assets.relyanceuat.xyz/images/docs/34595124632717/41134189253645.png)

![Outreach_data_inspection_20250224_202036.png](https://assets.relyanceuat.xyz/images/docs/34595124632717/34595092288269.png)

![Outreach_completion_20250224_202032.png](https://assets.relyanceuat.xyz/images/docs/34595124632717/34595092288909.png)

12. Confirm the integration Status reflects **Connected.**

<!-- failure-modes:begin (generated from the integration catalog; do not hand-edit) -->

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **A feature you enabled returns nothing.** Some scopes belong to a feature rather than to the connection: **Data subject requests** needs `calls.read`, `emailAddresses.read`, `phoneNumbers.read`, `prospects.read`, `prospects.delete`. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. **Authorised, then empty.** The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.

<!-- failure-modes:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

The **OAuth (browser authorization)** method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (`terraform import relyance_integration_connection.example outreach/<connection_id>`) or reading it with the `relyance_integration_connection` data source.

<!-- terraform-examples:end -->