Skip to content

Integrating SailPoint with Trigger

Trigger is a project management and time-tracking application at triggerapp.com. Use this connector to bring Trigger users and their access into SailPoint for Quick Compliance. This connector is for triggerapp.com only. It does not connect to other products that use the name Trigger. This document provides the instructions required to configure a new direct connection between SailPoint and Trigger. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.

Supported Features

The Trigger connector supports the following:

Account Management

  • Aggregate Users

Entitlement Management

  • Aggregate Companies

Note

User role is captured as part of account aggregation (embedded within the user record via the Role attribute, for example owner or employee). There is no separate Role group type, because Trigger does not provide a role catalog. This connector is read-only. It supports account and entitlement aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported in this release.

Important

Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:

  • Organization Admins: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
  • Regular Users: Limited to 1 manual account or entitlement aggregation per day per source.

These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

Prerequisites

Before you configure the Trigger connector, ensure the following requirements are met:

  1. Sign in to Trigger with a user who can see the users and companies you intend to govern.
  2. Select your profile picture (upper-right corner), then select My Settings.
  3. Scroll to the bottom of the page and copy the user token and the API key. Both values are required. The user token belongs to the signed-in user. The API key belongs to the Trigger account.
  4. Record the Base URL.

(Optional) You can confirm the credentials before configuring SailPoint:

curl -G 'https://www.triggerapp.com/api/v1/me' \
  --data-urlencode 'token=<USER_TOKEN>' \
  --data-urlencode 'api_key=<API_KEY>' \
  --data-urlencode 'format=json'

The response returns HTTP 200 and the current user when the credentials are valid. HTTP 403 with Invalid Token means the user token, the API key, or both are incorrect, or they do not belong to the same account. Example placeholder values such as YOUR_TOKEN will fail.

Note

  • Every API request requires both the user token and the account API key as query parameters, with format=json.
  • There is no access token, refresh token, or token endpoint. SailPoint stores the user token and API key and sends them on each request.
  • The user token and API key must be from the same Trigger account. Mixing a token from one user with an API key from another account fails authentication.
  • If either value is rotated in My Settings, update the stored values on the source before the next aggregation, or authentication will fail.
  • Treat both values as secrets. They are stored encrypted on the source.

Required Permissions

Any user who can open My Settings can copy their user token. The API key on that page is the account API key. Use an account that can list all users and companies you intend to govern. If that user cannot see some companies or users in Trigger, aggregation will omit them. Access is whatever the authenticated user can see in Trigger. There are no separate application scopes.

  • Test connection uses the current user.
  • Account aggregation lists users on the account, including each user's role (for example owner or employee).
  • Entitlement aggregation lists companies.
  • Company membership on the account is determined from each company's user list. Trigger does not return companies on the user record.

Key behaviors to account for:

  • If the user token or API key is invalid, requests return 403 regardless of who created the source.
  • If the authenticated user cannot see a company or user in Trigger, those objects are missing from aggregation rather than returned as an authorization error.
  • Role is an entitlement on the account. There is no separate Role group type, because Trigger does not provide a role catalog.

For more information about Trigger, refer to the following:

Note

The linked document is not maintained by SailPoint and is subject to change without notice.