Integration Connector
A standalone service that lets external events like GitHub issues or Slack messages trigger Agenhood agents.
Definition
An integration connector is a standalone Agenhood service that links external platforms, currently GitHub and Slack, to the agent fleet, so that events on those platforms, for example a new GitHub issue or a Slack message, can trigger or communicate with an agent, and so an agent's output can be posted back to the originating platform.
How it works in Agenhood
Connectors run as their own service, separate from the control plane, with their own database and their own OAuth flow for authenticating with GitHub and Slack. This keeps platform-specific concerns, webhook handling, API rate limits, OAuth token storage and refresh, out of the control plane, which only needs to expose the API that connectors, and other clients, call to create tasks or communicate with agents. When a connector receives an external event it cares about, it translates that event into a call against the control plane's public API, the same API the web console uses, rather than talking to agents directly. For example, a GitHub connector might open a task on a designated agent whenever an issue is labeled a certain way, then post that agent's result back as a comment on the issue once the task completes.
Why it matters
Isolating connectors as a separate service means adding support for a new external platform, or scaling and redeploying an existing integration, does not require changes to or downtime for the control plane or the agent fleet itself. It also limits the blast radius of a platform-specific credential or webhook issue to the connector service, rather than the core system that manages agent state. For teams, this is what makes it practical to have agents respond to work as it happens on GitHub or Slack, instead of requiring someone to open the console and start a task by hand.
Related concepts
Splitting third-party integrations into their own service with independent credentials and storage, rather than embedding every external API inside a core application, is a common pattern in service-oriented architectures generally. In Agenhood, a connector is one of several ways to create or drive a task, alongside direct API calls and the web console; what makes it distinct is that the trigger originates from an external platform's event rather than from a user acting inside Agenhood.