Connector Roles
The roles and capabilities of connectors in acteedog
Each connector is responsible for fetching data from a specific source and converting it into a format that can be used by the acteedog core application.
Some connectors only support a subset of features. See the list table below for details on feature support.
Activity Collection and Context Association
Using information such as API keys configured by the user, each connector periodically collects activity data from external services. The collected activities are then associated with related context information.
For example, the GitHub connector collects activities such as commits and pull requests from the user's repositories via the GitHub API, and associates them with related context information such as pull requests and issues.
Cross-Connector Context Detection
When a Slack message contains a GitHub pull request URL, for example, the system detects related context across connectors and associates it with the activity. This allows users to provide deeper context to the LLM when generating daily reports.
In addition to activity → context associations, acteedog also supports context → context associations, such as when a pull request contains an issue URL.
Context detection runs within the acteedog core application. For example, the GitHub connector defines detection patterns for pull request URLs, issue URLs, repository URLs, and more using regular expressions. If the user has the GitHub connector enabled, GitHub URLs found in messages from other sources such as Slack will also be detected and associated as related context.
Context Enrichment
For performance reasons, context information contains only the minimum necessary data at the time of activity collection and context detection. For example, when collecting activities, the GitHub connector only associates basic information such as the pull request ID and title as context.
Connectors that support context enrichment supplement the context information in a separate asynchronous process from activity collection. For example, the GitHub connector retrieves detailed information about the pull request (e.g., number of changed files, reviewers, etc.) via the API and updates the context.