Skip to content

For the complete documentation index, see llms.txt.

Integrations

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:

JobWhat the integration does
TriggersSends Promptless events, automatically or when someone asks, that can start documentation work.
ContextGives Promptless information to research while it drafts documentation.
PublishingLets Promptless push documentation updates to your Git-hosted docs.
MonitoringReports 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.

Each integration’s page covers how to connect it and what it can reach:

IntegrationUsed forWhat Promptless does with it
GitHubTriggers, context, publishingTriggers on pull requests, commits, and issues, reads code for context, and publishes to GitHub repositories.
GitHub (read-only)Triggers, context, publishing to public repositoriesReads any repository you grant, including private code, and publishes to public repositories through a pull request from a fork.
GitHub EnterpriseTriggers, context, publishingConnects GitHub Enterprise Server and Enterprise Cloud through a custom GitHub App.
GitLabTriggers, context, publishingTriggers on merge requests, reads source code for context, and publishes to GitLab projects.
AtlassianTriggers, contextTriggers on Jira issues, and reads Jira issues and Confluence spaces for context.
LinearContextReads Linear issues and projects for context.
NotionContextSearches Notion pages and databases for product specs and internal documentation.
Google DriveContextIn beta. Searches Google Drive, and reads Docs, Sheets, and Slides for context.
SliteContextSearches Slite notes for internal documentation and product context.
SlackTriggers, contextTriggers on mentions, message actions, DMs, and passive channel listening, and posts suggestion notifications.
Microsoft TeamsTriggersIn beta. Triggers on mentions, message actions, and passive channel listening.
LaunchDarklyTriggersIn beta. Triggers on feature flag changes.
VercelMonitoringReads the deployment status of your Starport documentation site, with read-only access.

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:

LabelWhat it meansWhat to do
ConnectedThe latest check succeeded. Promptless can reach the service and is authenticated.No action needed.
ProblemThe 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 reconnectThe 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.

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:

LabelWhen Promptless notifies you
Needs reconnectWhen the daily check first finds the problem, including when a Problem turns into it.
ProblemOnce, 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.

Organization administrators view and manage every connected integration on the Integrations page in the Promptless dashboard:

TaskWhat to do
Connect an integrationSelect the integration’s connect button, such as Connect GitHub, and follow the steps on its page.
Recheck a connectionSelect the card’s check action, such as Check access.
Change what an integration can reachSelect the card’s link to the provider, such as Configure in GitHub, and change access there.
Revoke Promptless’s accessSelect the card’s disconnect button, such as Disconnect GitHub, and confirm. Promptless’s access to that service ends immediately.