Connector List
List of available connectors and how to configure them
acteedog currently provides the following connectors.
| Connector | Activity Collection | Context Enrichment | Context Detection |
|---|---|---|---|
| GitHub | ✅ | ✅ | ✅ |
| Slack | ✅ | ✅ | ⬜ |
| Jira | ✅ | ✅ | ✅ |
| Google Calendar | ✅ | ✅ | ⬜ |
GitHub
Uses the GitHub API to collect activities such as commits and pull requests from the user's repositories, and associates them with related context information such as pull requests and issues.
Due to GitHub API limitations, only the most recent 30 days of activity can be collected, up to a maximum of 300 items. See the official documentation for details.
Authentication
The following two authentication methods are supported.
Personal Access Token
| Auth Field | Required | Description |
|---|---|---|
| Personal Access Token | ✅ | A GitHub Personal Access Token. The repo, read:user scopes are required. |
GitHub App (OAuth Device Flow)
Authenticate via GitHub App using the OAuth Device Flow in the app. The Acteedog GitHub Connector App must be installed in the target organization beforehand.
Configuration
| Field | Required | Description |
|---|---|---|
| Username | ✅ | The GitHub username for which to collect activities. |
| Repository Patterns | ⬜ | Patterns for specifying the repositories from which to collect activities. Wildcards (e.g., owner/*) can be used to specify multiple repositories. If not specified, activities are collected from all repositories. |
Slack
Uses the Slack API to collect activities such as messages and thread replies in channels the user has joined, and associates them with related context information such as channels and threads.
Authentication
User OAuth Token
| Auth Field | Required | Description |
|---|---|---|
| User OAuth Token | ✅ | A User OAuth Token (e.g., xoxp-...) obtained from the Slack App OAuth & Permissions page. The channels:history, channels:read, groups:read, im:read, mpim:read, search:read scopes are required. |
Configuration
| Field | Required | Description |
|---|---|---|
| User ID | ✅ | The Slack User ID for which to collect activities (e.g., U12345678). |
| Workspace URL | ✅ | The URL of the Slack workspace from which to collect activities (e.g., your-workspace.slack.com). |
Jira
Uses the Jira API to collect activities such as issues and comments from projects the user is involved in, and associates them with related context information such as issues and projects.
Authentication
API Token (Basic Auth)
| Auth Field | Required | Description |
|---|---|---|
| ✅ | The email address of your Atlassian account. | |
| API Token | ✅ | A scoped API token for calling the Jira API. The read:jira-user, read:jira-work scopes are required. You can generate one from Atlassian Account > Security > API Tokens. |
Configuration
| Field | Required | Description |
|---|---|---|
| Cloud ID | ✅ | The Jira Cloud ID. You can find it by accessing https://your-subdomain.atlassian.net/_edge/tenant_info. |
| Project IDs | ✅ | A list of project IDs (e.g., 1002). You can find them by accessing https://subdomain.atlassian.net/rest/api/3/project/KEY. |
| Site Subdomain | ✅ | The subdomain of your Atlassian environment (e.g., your-subdomain). |
Google Calendar
Uses the Google Calendar API to collect activities such as events and meetings from the user's calendars, and associates them with related context information such as calendars and events.
Authentication
Google OAuth 2.0
Click the "Connect" button in the app to open the Google sign-in page. Simply log in with your Google account and grant calendar access to complete the setup.
Configuration
| Field | Required | Description |
|---|---|---|
| Email Address | ✅ | The Google account email address for which to collect calendar events. |