# SailPoint Trigger Connector Documentation

> Trigger Connector Documentation

# Documentation

# Connecting SailPoint and Trigger

To connect SailPoint to the source, perform the following tasks:

## Adding and Configuring the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

1. Go to **Admin \> Connections \> Sources**.
2. Select **Create New**.
3. Search for a source type and select **Actions**.
4. In the **Actions** dropdown, select the setup method:

   - **Express Setup** - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     > **Note**
     >
     > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>). For more information, contact your SailPoint Customer Service Manager.
   - **Standard Setup** - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Express Setup

1. Review the directions and select **Start Express Setup**.
2. Review the pre-populated source name, source owner, and description. To update, select **Edit**.

   > **Note**
   >
   > Source name must be unique.
3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** page.
5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation.

   - If you want to aggregate now, select **Aggregate**.

     - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**.
     - To see the list of aggregated source accounts, go to **Account Management \> Accounts**.
   - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet.

### Standard Setup

Configure more detailed settings relative to Express Setup.

1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
4. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Here, continue to configure your connected source.

## Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a descriptive **Source Name** for the connection.
2. Enter the **Source Description** that provides details necessary to distinguish it from similar connection sources.
3. In **Source Owner**, begin typing the name of the source owner.
4. (Optional) Select the appropriate **Governance Group for Source Management** from the dropdown list. For more information about governance groups, refer to [Associating Governance Groups with a Source](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
5. Select **Create Manual Work Items** to enable the source to support additional source management features such as creating accounts and access profile management.

   > **Important**
   >
   > Once you enable this feature, it can't be disabled.

   For more information on manual work items, refer to [Work Items](<https://developer.sailpoint.com/docs/api/work-items>). For more information on SailPoint features, refer to [SailPoint Identity Services](<https://documentation.sailpoint.com/saas/help/index.html>).
6. Select **Save**.

## Connection Settings

Configure a secured, direct connection to the source.

1. Enter the Trigger host as **Base URL**. Do not append `/api/v1`. For example, `https://www.triggerapp.com`.
2. Enter the User token as **User Token**.
3. Enter the Account API key as **API Key**.
4. Select **Save**.

## Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to **Review and Test**.
2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.
3. Select **Test Connection**.

## SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface.

For more information, refer to [Application Onboarding](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.

# Integrating SailPoint with Trigger

Trigger is a project management and time-tracking application at [triggerapp.com](<https://www.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](<https://documentation.sailpoint.com/saas/help/sources/index.html#source-and-connector-definitions>).

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) 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](<https://www.triggerapp.com/>) 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:

```text
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:

- [Trigger website](<https://www.triggerapp.com/>)
- [Trigger API](<https://www.triggerapp.com/developers>)

> [!NOTE]
>
> The linked document is not maintained by SailPoint and is subject to change without notice.

# Schema Reference

The application schema is used to configure the objects returned from a connector.

> [!NOTE]
>
> - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The Trigger connector uses the following default correlation and object configurations.

## Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.

### Default Account ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*.

> [!CAUTION]
>
> Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
>
> To resolve issues caused by changing account IDs, reconfigure them to their default values.

The following table lists the default account IDs for this connector:

| Account ID | Schema Object Type |
| --- | --- |
| Id | Account |

### Default Account Attributes

The Trigger connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

| Attribute Name | Description |
| --- | --- |
| Id | Unique identifier of the user |
| Name | Display name of the user |
| Email | Email address of the user |
| Username | Username of the user |
| Phone | Phone number of the user |
| State | Account state of the user |
| Created At | Date when the user account was created |
| Last Connection | Date of the user's last connection |
| Role | Role assigned to the user |
| Companies | Companies assigned to the user |

## Default Entitlement Attributes

Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements](<https://documentation.sailpoint.com/saas/help/access/entitlements.html>) for more information.

> [!CAUTION]
>
> Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.

| Attribute Name | Description |
| --- | --- |
| Id | Unique identifier of the company |
| Name | Name of the company |
| Status | Status of the company |
| Country | Country of the company |