ISSUE TRACKER
Website feedback, straight into GitHub issues
Connect a repository once and every new thread becomes an issue — the author, the comment, and a link back to the exact page, in the repo where the fix will actually happen.
Available on Pro and above.
HOW IT WORKS
What happens when feedback arrives
Credentials are encrypted at rest, every delivery records its outcome, and a failing integration never blocks the feedback itself.
On new feedback
Annot8 opens an issue in the repository you pick, with a markdown body carrying who said it, what they said, and a link that opens the page it was pinned to.
Or on demand
On a repository where issues are your real backlog, leave the automation off and open issues only for the threads that need code.
Routed per project
Connect once for the workspace, then choose per Annot8 project whether it posts, and override the owner/repo where a project has its own repository.
GOOD TO KNOW
Before you connect GitHub
The specifics that save a support ticket — the same ones the docs lead with.
Where Agent Fixes land
The same GitHub connection is where Annot8's Agent opens draft pull requests when you ask it to fix a thread — feedback in, reviewable diff out.
Token expiry
Fine-grained tokens expire by default, and GitHub answers 404 rather than 403 for repos a token can't see — two things worth knowing before you debug.
Feedback in, GitHub notified, nothing re-typed
One script tag on the site, one connection to GitHub, and the pipeline runs itself.