Connected to the tools you already use.
Discuss work where the team already talks, turn incoming mail into tasks, push events to your own systems, and automate the rest with scoped API tokens.
- Microsoft Teams
- Signed webhooks
- Email-to-task
- Public API
Krrim where the conversation already is
Channel notifications and actions
Updates for the projects you choose, with assign, comment and status change available from the message itself.
Link unfurling that respects permissions
A Krrim link expands into the task’s title, status and assignee — for people who can see it. Anyone else gets the bare link. Unfurling is not a way around project membership.
Both directions
Signed webhooks
Every delivery is signed over its timestamp and raw body, so a captured request cannot be replayed against you forever.
Learn moreA retry curve you can plan around
1m, 5m, 30m, 2h, 6h — six attempts, published and fixed, because integrators size their outage tolerance against it.
Email-to-task
Give a project an intake address and mail becomes tasks. For support queues and stakeholders who will never open Krrim.
Scoped API tokens
A token authenticates a service account with a role you pick, restricted to the scopes — and optionally the projects and IPs — you choose.
Learn moreA kill-switch that is not revocation
Disconnecting the Public API integration stops every token at once without destroying any of them. The right tool for "turn it off while we investigate".
A changes feed that reports deletions
The one thing a task list cannot tell you. Incremental sync that does not accumulate ghosts.
Learn moreQuestions people ask
- Webhooks or the API?
- Both, usually. A webhook tells you the moment something happens and costs no rate limit; the API answers questions on your schedule. Solid integrations use webhooks for latency and a periodic changes-feed pass as the backstop.
- Does an API token inherit its creator’s permissions?
- No — that is the point. It authenticates a service account with its own role, so offboarding a person never breaks a production integration and audit rows name the bot.
- Are attachments imported from email?
- Not yet. The subject becomes the title and the body becomes the description; attachments are on the list.
- Is Slack supported?
- Not today. Microsoft Teams is the chat integration that ships; anything else can be built on webhooks and the public API in the meantime.
Wire Krrim into the rest of your stack
Teams and email-to-task are a few clicks. The API and webhooks are documented properly.
Free to start · No credit card required