INTEGRATIONS
Integrations
Send comments to Linear, GitHub, GitLab, Asana, Notion, ClickUp and Jira, and post feedback to Slack or any webhook.
Integrations live in your workspace Settings under Integrations. Workspace owners and admins see this page.
Issue trackers
Connect a tracker once, then send any comment to it as a ticket.
Connect a tracker
- Open Settings, then Integrations.
- Click Connect on the tracker's card.
- Sign in to the tracker and approve access. You never paste an API token.
Trackers need the Solo plan or higher. On the Free plan the card shows Upgrade to unlock.
After connecting, tickets go to a default destination: the first Linear team, GitHub repository, GitLab project, Jira project or Asana workspace your account can see. For Linear and GitHub, change it in Where tickets go, and use Send this canvas somewhere else to override it for one canvas. For Notion, choose the Database for new tasks. For ClickUp, choose the List for new tasks.
Send a comment
Open a comment and choose Send to tracker. The ticket includes:
- The comment text and a title
- The page address and the CSS selector of the element
- Browser, operating system, viewport size and device
- Console errors and failed network requests, when they were captured
- The comment's screenshot
- A link back to the canvas
Viewers cannot send comments to a tracker.
Linear and GitHub also support labels, assignees, a project or milestone, GitHub issue templates, sending a batch of comments at once and adding a comment to an existing ticket.
Status sync
Status moves in both directions between Notemark and Linear, Jira, GitHub and GitLab.
From Notemark to the tracker
When you resolve, reopen or change the status of a comment, its linked ticket follows. This also happens when a coding agent changes the status through the MCP server.
| Comment status | Linear | Jira | GitHub and GitLab |
|---|---|---|---|
| Open | Backlog or unstarted | A To Do status | Open |
| In progress | A started state | An In Progress status | Open |
| Resolved | A completed state | A Done status | Closed |
For Jira, Notemark uses the first workflow transition that leads to that status category. If the workflow has none, the ticket stays where it is.
When several comments are linked to one ticket, the ticket follows the least finished of them. It closes only when every linked comment is resolved.
If the tracker cannot be reached, Notemark retries right away and again during the daily sync. Asana, Notion and ClickUp tickets are not updated from Notemark.
From the tracker to Notemark
| Tracker | Status in Notemark |
|---|---|
| Linear | Updates when the ticket changes, by webhook |
| GitHub | Updates when the issue changes, by webhook |
| Jira, Asana | Checked once a day |
| GitLab, Notion, ClickUp | Not synced |
When a ticket is marked done in the tracker, the comment stays open and is flagged Needs verify, so someone checks the fix before resolving it. For GitHub, the account that connects needs admin rights on the repository so Notemark can register the webhook.
Reopening a resolved comment adds a note to its linked Linear or GitHub ticket.
Jira
- Connect Jira from the Integrations page and approve access to your Jira site.
- Notemark picks the first project your account can see. To change it, choose another one in Project for new tickets on the Jira card.
- Send comments to Jira like any other tracker.
The project list is read when you connect. If you create a Jira project later, disconnect and connect Jira again to see it. If no project is set when you send, Notemark asks you to pick where new tickets go and links to the integration settings.
Slack
Slack connects through an incoming webhook and needs the Solo plan or higher.
- In Slack, create an incoming webhook for the channel you want and copy its
https://hooks.slack.com/services/...address. - In Integrations, go to Webhooks and click Create Webhook.
- Set Send to to Slack and paste the address.
By default Slack gets a message when a comment is created and when one is resolved. Each message shows a short preview and a link to the canvas.
Webhooks
Webhooks need the Team plan or higher. They send events to any address you choose, including Zapier, Make and n8n. Point a webhook at a Zapier Catch Hook address; no separate app is needed.
Available events:
comment.created,comment.updated,comment.resolved,comment.deletedcanvas.created,canvas.updated,canvas.deleted
Requests to your endpoint are signed with HMAC-SHA256 in the X-Webhook-Signature header and time out after 10 seconds. Failed deliveries are not retried automatically: open View delivery logs and click Retry.
After a plan change
If your workspace moves to a plan that does not include Slack or webhooks, the ones you already set up keep sending. You can still view delivery logs, pause and delete them. Creating new ones, editing, turning a paused one back on and sending a test need the plan again.
Coding agents
To let Claude Code, Cursor and other agents read and resolve comments, see MCP server.