Skip to main content

Pipeliner proof types and permissions

Written by Hyperproof Support
Updated this week

Hyperproof uses Merge, a third-party API, to retrieve data from customer relationship management (CRM) apps. Hyperproof uses the User:Read scope. If you are interested in learning more about the permissions needed for CRM 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 Pipeliner on a control or label, you can automatically collect the following proof types:

Pipeliner proof types and fields

Proof type

Fields

Testable

List of Accounts

Name, Industry, Website, Owner, Created

Yes

List of Contacts

Name, Account, Created

Yes

List of Opportunities

Name, Description, Amount, Status, Stage, Account, Owner, Close Date, Created

Yes

List of Users

Name, Email, Active, 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 Pipeliner and collect proof, your Pipeliner configuration must meet the following requirements.

  • Domain - Your Pipeliner domain. To generate:

    1. Log in to Pipeliner and select Units, Users & Roles.

    2. Select the Applications tab and click Create New.

    3. Enter a name and your email address to create the application.

    4. Click Show API Access.

    5. Copy the Service URL without the https:// part. For example, if the URL is https://us-east.api.pipelinersales.com, copy us-east.api.pipelinersales.com.

  • Application Credentials and Space ID -

    1. In Pipeliner, select Units, Users & Roles.

    2. Select Applications and click your application.

    3. Click Show API Access.

    4. Copy the Username and Password.

    5. Copy the Space ID.

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

Authentication type: Custom​

Custom authentication parameters: Domain, Username, Password, Space ID

When you configure a Hypersync for Pipeliner for the first time, you must provide the following information:

  • Domain

  • Username

  • Password

  • Space ID

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 Pipeliner

  1. From the left menu, select either Controls or Labels, depending on the object you want to link to the Hypersync.

  2. Select the control or label for which you want to automate proof.

  3. Select the Automations tab.

  4. Click Create Hypersync.

    The Choose app window opens.

  5. 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.

  6. 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.

  7. 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.

Did this answer your question?