Troublesome Third-Party Integration Guide

How It Works
Troublesome uses a resource integration model. Each third-party connection is configured as a "resource" by an account administrator. TroubleSome supports two primary authentication methods:

OAuth 2.0 — Used by most integrations. Troublesome initiates a secure authorization flow where users grant access through the third-party provider's consent screen. Tokens are managed and refreshed automatically.

API Key / Credentials — Some integrations use API keys or client credentials provided directly during setup.

Supported Integrations

• Integration Auth Method Category

• Atlassian (Jira/Confluence) OAuth 2.0 ALM

• Google Calendar OAuth 2.0 Collaboration

• Google Workspace OAuth 2.0 Collaboration

• QuickBooks OAuth 2.0 Accounting

• Microsoft 365 OAuth 2.0

​

Collaboration

• Microsoft Project OAuth 2.0 PM

• HCSS OAuth 2.0 Construction

• Oracle P6 OAuth 2.0 / Basic Auth PM

• Smartsheet OAuth 2.0 PM

• Trimble Vista API Key Construction

• Trello API Key + Token Collaboration

Setup Flow

1. Admin navigates to Admin > Resource

2. Management in Troublesome

3. Select the integration type and fill in required configuration (API keys, OAuth app credentials, URLs, etc.)

For OAuth integrations: the admin is redirected to the third-party provider's authorization page to grant access.

4. Upon approval, Troublesome receives and securely stores the access tokens.

Troublesome automatically refreshes tokens and manages the connection lifecycle going forward.

 

Security
All credentials are stored in AWS Secrets ManagerOAuth tokens are automatically refreshed before expiration.

Connections are scoped to the minimum permissions required.

All communication uses HTTPS/TLS encryption.