Connect Monday, Slack, Jira, GitHub, or Sentry once. From then on, a new task or bug opens a conversation with Mark, the team's developer, who reads it, fixes it, ships it, and answers right where it came from.
No copying tasks over, no opening a conversation by hand. On your phone and in the browser.
All five connections are open to every account today. Each one listens for a different signal, and every one answers where the task came from.
Leave your details in the form below and pick your tool. We'll get back to you with what can be done today.
To the formAn example from a Monday board. The same thing happens with a Slack message, a GitHub or Jira issue, and a Sentry error.
"Save button does nothing in Safari" lands on the bug board
An update with the conversation's link appears on the item, and Mark finds the line and fixes it
Another update on the item: what was done, what's still open, and a link to the code change
Tasks that open on their own need clear limits. These are the limits.
Sign up for Kringl and connect a repository from GitHub, GitLab, or Bitbucket. That's the project Mark works on.
In settings, under Connections: paste a token, create a Slack app from the ready manifest, or install the GitHub App.
Which board, channel, or Sentry project belongs to which project. From then on, a new task there opens a conversation.
Connections are set up by the owners or admins of your company in Kringl. The conversations they open run under the owner.
Sign up, connect a repository and your tool, and the next task that opens is already with Mark. The first 30 days are free.
Leave your details and tell us where your tasks live, and we'll get back to you for a short talk about your board, your team, and your project.
Only on a board mapped to a project. In Jira and GitHub, only an issue with the label kringl or a comment with @kringl, unless you let every new issue in. In Slack, only a mention or a direct message. In Sentry, a new issue or one that came back, not every event.
By default Mark merges the change, like a developer on your team. Whoever runs your company in Kringl can set, per person and per project, that the change waits on the "Waiting to merge" screen until a person approves, returns, or rejects it.
No. Mark writes an update when work starts, and again with a question, when it's done, or when something failed. The status, the column, and the assignee stay in your hands.
Pricing is per seat, never per token, and the first 30 days are free. Each person can set a monthly, daily, and per conversation spending cap, so tasks that open on their own hold no surprises.
Monday, Slack, Jira, GitHub, and Sentry, connected on your own from settings. Using something else? Pick it in the form and we'll get back to you.
Exactly what the token or the app you gave allows, and only on boards and channels mapped to a project. On Monday a separate user is a good idea, because the updates appear under the token's owner.
Mark asks. The question arrives as an update or a comment in the same place, and your answer there continues the conversation.
