Connectors Overview
aprity connectors let you publish generated Salesforce documentation directly to external platforms. 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: Enterprise
Coming Soon
Notion
Publish documentation to Notion workspaces with native formatting and database integration.
Status: In development.
Future Connectors
The following connectors are on the aprity roadmap:
| Connector | Use Case |
|---|---|
| Jira | Automatically create or update Jira tickets when documentation changes are detected. |
| Slack | Send notifications to Slack channels when new documentation is generated. |
| Google Drive | Export documentation files directly to Google Drive folders. |
Connector availability depends on your plan. Enterprise plans include access to all available 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 Enterprise 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's output format will still run but will skip the publishing step. The generated documentation remains available for download in the Document Browser.
How Connectors Work with Scans
When you select an output format tied to a 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 generated files are available for manual download.