Skip to main content

Documentation Index

Fetch the complete documentation index at: https://archie.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Organization integrations apply across every project in your org. Configuring them once means each new project inherits the connection automatically.

​
Available integrations

The most common org-level integrations are GitHub and Slack. Connect them from Organization → Integrations.

​
GitHub

GitHub integration enables two-way code sync between Archie projects and your GitHub repositories. After connecting, every project in the org can push code to a GitHub repo and pull changes back. See Connecting GitHub for the full setup. The connection covers:
  • Pushing generated code to a repo
  • Pulling commits made outside Archie
  • Pull request creation from project changes
  • Branch-based deployment to environments

​
Slack

Slack integration sends project notifications (build success, deploy failures, mentions) to a channel of your choosing. Once connected, configure which categories trigger Slack messages from the notifications page.

​
Jira (Enterprise)

Jira integration lets Archie create issues from build errors and link blueprint changes to tickets. Available on Enterprise plans only.

​
Per-project vs. organization integrations

Some integrations live at the org level (GitHub, Slack, Jira) — they configure once and apply org-wide. Others live per-project (Stripe, SendGrid, Twilio) because each project has its own API keys and secrets. Per-project integrations are managed in the project’s Backend Integrations surface.

​
How do I connect GitHub?

Open Organization → Integrations, click GitHub, then Connect. Archie redirects you to GitHub’s OAuth flow. Approve the requested scopes, choose which repositories Archie can access (all, or selected), and confirm. The connection persists for the org. After connecting, individual projects can link to specific repositories from their own settings.

​
Disconnecting

Click Disconnect on the integration row. This removes Archie’s access to the third-party service for the entire org. In-flight syncs complete. Each project’s link to a specific repo or channel breaks, but project history stays intact.

​
Custom integrations

To connect a service Archie does not ship with, build a custom integration with Archie Core integrations. Custom integrations live at the project level, not the org level, since they typically use project-specific credentials.