Jira
Jira Cloud connects with an API token rather than OAuth — nothing to register, nothing to refresh. Flipper reads issues and, crucially, their comments.
- 1Create an API token
At id.atlassian.com/manage-profile/security/api-tokens, choose Create API token, name it Flipper, and copy it — Atlassian shows it once.
- 2Collect three things
Your site URL (
https://your-team.atlassian.net), the email you sign in to Atlassian with, and the token. The email is the Basic-auth username, not a secret. - 3Paste them into Flipper
Connectors → Jira → connect. Flipper validates the credentials against your site before storing anything.
What it reads
Issue summary, description and the most recent comments, along with project, status, type, assignee and labels. Descriptions and comments arrive in Atlassian Document Format and are flattened to text — including @mentions and linked cards, which is the difference between a comment that names who owns the follow-up and one that reads “raising it to 50, see”.
Comments matter more than they look. A Jira description says what the work is; the comments say why it changed, who objected, and what was decided instead — and that is what an agent is later asked about.
