Source Integrations

A majority of minware's insights depend on data from both version control and ticket tracking, though some will work with only one or the other. As such, we highly recommend setting up at least one version control system and at least one ticketing system for ingest into minware. Connecting a calendar system is optional and provides greater insight into time spent in meetings, but most of the reports work without it.

Supported Systems

minware currently supports integrations with the following systems. However, we can add new integrations for additional systems not on the list. Please contact support@minware.com if you are interested in an integration not listed here.

Version Control

• GitHub
• GitLab
• Bitbucket
• Azure DevOps

CI/CD Data

• GitHub
• GitLab

Ticketing

• Jira
• GitHub Issues

Calendar

• Google Calendar

AI Usage

• GitHub Copilot
• Claude
• Cursor

AI Agent Telemetry

• Claude Code

Custom Upload

• Custom CSV/JSON

Updating an Integration Token

Organization admins can replace personal access tokens or API tokens at any time.

To update a token:

1. Visit Settings > Integrations in minware.
2. Find the integration and click "Update Token".
3. Generate a new token in the source system with the same permissions as the original (see the setup instructions for your source above), then paste it into the form.
4. Jira integrations also ask for the login email associated with the token. Leave it blank to keep the current value.

minware validates the new token before saving it, and the new token must have access to the same organization as the current one. If validation fails, the current token remains in place and data ingestion continues unchanged.

Some sources create multiple minware integrations from a single token. For example, one Azure DevOps personal access token can back both an Azure Repos and an Azure Boards integration. Updating the token for one of them updates it for every integration that shares it, and the update form lists the affected integrations.

After the update, all future data ingestion uses the new token. An ingest job that is already running may finish with the previous token, so if you plan to revoke the old token in the source system, wait for any in-progress ingest to complete first.

Note that this only applies to token-based integrations. Integrations that use an installed application (such as the GitHub or Jira apps) or OAuth (such as Google Calendar) manage their credentials automatically and do not have an "Update Token" action.

minware On-Premise Ingest Agent

minware offers an on-premise agent for data ingestion that runs inside of your infrastructure. The on-premise agent is available with our enterprise-level plan.

Ingest Frequency

minware will ingest data nightly, typically between 2-7 AM Eastern time. This ingest process may take a few hours, depending on the size of your organization's data

Additionally, you can request that minware re-process data from your ticketing system by clicking on the "Sync Now" button available on certain reports. This ticket-only typically takes around five minutes to complete. It will only update ticket tracking data and will not ingest new version control or calendar data.