Explore Bots
Browse Bots Features Developers Pricing Docs Integrations Explore Bots

GitHub Integration

Discover, Manage, and Scale Discord Bots

Connect Your Repository View API Documentation
Setup Steps

Link Your Source Control

Establish a secure, bidirectional sync between your GitHub organization and BotNexus for automated dependency resolution, semantic versioning, and zero-downtime deployments.

All webhook payloads are signed with HMAC-SHA256 and require TLS 1.3. Follow the workflow below to configure your pipeline, manage environment variables, and trigger automated builds.

01. Generate OAuth Credentials

Navigate to GitHub's Developer Settings and create a new OAuth App. Assign the repo, admin:org, and workflow scopes. Copy the client ID and secret into your BotNexus dashboard under Integrations > GitHub.

02. Configure Webhook Secrets

Add the auto-generated signature to your repository's environment variables. Set the key to BOTNEXUS_WEBHOOK_SECRET and mark it as masked. This ensures payload verification for push, release, and pull_request events.

03. Define Pipeline Configuration

Create a .botnexus.yml file at your project root. Specify your runtime version (node:18.17.0), build script (npm run build), and deployment target (us-east-1). Reference your bot token via DISCORD_TOKEN: $BOTNEXUS_VAULT_TOKEN.

04. Trigger Initial Sync

Push your configuration to the main branch or create a version tag prefixed with v (e.g., v2.4.1). The CI runner will automatically clone the repo, resolve dependencies, and deploy a fresh container instance within 45 seconds.

05. Monitor Version Tracking

Visit the Deployments tab to view commit hashes, build durations, and uptime metrics. Enable automatic rollbacks if health checks on /api/ping fail for three consecutive intervals. Historical builds are retained for 90 days.

Initialize New Repository Sync Troubleshoot Webhook Failures