Context Sources
Context sources are integrations that give Promptless read-only access to your organization’s existing tools and data. They provide additional context that helps Promptless create more accurate and comprehensive documentation suggestions.
Context sources are one-way: Promptless reads information from these services to inform documentation updates, but never writes back to them. Your Jira tickets, Linear issues, and Confluence pages remain unchanged.
How Context Sources Work
Section titled “How Context Sources Work”Think of context sources as Promptless’s way of understanding your team’s unique ecosystem. When triggered to create documentation updates, Promptless intelligently searches through your connected tools to gather the most relevant context. This creates documentation that feels like it was written by someone who truly understands your project.
Context sources are optional but highly recommended. They can significantly improve the quality and relevance of Promptless’s documentation suggestions.
Available Context Sources
Section titled “Available Context Sources”
Linear
Access Linear issues, projects, and team workflows for project management context
Jira
Query Jira tickets and project data using JQL search capabilities
Confluence
Search Confluence spaces for existing documentation patterns, terminology, and architectural decisions
Notion
Search Notion pages and databases for product specs, internal documentation, and team knowledge
Examples
Section titled “Examples”Linear as a Context Source
Section titled “Linear as a Context Source”When a GitHub PR mentions a new feature, Promptless searches Linear for related issues to understand additional project context. This ensures your documentation includes the “why” behind code changes, not just the “what.”
Jira as a Context Source
Section titled “Jira as a Context Source”If a GitHub PR references a Jira ticket (like “PROJ-123”), Promptless automatically reads that Jira ticket for additional context. It also proactively searches Jira using JQL for related issues and epics.
Confluence as a Context Source
Section titled “Confluence as a Context Source”When writing documentation, Promptless searches your Confluence spaces for existing documentation patterns, terminology, and architectural decisions. This ensures new documentation matches your team’s existing style and conventions.
Notion as a Context Source
Section titled “Notion as a Context Source”When a GitHub PR references a Notion page containing feature specifications, Promptless automatically fetches that page content. It also searches your Notion workspace for related product documentation, ensuring new docs align with existing feature definitions and terminology.
Configuring Context Sources
Section titled “Configuring Context Sources”Context sources are configured at the project level in your projects page. For each project, you can:
- Select which context sources to enable
- Configure search scope (e.g., specific teams, projects, or repositories)
- Set permissions for what Promptless can access
Data Privacy and Security
Section titled “Data Privacy and Security”Promptless prioritizes your data privacy and security with context sources:
Real-time Queries Only
We do not store any of your organization’s data from context sources. Instead, our agents query the relevant APIs in real-time when documentation updates are needed, ensuring that we only access the information required for the specific documentation task at hand.
Secure Authentication
All context source integrations use:
- OAuth 2.0 authentication
- Encrypted data transmission (TLS 1.2+)
- Granular permission controls
- Token-based access that can be revoked at any time
Minimal Data Access
Promptless only accesses the specific information needed for documentation generation and does not retain or cache this data after processing.
Requesting Additional Context Sources
Section titled “Requesting Additional Context Sources”Need integration with other tools? Contact help@gopromptless.ai to request additional context sources. We’re continuously expanding our integration options to better serve your documentation needs.