Connect Developer tools
What the Developer tools connections surface, what the AI layer does with them, and how to set one up.
Connections in this category
- GitHub — Pull requests, issues and deployments in the channel that owns them. · Full description
- Vercel — Build and preview notifications, with the failing log attached. · Full description
- Supabase — Database migrations and edge function logs where the team can read them. · Full description
- Sentry — New issues routed to the channel that owns the service. · Full description
- PagerDuty — Incidents open a thread, and the thread becomes the timeline. · Full description
What these connections surface
- Route events to the channel that owns the service.
- Attach the failing log or diff to the message.
- Link a thread to the commit, build or incident it concerns.
What the AI layer does with them
- Ask what changed on a service this week and get an answer with sources.
- Summarise an incident thread into a timeline with owners.
- Search code and deployments from the same box as chat.
Setting one up
- Ask an owner to connect the tool — the connection is made once.
- Authorise the connection and pick which channels or spaces it feeds.
- Huub indexes the history in the background — search reaches it within minutes.
Note — Connections are unlimited from Team upwards. Starter is capped at 5.