Integrations
Overview
Section titled “Overview”Integrations connect Promptless to the tools your team already uses. This page lists each integration and the jobs it does, explains the health labels on the Integrations page, and covers how organization admins manage connections. Each integration does one or more of these jobs:
| Job | What the integration does |
|---|---|
| Triggers | Sends Promptless events, automatically or when someone asks, that can start documentation work. |
| Context | Gives Promptless information to research while it drafts documentation. |
| Publishing | Lets Promptless push documentation updates to your Git-hosted docs. |
| Monitoring | Reports on a connected service, such as whether your Starport site’s Vercel deployment built and published. |
Some integrations in beta aren’t listed here. To ask about an integration that isn’t listed, or to request a new one, contact help@gopromptless.ai.
Available integrations
Section titled “Available integrations”Each integration’s page covers how to connect it and what it can reach:
| Integration | Used for | What Promptless does with it |
|---|---|---|
| GitHub | Triggers, context, publishing | Triggers on pull requests, commits, and issues, reads code for context, and publishes to GitHub repositories. |
| GitHub (read-only) | Triggers, context, publishing to public repositories | Reads any repository you grant, including private code, and publishes to public repositories through a pull request from a fork. |
| GitHub Enterprise | Triggers, context, publishing | Connects GitHub Enterprise Server and Enterprise Cloud through a custom GitHub App. |
| GitLab | Triggers, context, publishing | Triggers on merge requests, reads source code for context, and publishes to GitLab projects. |
| Atlassian | Triggers, context | Triggers on Jira issues, and reads Jira issues and Confluence spaces for context. |
| Linear | Context | Reads Linear issues and projects for context. |
| Notion | Context | Searches Notion pages and databases for product specs and internal documentation. |
| Google Drive | Context | In beta. Searches Google Drive, and reads Docs, Sheets, and Slides for context. |
| Slite | Context | Searches Slite notes for internal documentation and product context. |
| Slack | Triggers, context | Triggers on mentions, message actions, DMs, and passive channel listening, and posts suggestion notifications. |
| Microsoft Teams | Triggers | In beta. Triggers on mentions, message actions, and passive channel listening. |
| LaunchDarkly | Triggers | In beta. Triggers on feature flag changes. |
| Vercel | Monitoring | Reads the deployment status of your Starport documentation site, with read-only access. |
Connection health
Section titled “Connection health”Once a day, Promptless checks each connected integration to confirm that its credentials are still valid and that the service is reachable. Each card on the Integrations page shows the result as a health label, along with when Promptless last checked:
| Label | What it means | What to do |
|---|---|---|
| Connected | The latest check succeeded. Promptless can reach the service and is authenticated. | No action needed. |
| Problem | The service was unreachable, or Promptless couldn’t verify the integration, during the latest check. | No action needed. Promptless checks again and returns the card to Connected when the check succeeds. |
| Needs reconnect | The authorization expired or was disconnected, and it needs you to reauthorize it. | Reconnect the integration from its card. |
Some cards use their own label for a problem state, such as Access check failed on a GitHub card. To see details for a problem state, select the label. The details show the time Promptless last confirmed the integration was healthy. For a Problem, they also show when Promptless first and last detected the issue. To check a connection right away, select the card’s check action, such as Check access. For symptoms and fixes by integration, see Connection health.
Proactive notifications
Section titled “Proactive notifications”If your organization has an escalation channel configured in Slack, Microsoft Teams, or email, Promptless reports connection problems there and names the affected integration. You learn about a broken integration without checking the Integrations page:
| Label | When Promptless notifies you |
|---|---|
| Needs reconnect | When the daily check first finds the problem, including when a Problem turns into it. |
| Problem | Once, after the problem has lasted at least 24 hours. A shorter problem sends no notification. |
Promptless doesn’t notify you again about the same ongoing problem. After the integration recovers, a new problem sends a new notification.
Manage integrations
Section titled “Manage integrations”Organization administrators view and manage every connected integration on the Integrations page in the Promptless dashboard:
| Task | What to do |
|---|---|
| Connect an integration | Select the integration’s connect button, such as Connect GitHub, and follow the steps on its page. |
| Recheck a connection | Select the card’s check action, such as Check access. |
| Change what an integration can reach | Select the card’s link to the provider, such as Configure in GitHub, and change access there. |
| Revoke Promptless’s access | Select the card’s disconnect button, such as Disconnect GitHub, and confirm. Promptless’s access to that service ends immediately. |
See also
Section titled “See also”- Connection health, to diagnose an integration that stopped working
- Data handling and classification, for how Promptless encrypts, stores, and retains data from connected services
- Configuration reference, for the triggers, context sources, and doc collections that use these integrations