> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rogeriq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

Connect channels, commerce tools, issue trackers, and developer systems.

# Integrations

Integrations bring outside context and actions into RogerIQ. They can power sidebar cards, AI tools, sync runs, channel accounts, and webhook-driven workflows.

## Integration Categories

| Category | Examples |
| --- | --- |
| Channels | Slack, Discord, Telegram, email, widget, forms. |
| Commerce | Shopify and Stripe. |
| Issue tracking | GitHub, Linear, Jira. |
| Web3 | Wallet lookup and transaction debugging. |
| Docs | HolyDocs and hosted docs sync. |
| Developer | API keys, OAuth apps, webhooks, custom actions. |

## Connection Types

| Type | Description |
| --- | --- |
| OAuth | User authorizes the provider in a popup, such as GitHub or Slack. |
| API key | User pastes provider credentials, such as Stripe or Linear. |
| Channel token | Channel account is connected for message ingestion and replies. |
| First-party docs sync | HolyDocs uses OAuth and API-key-backed sync endpoints. |

## Operational Advice

Connect only the systems the team will actually use. A shallow integration that appears in every workflow is worse than a narrow integration that reliably answers one high-value support question.

Document each integration owner, credential rotation path, and what the AI agent is allowed to do with it.