Skip to main content
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. Whenever the person asks you to create an external issue from a ticket, call this as part of that export — it does not need a separate ask. Do not call it for issues you did not create, and it is not a way to mark a ticket done. 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

​
string
required
Id of the Montra ticket (UUID).
​
string
required
External system the ticket was exported to: linear or notion.
​
string
required
Provider-facing id of the issue or page, such as a Linear identifier like MON-123. Trimmed; 1–64 characters.
​
string
required
Deep link to the external issue or page. Must be an https URL.

​
Output

​
object
required

​
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: get_ticket, update_ticket, and the agent workflow guide.