Skip to main content
Integrations give Interfere the context around your code and a way to reach your team. You connect and manage them from Settings → Integrations. They fall into three groups:
  • Sources are where your code lives, so Interfere can tie a problem to the change that caused it.
  • Destinations are where your code runs, so Interfere can line a problem up with the release that shipped it.
  • Communications are how Interfere reaches your team and takes direction back.
Deploying somewhere without a native integration, like AWS, Fly, Render, or your own servers? Use the CLI to report releases and upload source maps from your pipeline.
Interfere requests the least access each integration needs, and read-only wherever possible. Each page lists the exact permissions and why.
https://mintlify.s3.us-west-1.amazonaws.com/interfere/icons/tech/github/currentcolor.svg

GitHub

Connect your repositories so Interfere can tie problems to the code that caused them.
https://mintlify.s3.us-west-1.amazonaws.com/interfere/icons/tech/vercel/currentcolor.svg

Vercel

Watch your Vercel deployments so each release lines up with the deploy that shipped it.
https://mintlify.s3.us-west-1.amazonaws.com/interfere/icons/tech/cloudflare-workers/transparent.svg

Cloudflare Workers

Track Worker deployments and their versions.
https://mintlify.s3.us-west-1.amazonaws.com/interfere/icons/tech/slack/transparent.svg

Slack

Route notifications, receive direct messages, and direct the agent from Slack.

CLI

Upload source maps and confirm releases from CI with the Interfere CLI.