Platform

Work integrations

Standups are self-reported, so InRoots cross-checks them against the systems where work actually lands and lets the assistant act on your infrastructure with your own credentials.

Jira

  • Connected per tenant through Atlassian OAuth; tokens are encrypted at rest and refreshed automatically every 50 minutes.
  • An admin picks the project and maps Jira statuses to InRoots task states so ticket movement and standup tasks line up.
  • A person’s assigned issues are shown alongside their status; the connection can be removed by the person or the admin at any time.
  • Available on the Pro plan and above.

GitLab and GitHub activity

Off by default. With a token for either or both, InRoots resolves each person’s username, counts commits and merge requests over a look-back window, and adds a line such as 6 commits, 2 MRs to the daily digest beside their standup. A per-person activity endpoint gives managers the same figures and returns a clean not-configured state rather than zeros when no token is set.

  • Activity is a cross-check on the narrative, not a score input; the Progress pillar is built from the standup text.
  • The GitLab base URL is validated so only a safe host is ever called; tokens are encrypted.
gitdev.enabled
gitdev.gitlab_base_url
gitdev.lookback_days

Cloud accounts in chat

A person can store credentials for a supported cloud platform in an encrypted per-user vault and then work from a direct message: list servers, show details, power state, IPs, DNS, firewall and snapshots. The conversation stays open after a command for follow-ups. Commands check the caller’s role on every invocation; the open conversation never elevates permissions.

  • An optional weekly advisor sends opt-in tips from a snapshot of the account.
  • When someone reports an error in a general room, the bot can probe the platform and escalate with what it found.
  • Persona replies to cloud questions are enriched with the asker’s own infrastructure context.
vpsie list
vpsie info web-01
vpsie status web-01
vpsie snapshots

n8n and automation

  • As a provider: point the AI at your own n8n workflow exposing an OpenAI-compatible chat-completions webhook and route every model call through your pipeline.
  • As a target: outbound webhooks deliver signed events to any HTTP endpoint, which is how observability and workflow tools receive InRoots events.