Azelpi / Agent Hub
Integrations
Agent Hub keeps provider connections workspace-scoped, read-model based, and explicit about what can be written back to an external service.
Vercel
Connect Vercel from Agent Hub’s Integrations screen. Vercel handles the personal-account or team choice and the project selection. Agent Hub synchronizes only the projects granted by that installation.
- Read access covers the current user, projects, deployments, and the integration configuration required to identify the installation.
- Deployment and project webhooks are accepted by the API, deduplicated, and processed by the integration worker; periodic reconciliation repairs missed or out-of-order events.
- Agent Hub currently uses Vercel for project, deployment, production-health, and aggregate analytics context. It does not deploy, redeploy, cancel, or roll back Vercel projects.
- Disconnecting the integration stops the workspace connection and removes it from future workspace reads.
Google Calendar and Gmail
Google capabilities are independent. You can connect Calendar, Gmail, both, or neither.
- Calendar: read upcoming events and prepare calendar events that are created only after you approve the action.
- Gmail: search message metadata such as subject, sender, date, and snippet, and prepare drafts. Agent Hub does not send email on your behalf.
- Disconnect each capability independently from Integrations. Google credentials remain server-side and are never returned to the browser.
GitHub
Agent Hub supports a managed GitHub App for granular repository selection and an optional GitHub OAuth compatibility path. Both flows are workspace-scoped.
- The GitHub App is the preferred path when you want GitHub-enforced repository selection and read-only metadata, contents, pull requests, and actions access.
- GitHub OAuth uses a broader provider grant, but Agent Hub still enforces the workspace repository allowlist inside the product.
- Creating a GitHub issue is an approval-gated action. Agent Hub does not silently write to repositories during synchronization.
Connection lifecycle
Provider health is reported as connected, syncing, healthy, stale, reconnect required, or disconnected. If access expires or a provider rejects a request, Agent Hub preserves a recovery state instead of pretending the cached data is current.