Connect External Tools
This page explains how to connect tools such as GitHub and Jira so that EM-OS can import development data automatically. Organization admins set up integrations in Admin > Integrations. Integrations are available on the Enterprise plan and above.
TIP
Start by connecting only GitHub and confirm that development metrics (Four Keys) are calculated, then add other tools.
Supported tools
| Tool | Data imported | How EM-OS uses it |
|---|---|---|
| GitHub | Repositories, commits, pull requests, issues | Four Keys and SPACE metrics, issue lead time, review efficiency |
| Jira | Projects, tickets | Importing and syncing projects, story points, maintenance work |
| Slack | Channel activity | Communication frequency between teams, notifications |
| Google Calendar | Events | Scheduling 1on1s |
| AWS (beta) | Availability metrics for some resources | SLO (Stability) achievement |
| GCP | Monitoring metrics | SLO (Stability) achievement |
Connect GitHub
To connect GitHub, you create a GitHub App in your GitHub Organization and install it. You need admin permissions for the GitHub Organization.
- On GitHub, open New GitHub App and create a GitHub App.
- Under "Permissions", set all of the following to Read-only:
- Contents (code and commit history)
- Metadata (repository information)
- Issues (lead time and recovery time)
- Pull requests (review efficiency and deployment frequency)
- Actions (CI/CD workflows and deployment frequency)
- Install the App on your Organization and select the target repositories.
- In the App settings, generate a Private Key and note the App ID and Installation ID.
- In EM-OS, open Admin > Integrations, select "Connect Now" for GitHub, enter the App ID, Installation ID, and Private Key, and save.
- It may take a few minutes for data to appear.
After connecting, you can change the following in the GitHub "Settings":
- Excluded Users: Enter GitHub user names, separated by commas, to exclude from Four Keys calculations (for example, bots).
NOTE
If "Reconnect Required" appears, the GitHub App's permissions have changed or its token has expired. Check the App's permissions and installation, and if needed, generate a new Private Key and enter it again. If you reach GitHub's API rate limit, syncing pauses until the time shown.
Connect Jira
- Create an API token in your Atlassian account settings.
- In Admin > Integrations, select "Connect Now" for Jira and enter:
- Jira Domain (for example,
example.atlassian.net) - The email address of your Atlassian account
- The API token
- Jira Domain (for example,
- Optionally set:
- Story Point Custom Field ID (for example,
customfield_10031) - Issue Types for Maintenance: If left empty, Bug, Defect, Glitch, and Maintenance are counted as maintenance.
- Story Point Custom Field ID (for example,
- Use "Test Connection" to check the connection, then select "Save Connection".
For importing Jira projects, see Administration.
Connect Slack
- Create a Slack App and get its Bot User OAuth Token (starts with
xoxb-). - In Admin > Integrations, select "Connect Now" for Slack, enter the token, and save.
- If you do not specify channels, all public channels are analyzed. To include private channels, invite the bot to those channels and specify their channel IDs.
- In "Settings", enter the Signing Secret from the Basic Information page of your Slack App. The saved value is not shown again; the screen only shows that it is set. Enter it again only to change it (if left empty, the current value is kept).
Check or remove an integration
- Use "Test Connection" on each tool to check that the credentials and permissions are correct.
- Tools that show "Sync Now" can import data without waiting for the next scheduled sync.
- Use "Disconnect" to stop an integration.
If data does not sync, see Troubleshooting.
