Understanding Integrations

Integrations connect external services to your Devpilot workspace so you can deploy code from your repositories, provision servers on your preferred cloud, and receive notifications about workspace activity. Every integration is scoped to a single workspace, so teams can maintain their own connections independently.

Integration Types

Devpilot organises integrations into three categories, each with its own authentication method and capabilities.

Source Control Integrations

Source control integrations use OAuth authentication. You are redirected to your provider's consent screen, approve the permissions, and Devpilot stores the resulting token automatically. You never paste tokens manually.

Once connected, Devpilot can:

• List your repositories and branches
• Pull source code for each deployment
• Register webhooks for automatic deployment on push
• Refresh its own access token when required (GitLab and Bitbucket)

Available providers: GitHub, GitLab, Bitbucket

Cloud Provider Integrations

Cloud provider integrations use API credentials (access key and secret key, or provider-specific fields such as subscription and tenant IDs for Azure) that you generate in your cloud console and paste into Devpilot. Before saving, Devpilot validates the credentials by making a read-only API call so you find out immediately if something is wrong.

Once connected, Devpilot can:

• Provision virtual machines on your behalf
• Retrieve server information and connection details
• Install the Devpilot agent on the new server
• Destroy servers that were provisioned through Devpilot

Available providers: AWS, Azure, GCP, DigitalOcean, Vultr

Planned providers (coming soon): Hetzner, Linode, MTN Cloud

Notification Channels

Notification channels deliver alerts about deployment and script events. They are configured per-workspace and can be attached to specific apps or deployments so each team only gets the alerts it cares about.

Available channels: Slack webhooks, Discord webhooks, Email, and generic HTTP Webhooks — see Notifications.

Managing Integrations

All integrations live on the Integrations tab of your workspace settings.

Adding an Integration

Navigate to Workspace Settings > Integrations and choose the service you want to connect. Source control providers send you through an OAuth consent flow; cloud providers open a credential form.

Viewing Connected Integrations

The Integrations page lists every active connection with its status, the date it was added, and the linked account, organisation, or project.

Testing Credentials

For any cloud provider integration you can open the integration and select Test Credentials. Devpilot runs the same validation call used when the integration was first saved, and reports success or the exact error returned by the provider.

Removing an Integration

Open the integration and select Remove. Stored credentials and tokens are deleted from the workspace. Existing servers or deployments that rely on the integration are not deleted but future actions that need it will fail until you reconnect.

Credential Security

• Encryption at rest for all tokens, access keys, and secrets
• Encryption in transit using TLS for every external call
• Workspace isolation — credentials never cross workspace boundaries
• Minimum scopes — OAuth requests only the scopes documented on each provider page
• No credential logging — secrets are never written to logs or displayed again after entry

Next Steps