Connected work systems

The idea

Native connectors and signed webhooks link GitHub, GitLab, Jira, Linear, Slack, Teams, Notion and Confluence for both worker actions and the Timeline.

The problem
Workers and the Timeline need governed access to the team's real systems.
Why it matters
Actions and activity flow through one gateway with signature checks and de-duplication.
Where it stands
Partly built as of GitHub works end to end; real Jira and Slack delivery is not proven yet.

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

Where it lives in the product

  • Timeline: automatic cross-system activity feed

    An automatic feed of what one identity or Everyone did across GitHub, Jira, Slack and other connected systems; an identity can be a person, an outside agent, an AI worker or an automation.

  • Slack and Teams as work channels

    Slack and Teams carry approvals and format posts, and the new client adds native request, review, Start and result flows with one-use personal-chat linking.

  • One governed tool gateway

    Every action goes through one gateway. It checks authorization, policy, risk, budget and approval, writes the action ledger first, and reads back each external write. A model answer can only add a requirement.

  • Redaction on write and the credential vault

    Secret-shaped values are removed before events, steps, tool results and model context are stored, and customer credentials are sealed with AES-256-GCM bound to org and credential.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.