Integrations
Feedback on the page, work in your tools
StiqNote is where feedback is left: on the page, at the exact spot. Your tracker is where the work gets done. The integrations connect the two, so nobody copies screenshots into tickets by hand.
All integrations are on Pro and Agency. An owner or member connects them in Settings → Integrations.
Issue trackers
Send a thread as an issue or task. It carries the comment, the screenshot, a link back to the pin, the replay and the logs.
| What a thread becomes | Status sync | Comment sync | |
|---|---|---|---|
| GitHub | An issue in a repository | Both ways | Both ways, private repositories only |
| Linear | An issue in a team, in Triage if the team uses it | Both ways | Both ways |
| Jira | An issue in a project, of the issue type you pick | Both ways | Both ways |
| Asana | A task in a project and section | Both ways | Both ways |
| ClickUp | A task in a list | Both ways | Both ways |
| Trello | A card in a board's list | Both ways: a Done list, or archiving | Both ways |
| Notion | A page in a database | Both ways, through its status property | Both ways |
For each tracker you can:
- Ask each time, and send threads by hand with Send to…, or send every new comment on its own, optionally only some comment types or priorities. Private comments are never sent.
- Pick a destination for each project. To send a site somewhere else, give it its own project.
- Link to an existing issue instead of making a new one.
- Match people by email, so the thread's assignee becomes the issue's assignee (in Trello you match them by hand).
- Add a StiqNote label or tag (GitHub, Linear, Jira, ClickUp, Trello and Notion) so you can filter for everything that came from feedback. In Jira, fill fields such as a Sprint or Component on every issue.
How comment sync works
- StiqNote replies → the tool: on by default. Replies go to the issue as "Jane Smith via StiqNote". Private replies never go.
- The tool's comments → StiqNote: they come back to the thread as private notes, so your team sees them and clients don't. You can show them to everyone in the thread instead, send only your replies, or turn comment sync off.
Chat
- Slack: new feedback goes to a channel you pick, with replies and status changes in the message's thread. Resolve and Assign right from Slack.
- Microsoft Teams: new feedback, replies and status changes go to a Teams channel as cards, through a Workflows webhook. Each project can have its own channel.
Everything else
- Webhooks: signed events for new comments, replies and status changes, sent to your own endpoints.
- MCP server: let Claude, Cursor and other AI tools read and answer feedback.
- The API and CLI: see feedback for AI agents.
What guests see
Nothing of this. Guests never see linked issues or where a thread was sent.
Questions
What happens if we disconnect a tool?
Threads keep their links, and nothing is deleted on either side. Reconnect the same workspace and its settings come back.
Can we connect more than one tool?
Yes. Connect as many as you like. Each thread can be linked to issues in several tools.
Is there a Zapier, Make or n8n integration?
Not as an app yet. For now, webhooks send events to Zapier, Make, n8n or any service that accepts them.
Which plan do we need?
Pro or Agency. The Free plan has no integrations.
Stop sending screenshots in Slack
Pin the feedback where it belongs. Free to start, with 14 days of Agency for your first team.