![Hyperproof.Io [Test] Help Center](https://downloads.intercomcdn.com/i/o/xgk1dxp2/757668/427b255f2659cc7e0853d6a00ec1/628914ae2617199b7d999ba797a5305a.png)
Hyperproof uses Merge, a third-party API, to retrieve data from Ticketing apps. Hyperproof uses the Attachment, Collection, Role, Tag, Team, Ticket, and User scopes. If you are interested in learning more about the permissions needed for Ticketing Hypersyncs that use Merge, refer to the Merge Authentication Guides page in their Help Center.
Note: This Hypersync is not supported in Hyperproof Gov.
When you configure a Hypersync for Trello on a control or label, you can automatically collect the following proof types:
Trello proof types and fields
Proof type | Fields | Testable |
List of Groups | Name, Description, Remote ID | Yes |
List of Issues | Name/Subject, Status, Priority, Assignees, Creator, Due Date, Created, Updated, Completed, Tags, Ticket URL | Yes |
List of Users | Name, Email, Active, Teams, Roles, Remote ID | Yes |
Blocking sensitive data
When Hyperproof connects to a Merge Hypersync, we intentionally minimize data exposure and follow least-privilege principles. Sensitive data can't be blocked entirely from within Hyperproof; it can only be blocked at the source. We recommend working with the System Administrator for the app you are accessing to configure a service account specifically for Hyperproof with access only to the data you need the Hypersync to collect.
Requirements
To connect to Trello and collect proof, your Trello configuration must meet the following requirements.
You must be a Trello administrator.
API Key and Token - API key and token are only required if you are using the API key login method. To locate:
Log in to Trello and navigate to https://trello.com/app-key.
Go to the Power-Up Admin Portal to access your API keys.
Click New to create a new Power-Up and complete the fields displayed.
Click Generate a new API key.
Copy the API key and store it in a secure location.
Next to the API key you generated, click the Token link.
Copy the token and store it in a secure location.
Note: Hyperproof connects to many third-party systems that frequently change, including the system interface. Contact your System Administrator or the third-party provider for assistance in meeting the requirements to integrate with Hyperproof and collect the proof you need.
Connection configuration
User authentication
Authentication type: Oauth
Custom authentication parameters: Email, password
API key authentication
Authentication type: Custom
Custom authentication parameters: API key, Token
When you configure a Hypersync for Trello for the first time, you must provide the following information:
My credentials login (recommended) - You can log in with your email and password, a passkey, or a third-party authentication method, such as Google.
API key login - Requires an API key and token.
The first time you run this Hypersync, it may take up to 24 hours to load all data.
Note: You only need to connect Hyperproof to the app once, and then you can create as many Hypersyncs as you need.
Additionally, you can create multiple Hypersyncs for a single control or label.
Additional documentation
Connecting to Trello
From the left menu, select either Controls or Labels, depending on the object you want to link to the Hypersync.
Select the control or label for which you want to automate proof.
Select the Automations tab.
Click Create Hypersync.
The Choose app window opens.
Use the filter at the top of the Choose app window to find the app where the proof data will be pulled from, e.g., Azure or GitHub. You can search for apps by Name, App ID, or Category, such as Ticketing or Accounting apps.
Select your app.
The Connect window opens.
Note: Hyperproof uses Merge, a third-party API, to streamline the connection process. For more information on how Hyperproof integrates with Merge, please refer to the Hyperproof Security Overview.
Sign in to your account.
Note: Depending on the app, you might be asked for your username and password or a token. The sign-in process varies by app. See the Requirements and Connection configuration sections of the specific Hypersync document for more details.