link_ticket_issue

Record the Linear or Notion issue a Montra ticket was exported to.

Records where a ticket now lives downstream — the Linear issue or Notion page you just created from it — so the Montra ticket shows a link back to it.

A ticket holds one link per provider. Calling this again for the same ticket and provider re-points the existing link rather than adding a second one.

Input

ticketId · string · required

Id of the Montra ticket (UUID).

provider · string · required

External system the ticket was exported to: linear or notion.

identifier · string · required

Provider-facing id of the issue or page, such as a Linear identifier like MON-123. Trimmed; 1–64 characters.

url · string · required

Deep link to the external issue or page. Must be an https URL.

Output

link · object · required

Show properties

id · string · required

Id of the recorded link.

ticketId · string · required

Id of the Montra ticket the link belongs to.

documentId · string · required

Id of the document that ticket belongs to.

provider · string · required

linear or notion.

identifier · string · required

Provider-facing id of the issue or page.

url · string · required

Deep link to the external issue or page.

Notes

• When you create the external issue, link it back to Montra using that ticket’s own durable humanShareUrl from the share link payload — not the shareUrl the payload was fetched with, which can be a legacy expiring link.
• Tickets outside the workspace this connection is bound to read as not found. See workspace binding.
• Related: set_ticket_status, get_ticket, and the agent workflow guide.