The request came by email,the ticket, and the reply, take one shortcut
Stakeholders, clients, and other departments don't file Jira tickets. They email you. Khint pulls the Gmail thread in, distills the actual ask with one AI action, files the issue in Jira, and drafts the “done, here's the ticket” reply, so the loop closes in the requester's inbox, not just in your backlog.
Email is where requests arrive
from people who will never open Jira
Inside the team, work starts in the tracker. Outside it, work starts in your inbox: a client reports a problem, legal needs a change, a country manager forwards a chain with “can we do this?” at the top. Turning that into a ticket means re-reading the whole exchange, untangling the actual requirement from the courtesy, filing it, and then writing a reply anyway, because unlike a chat thread, an email demands an answer. Khint handles the round-trip from one palette shortcut, with Agents doing the distilling, Memory carrying the context, and its Gmail and Jira integrations doing the reading and the filing.
Inbox to backlog and back, in five moves
The whole round-trip runs from Cmd+Shift+K.
Pull the thread in: replies, forwards, and all
Open the palette with Cmd+Shift+K and run Pull thread in the GMAIL section, or Search first if the request is somewhere three weeks deep. Khint reads the conversation into your workspace, and with a Memory session active it is logged as session context, so every later step sees the whole exchange instead of one quoted fragment.
Extract the actual ask from the politeness
Requests that arrive by email are rarely written like requirements: the real ask hides between greetings, hedges, and “when you get a chance”. Run a reusable Action over the thread to distill what is being requested, for whom, and by when, in the shape your team files tickets, acceptance criteria included.
File the Jira issue without opening a browser tab
With Atlassian connected on the Integrations page, run Create issuefrom the palette's JIRA section. The Create flow formats the content through your saved Action before filing, so the issue lands with a real title and description, one issue per run, exactly what you reviewed.
Answer the requester with the ticket link
This is the half that email demands and chat tools never do: the person who wrote to you is waiting for a reply. Run Create draftand Khint writes your response into Gmail's Drafts. You add the ticket reference, adjust the tone, and send it from Gmail yourself. Prefer to send directly? The Send emailrow shows a full preview and only fires after you type “yes”.
Chain it once the rhythm is routine
A Workflow strings up to five steps: your ticket-writing Action, a Jira Create issue step, then a Gmail Create draft step. The new issue key flows from the Jira step into the draft, so the reply starts life with the reference already in it, and because Workflow email steps only ever draft, the send still waits for you.
Why not just forward the email into Jira?
A forwarded email makes a filed record, not a workable ticket: the subject line becomes the summary, the entire chain (signatures, disclaimers, quoted history) becomes the description, and a developer still has to excavate the requirement before anything moves. And the requester still hears nothing. The version Khint files has been shaped by an Action into a title and acceptance criteria, and the reply draft carries the ticket reference back to the person who asked. When the request lands in chat instead of your inbox, the same round-trip works from a Slack thread, and for the opposite direction, sending polished updates out, stakeholder emails drafted in Gmail picks up where this flow ends.
Common questions
How does Khint read my email?
Connect Gmail once from Khint's Integrations page. It uses Google sign-in (OAuth), not a pasted password, and the token is stored in your operating system's keychain rather than on Khint's servers. The palette then gains a GMAIL section with Pull thread, Search, Create draft, and Send email rows, and each row is individually hideable from the Gmail card so you show only the ones you use. Reads happen when you trigger them. Khint never scans your inbox in the background.
Can Khint send an email without me noticing?
No. The Create draft row only writes into your Gmail Drafts. You open the draft, finish it, and hit send yourself in Gmail. The Send email row is deliberately guarded: it collects the recipient and subject, shows you a preview of the full message, and sends only after you type "yes" to confirm. In Workflows, the Gmail step can only create drafts, never send, so an automated chain can prepare your reply but the send always stays a human act.
Does the ticket just contain the whole email chain pasted in?
Only if that is what you ask for. Jira's Create issue flow runs the content through a reusable Action first, so a meandering thread (greetings, signatures, three rounds of "just following up") comes out as a clear title, a structured description, and acceptance criteria. With a Memory session active, the pulled thread is already in the session's compacted context, so the Action writes the ticket knowing what was actually discussed, not just the last message.
What do I need on the Jira side?
Connect Atlassian from the same Integrations page with your account email, an API token, and your cloud domain. All three stay in your OS keychain, local to your machine. The palette then shows a JIRA section with Create issue among its rows. Each run files exactly one issue, so what lands in your project is always something you triggered and reviewed, nothing is created silently.
Close the loop where the request started
Free with 10 AI actions and 5 captures per day. No credit card. Gmail connects with Google sign-in; every send stays a step you confirm.