Skip to content

Commit 2b25584

Browse files
authored
Merge pull request #3551 from trycompai/chore/refresh-integrations-catalog
chore: refresh integrations catalog (583 → 590)
2 parents 09aa8ba + dbffb49 commit 2b25584

98 files changed

Lines changed: 1070 additions & 312 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎integrations-catalog/README.md‎

Lines changed: 39 additions & 32 deletions
Large diffs are not rendered by default.

‎integrations-catalog/index.json‎

Lines changed: 126 additions & 63 deletions
Large diffs are not rendered by default.

‎integrations-catalog/integrations/15five.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
"authConfig": {
99
"type": "api_key",
1010
"config": {
11-
"setupInstructions": "1. Log in to 15Five at https://my.15five.com\n2. Go to Settings → Integrations → API\n3. Generate an API key\n4. Enter it below",
11+
"setupInstructions": "1. Log in to 15Five at https://my.15five.com\n2. Go to Settings → Integrations → API\n3. Generate an API key\n4. Enter it below\n5. If you get a 401 error, try regenerating the API key (15Five keys expire 1 year from creation; API access may vary by plan tier).",
1212
"credentialFields": [
1313
{
1414
"label": "API Key",

‎integrations-catalog/integrations/1password.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@
4141
{
4242
"slug": "onepassword_signin_attempts",
4343
"name": "Employee Access",
44-
"description": "Reviews recent 1Password sign-in attempts for unauthorized access and suspicious activity",
44+
"description": "Reviews recent 1Password sign-in attempts via the Events API and surfaces aggregate evidence (success/failure counts, unique users, unique IPs, latest sign-in). Fails if the Events Reporting token is missing the \"signinattempts\" scope or no sign-ins are returned.",
4545
"defaultSeverity": "high",
4646
"enabled": true
4747
}

‎integrations-catalog/integrations/360learning.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
"authConfig": {
99
"type": "custom",
1010
"config": {
11-
"setupInstructions": "1. Log in to 360Learning as an admin\n2. Go to Settings > API\n3. Copy your Company ID and API Key (v1 credentials)\n4. If you don't have API credentials, contact your 360Learning Customer Success Partner (CSP)\n5. Enter both values below\n\nNote: API v2 credentials are NOT compatible. Use API v1 credentials only.",
11+
"setupInstructions": "1. Log in to 360Learning as an admin\n2. Go to Settings > API\n3. Copy your Company ID and API Key (v1 credentials)\n4. If you don't have API credentials, contact your 360Learning Customer Success Partner (CSP)\n5. Enter both values below\n\nNote: API v2 credentials are NOT compatible. Use API v1 credentials only.\n\nNote: this integration uses 360Learning API v1, which the vendor plans to sunset in mid-2027. A migration to API v2 will be required before then.",
1212
"credentialFields": [
1313
{
1414
"label": "API Key",

‎integrations-catalog/integrations/activtrak.json‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,22 +33,22 @@
3333
"checks": [
3434
{
3535
"slug": "activtrak_monitoring_alerting",
36-
"name": "Monitoring & Alerting",
37-
"description": "Verifies ActivTrak activity monitoring is active by checking for recent activity data collected by deployed agents",
36+
"name": "ActivTrak User Activity (Last 7 Days)",
37+
"description": "Confirms ActivTrak agents are reporting activity by reading the working-hours report for the last 7 days; surfaces per-user totals as evidence. Note: this is not an alarm/alert configuration check — it verifies end-to-end monitoring is functioning.",
3838
"defaultSeverity": "medium",
3939
"enabled": true
4040
},
4141
{
4242
"slug": "activtrak_employee_access",
4343
"name": "Employee Access",
44-
"description": "Lists all ActivTrak console users (consumers) with their roles and group access permissions",
44+
"description": "Lists all ActivTrak console users (consumers) with email, SSO status, and viewable groups for access-review evidence. Uses Authorization: Bearer auth.",
4545
"defaultSeverity": "medium",
4646
"enabled": true
4747
},
4848
{
4949
"slug": "activtrak_device_list",
5050
"name": "Device List",
51-
"description": "Lists all monitored devices (user agents/clients) registered in ActivTrak",
51+
"description": "Lists all monitored ActivTrak agents (clients) with id/name/domain/alias. Uses Authorization: Bearer auth.",
5252
"defaultSeverity": "medium",
5353
"enabled": true
5454
}

‎integrations-catalog/integrations/airbyte.json‎

Lines changed: 17 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,17 +4,29 @@
44
"description": "Monitor Airbyte data integration pipelines for connection status and workspace access compliance",
55
"category": "Cloud",
66
"docsUrl": "https://reference.airbyte.com/reference/getting-started",
7-
"baseUrl": "https://api.airbyte.com/",
7+
"baseUrl": "https://api.airbyte.com",
88
"authConfig": {
9-
"type": "api_key",
9+
"type": "custom",
1010
"config": {
11-
"setupInstructions": "1. Log in to Airbyte Cloud at https://cloud.airbyte.com\n2. Go to Settings → API Keys\n3. Generate a new API key\n4. Copy and enter it below",
11+
"setupInstructions": "1. Log in to Airbyte Cloud at https://cloud.airbyte.com (or your self-hosted instance).\n2. Go to Settings > Applications.\n3. Create a new Application; copy the Client ID and Client Secret (secret shown only once).\n4. Paste them above. For self-hosted Airbyte, also enter your API Base URL.\n5. Comp will exchange these for short-lived access tokens automatically.",
1212
"credentialFields": [
1313
{
14-
"label": "API Key",
14+
"label": "Client ID",
15+
"type": "text",
16+
"required": true,
17+
"helpText": "Airbyte Cloud Application Client ID. Settings > Applications > Create Application."
18+
},
19+
{
20+
"label": "Client Secret",
1521
"type": "password",
1622
"required": true,
17-
"helpText": "Found in Airbyte Cloud Settings → API Keys"
23+
"helpText": "Airbyte Cloud Application Client Secret. Shown once at application creation."
24+
},
25+
{
26+
"label": "API Base URL (optional, self-hosted only)",
27+
"type": "text",
28+
"required": false,
29+
"helpText": "Defaults to https://api.airbyte.com for Airbyte Cloud. For self-hosted Airbyte, enter your instance URL (e.g. https://airbyte.example.com/api/public)."
1830
}
1931
]
2032
}

‎integrations-catalog/integrations/aircall.json‎

Lines changed: 16 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,23 @@
66
"docsUrl": "https://developer.aircall.io/api-references/",
77
"baseUrl": "https://api.aircall.io",
88
"authConfig": {
9-
"type": "basic",
9+
"type": "custom",
1010
"config": {
11-
"setupInstructions": "1. Log in to Aircall Dashboard at https://dashboard.aircall.io\n2. Go to Company Settings\n3. In the API Keys section, click 'Add a new API key'\n4. Copy the API ID and API Token\n5. Enter them below",
12-
"usernameField": "api_id",
13-
"passwordField": "api_token"
11+
"setupInstructions": "IMPORTANT: Do not enter your Aircall account email and password here. Aircall requires a separate API key, which generates an API ID and API Token. Paste those values below — NOT your account login.\n\nYou must be an Admin or Owner in Aircall to create company-level API keys.\n\n1. Log in to the Aircall Dashboard at https://dashboard.aircall.io\n2. Click on the gear icon, then go to Company Settings > Integrations & API > API Keys\n3. Click \"Add a new API key\" and give it a name (e.g. \"Comp AI\")\n4. Aircall will show you the API ID and API Token once. Both are long random strings.\n5. Copy BOTH values immediately — they are shown only once\n6. Paste the API ID into the \"API ID\" field below and the API Token into the \"API Token\" field\n\nIf the integration shows 403 Forbidden errors later, the API key has likely been regenerated or revoked on the Aircall side. Create a new one and update the values here.",
12+
"credentialFields": [
13+
{
14+
"label": "API ID",
15+
"type": "text",
16+
"required": true,
17+
"helpText": "The API ID generated in Aircall Dashboard > Company Settings > Integrations & API > API Keys. This is a long random string, NOT your Aircall account email."
18+
},
19+
{
20+
"label": "API Token",
21+
"type": "password",
22+
"required": true,
23+
"helpText": "The API Token shown alongside the API ID. This is a long random string, NOT your Aircall account password. Aircall shows it only once at creation time."
24+
}
25+
]
1426
}
1527
},
1628
"capabilities": [

‎integrations-catalog/integrations/airtable.json‎

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,16 @@
77
"baseUrl": "https://api.airtable.com/",
88
"authConfig": {
99
"type": "api_key",
10-
"config": {}
10+
"config": {
11+
"setupInstructions": "1. Go to https://airtable.com/create/tokens and sign in.\n2. Click \"Create new token\".\n3. Grant the following scopes:\n - schema.bases:read (list bases and their permission levels)\n - user.email:read (identify the token owner)\n4. Under \"Access\", choose \"All current and future bases in all current and future workspaces\".\n5. Create the token and copy the value (starts with \"pat\").\n6. Paste it into the Personal Access Token field above.\n\nNote: Listing all workspaces requires an Airtable Enterprise plan and additional enterprise scopes. These checks operate at the bases level so they work for every plan tier.",
12+
"credentialFields": [
13+
{
14+
"label": "Personal Access Token",
15+
"type": "password",
16+
"required": true
17+
}
18+
]
19+
}
1120
},
1221
"capabilities": [
1322
"checks"
@@ -18,14 +27,14 @@
1827
{
1928
"slug": "airtable_employee_access",
2029
"name": "Employee Access",
21-
"description": "Reviews Airtable bases and verifies workspace is properly configured",
30+
"description": "Verifies the Personal Access Token owner and the bases reachable for employee access auditing.",
2231
"defaultSeverity": "medium",
2332
"enabled": true
2433
},
2534
{
2635
"slug": "airtable_access_review",
2736
"name": "Access Review Log",
28-
"description": "Reviews Airtable workspace configuration for access controls",
37+
"description": "Reviews Airtable bases and their permission levels to support access reviews.",
2938
"defaultSeverity": "medium",
3039
"enabled": true
3140
}

‎integrations-catalog/integrations/amplitude.json‎

Lines changed: 17 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,24 @@
44
"description": "Monitor Amplitude projects and user access for product analytics compliance",
55
"category": "Monitoring",
66
"docsUrl": "https://www.docs.developers.amplitude.com/analytics/apis/management-api/",
7-
"baseUrl": "https://management.us.amplitude.com/",
7+
"baseUrl": "https://core.amplitude.com",
88
"authConfig": {
9-
"type": "api_key",
10-
"config": {}
9+
"type": "custom",
10+
"config": {
11+
"setupInstructions": "1. Sign in to Amplitude as an Organization Admin.\n2. Go to Settings > Organization > SCIM (requires the SCIM/SSO add-on on your plan).\n3. Generate a SCIM API token and copy it (starts with scim_).\n4. Paste the token above and select your data region (US or EU).\n5. Note: SCIM endpoints require the SCIM add-on. If your plan does not include SCIM, the Employee Access check will return an actionable failure.",
12+
"credentialFields": [
13+
{
14+
"label": "SCIM Token",
15+
"type": "password",
16+
"required": true
17+
},
18+
{
19+
"label": "Region",
20+
"type": "select",
21+
"required": true
22+
}
23+
]
24+
}
1125
},
1226
"capabilities": [
1327
"checks"

0 commit comments

Comments
 (0)