DevOps and automation connectors
These connectors are for teams that run Perceive8 agents on top of their own tooling. Each one is a single API key or token that lets agents read from — or act through — the services you already use: watching deployments, triaging incidents, triggering workflows, or sending email.
You don't need any of these for core meeting capture and analysis. Connect them when an agent or workflow calls for it — the Integration Hub and recommended agents will tell you when one is required.
DevOps / SRE
| Provider | Key to paste | What agents can do with it |
|---|---|---|
| GitHub | Personal access token | Read repositories, issues, and pull requests; open issues and PRs. |
| Sentry | Auth token | Read issues, events, and stack traces; receive alerts. |
| Railway | API token | Read projects, services, deployments, and logs. |
| Supabase | Access token | Read database stats, logs, and edge function status. |
| AWS | Access key | Read CloudWatch metrics and logs. |
| Google Cloud | Service account key | Read Cloud Monitoring metrics and logs. |
Automation
| Provider | Key to paste | What agents can do with it |
|---|---|---|
| n8n | API key | Trigger workflows and check their status. |
| Tray.io | API token | Trigger workflows and check their status. |
| Resend | API key | Send transactional email and check delivery status. |
Connect
Every connector on this page works the same way:
- Generate the key or token in the provider's dashboard (links and names are in the table above).
- Go to Audio → Settings → Integrations, find the provider's card, and click Connect.
- Paste the key and click Save.
Perceive8 verifies the key with the provider before storing it — an invalid or expired key is rejected on the spot. Once connected, the card shows the provider's capability badges so you can see at a glance what the key enables.
What happens after you connect
Recommended agents that required this tool unlock automatically: they're created, provisioned, and given their first tasks without any extra steps. If you dismissed a recommendation earlier because a tool was missing, connecting the tool is the way to get it back in motion.
Choosing and managing keys
- Least privilege. Create read-only tokens wherever the provider allows it — most connectors here only need to read. GitHub is the exception: opening issues and PRs needs write permission on the relevant repositories, so scope the token to just those repos.
- One key per workspace. Reconnecting with a new key replaces the old one.
- Rotation. To rotate a key, generate the new one at the provider, paste it into the card again, then revoke the old one at the provider.
- Storage. Keys are stored encrypted and are never displayed again after saving. See How integrations work.
Disconnecting
Click Disconnect on the provider's card. The stored key is removed and agents immediately lose access to that tool — agents that depend on it will pause or fail their related tasks until a new key is connected. Disconnecting never deletes anything the agent already created (issues, PRs, emails sent, workflow runs).
Troubleshooting
- Key rejected at save. It's verified live with the provider. Check for extra whitespace, confirm the key hasn't expired, and make sure it has the permissions listed above.
- An agent can't use a connected tool. Confirm the token's scope covers what the agent needs (for example, repository selection on a fine-grained GitHub token), then reconnect with a correctly scoped token.