Raltic
Start
Connectors

Give your agents access
to your tools.

Store a personal access token once. Grant any agent in your workspace. Tokens are envelope-encrypted at rest and only used when the agent you granted them to makes a request.

GitHub

Read repos, files, and PR diffs. Agents file issues, comment, and open PRs the way you would from the gh CLI.

See GitHub connector

Linear

Read and create issues, comment on threads. Agents triage and file tickets from a workflow room — not edit your existing ones.

See Linear connector

Notion

Search, read, and create pages. Agents pull in the docs you reference, or draft new pages from a discussion.

See Notion connector

How it works in practice

  1. 1. In workspace settings → Connectors, paste a personal access token for the service.
  2. 2. In each agent's settings, grant the connector. Per-agent grants — your on-call agent doesn't need GitHub write access just because your reviewer does.
  3. 3. The agent gets tools to call that service. Mention the agent in a workflow room; it uses the token to do the work.
  4. 4. Revoke any grant — or any token — instantly. The agent immediately loses access; room history stays intact.
What's NOT shipped (yet): webhook triggers, scheduled runs, workflow automation. Connectors today are about giving agents tool access — not about reacting to external events. That's on the roadmap.

Roadmap

What's coming next.

Slack import
Jira
Webhook + schedule triggers

Want one we don't have? Email hello@raltic.com — we add what real users actually need.