Connectors Overview
aprity connectors let you publish generated Salesforce documentation directly to external platforms and connect AI tools to your org documentation. Instead of manually downloading and uploading files, connectors automate the delivery of documentation to the tools your team already uses.
Available Connectors
Confluence
The Confluence connector publishes aprity-generated documentation directly to your Atlassian Confluence workspace. Pages are created with proper formatting, hierarchy, and metadata.
Authentication: OAuth 2.0
Supported plans: Intelligence, Trial
Salesforce Knowledge
The Salesforce Knowledge connector publishes aprity documentation as Knowledge articles in your org, making documentation available in Experience Cloud portals and through Agentforce.
Authentication: Uses the existing JWT Bearer connection
Supported plans: Intelligence, Trial
See: Salesforce Knowledge Output
Jira Cloud — Story Agent
The Jira Cloud connector adds an AI-powered backlog panel inside Jira. It generates structured user stories grounded in your Salesforce org's metadata and business rules and can push them straight to your Jira backlog.
Authentication: Activation code (APRT-XXXX-XXXX)
Supported plans: Intelligence, Trial
Azure DevOps — Story Agent
The Azure DevOps connector adds a Story Agent hub to Azure Boards. It generates structured work items based on your org's real metadata and pushes them to your ADO Boards.
Authentication: Activation code (APRT-XXXX-XXXX)
Supported plans: Intelligence, Trial
See: Azure DevOps — Story Agent
Slack — Story Agent
The Slack connector provides a /aprity slash command to generate user stories from any channel, powered by your org's documentation.
Authentication: Activation code (APRT-XXXX-XXXX)
Supported plans: Intelligence, Trial
See: Slack — Story Agent
Agentforce — Help Agent
The Agentforce channel exposes the aprity Help Agent inside Salesforce, so users can ask natural-language questions about the org and get answers grounded in the latest scan. Set up via the guided wizard in the aprity app.
Authentication: Salesforce-native (uses the installed managed package)
Supported plans: Intelligence, Trial
See: Agentforce Setup
Bring Your Own LLM (BYOLLM)
BYOLLM lets you point aprity at your own approved LLM endpoint instead of the aprity-managed one, so analysis runs against a model you control. Configured per tenant.
Authentication: Endpoint credentials stored in aprity for your tenant
Supported plans: Intelligence only
AI Clients (Remote MCP Server)
A separate class of connectors lets your team's AI tools -- ChatGPT Desktop, Claude Desktop, Claude.ai, Claude Code, Cursor -- query your aprity-scanned org over the Model Context Protocol (MCP). Once connected, the AI client can answer questions, describe object behaviour, and draft user stories using your most recent scan as the source of truth.
This is different from the tracker connectors above : the tracker connectors push aprity output to your team's collaboration tools, while AI Clients let an AI assistant pull from aprity on demand.
You connect by pointing your AI client at the aprity MCP endpoint (https://mcp.aprity.ai/v1/mcp). The client runs an OAuth 2.1 + PKCE sign-in with Salesforce SSO; there is no activation code or hand-copied token. Disconnect from within the AI client at any time.
Authentication: Salesforce SSO (OAuth 2.1 + PKCE) -- no activation code
Supported plans: Intelligence, Trial
See: Remote MCP Server for the feature overview, and the per-client setup guides (ChatGPT, Claude Desktop, Claude.ai, Cursor).
Upcoming
See Upcoming Connectors for connectors currently on the roadmap (Notion, Google Drive).
Connector availability depends on your plan. The Confluence and Salesforce Knowledge publishers, Story Agent connectors (Jira / Azure DevOps / Slack), the Agentforce Help Agent channel, and AI Clients (MCP) are available on Intelligence and Trial plans. BYOLLM is Intelligence only. The Documentation plan does not include connectors.
Connecting to Confluence
Prerequisites
Before connecting, ensure you have:
- An Atlassian Confluence Cloud workspace.
- Administrator or space-level permissions in the target Confluence space.
- An active aprity Intelligence or Trial plan.
OAuth 2.0 Flow
- Navigate to the Connectors tab in the aprity app.
- Locate the Confluence card and click Connect.
- You are redirected to the Atlassian authorization page.
- Sign in with your Atlassian account and grant aprity the requested permissions.
- After authorization, you are redirected back to the aprity app.
- The Confluence card updates to show Connected status with your Atlassian account details.
The OAuth token has a limited lifetime. If the connection expires, you will need to re-authorize through the same flow. aprity displays a warning when the token is nearing expiration.
Connection Status
Once connected, the Confluence card displays:
- Connected account -- the Atlassian email used for authorization.
- Connection date -- when the OAuth flow was completed.
- Status indicator -- green for active, yellow for expiring soon, red for expired.
Disconnecting a Connector
To disconnect a connector:
- Navigate to the Connectors tab.
- Click the Disconnect button on the connector card.
- Confirm the disconnection in the dialog.
Disconnecting revokes the OAuth token and removes the connection from aprity. Previously published documentation in the external platform is not affected.
After disconnecting, any scan configured to use that connector will still run but will skip the publishing step. The generated documentation remains available in the portal.
How Connectors Work with Scans
When you enable a publishing connector (e.g., Confluence), aprity performs two steps during the scan finalization phase:
- Generate -- the documentation is produced in the connector-specific format.
- Publish -- the generated content is pushed to the connected platform.
If the publishing step fails (e.g., due to network issues or expired credentials), the scan still completes and the documentation remains available in the portal.