Bridge Integrations

Evidence collection is a critical part of maintaining compliance and preparing for audits. Strike Graph's Bridge integrations provide a flexible, API-driven solution to collect evidence from external services directly through their APIs.

What are Bridge Integrations?

Bridge integrations are flexible type of integration that allows you to connect Strike Graph to external services so that you can use their API for evidence collection. Unlike our dedicated integrations that come with predefined evidence collection options, Bridge integrations let you specify exactly what API endpoints to call and what data to collect.

Think of Bridge integrations as creating a direct "bridge" between Strike Graph and external services, giving you the power to:

• Make custom API calls to specific endpoints

• Define the HTTP method (GET or POST)

• Provide custom request bodies for POST requests

• Collect returned data as evidence

This approach provides maximum flexibility while maintaining the security and automation benefits of our integration framework.

How Bridge Integrations Work

Like all of our integrations, Bridge integrations come with two components:

1. Integration Manager configurations where you set up the permissions necessary to authorize Strike Graph to collect evidence from your systems. Strike Graph only requires (and generally recommends*) read-only access, meaning that your data and systems remain secure.

2. Evidence Collection & Automated Collection configurations where you link your integration with evidence objects and define what (and how frequently) you would like Strike Graph to collect evidence.

Bridge integrations are unique in that they provide a user-friendly interface for defining API requests without requiring deep technical knowledge. With just a few form fields, you can configure evidence collection from almost any API endpoint of supported services.

* Some authentication providers don't allow fine grain control of scopes or access; and just keep in mind that there may be reasons why you want write access for certain POST requests.

Configuring Bridge Integrations

Each Bridge integration requires authentication to allow Strike Graph to securely access the external service.

Currently supported Bridge integrations:

• ClickUp

Using Bridge Integrations to Collect Evidence

After you have configured a Bridge integration, you can define the evidence you'd like to collect. To get started, open the evidence object that you want to add an attachment to.

Once you have the evidence object selected, choose either direct attachment (for a one-time pull) or automated collection (recommended for ongoing compliance).

Basic Components of Bridge Evidence Collection

Bridge evidence collection has a simple form-based interface with these key components:

HTTP Method

Select the type of request you want to make:

• GET - Retrieve data from an endpoint

• POST - Send data to an endpoint and retrieve the response

API Route

Specify the API endpoint you want to access, as defined in the third party's API documentation. Since this is unique per provider, endpoints will vary, however the base URL will be specified by the integration so you only need to provide the route. For example, an API documentation may define endpoints like these that you can utilize:

• /api/v2/user - Get user information

• /api/v2/team - Get team information

• /api/v2/task/123456 - Get details of a specific task

Request Body (for POST requests)

For POST requests, you can provide a JSON-formatted request body with the specific parameters required by the API endpoint.

Data Collection

Once the API request is configured and submitted, Strike Graph uses this information to collect the necessary evidence attachment. This may take a moment to complete, but once finished you can view the information collected by clicking on the evidence attachment.

The data collected is stored as JSON and may be lightly formatted to make it more human-readable.

Troubleshooting

If you encounter an error while setting up a Bridge integration, consider these common issues:

Check permissions

Ensure you've given Strike Graph the necessary permissions to collect data from the service. While OAuth often handles most of this automatically, some services require additional permission settings.

Validate API endpoints

Make sure the API endpoints you're using are correct and accessible with the permissions you've granted. You may want to check the service's API documentation to confirm the correct endpoints and required parameters.

If these tips don't help, send us a message via the Messenger chat and we'll do our best to help troubleshoot.

Benefits of Bridge Integrations

Bridge integrations offer several advantages:

1. Flexibility - Access virtually any API endpoint the service offers

2. Customization - Tailor evidence collection to your specific needs

3. Automation - Schedule regular evidence collection to maintain compliance

4. Security - OAuth authentication ensures secure access without sharing credentials

5. Simplicity - No coding required, just fill out a form to define your API request

By leveraging Bridge integrations, you can further streamline your compliance workflow and ensure you're collecting the evidence you need, exactly how you need it.