create_ticket

Adds a new ticket to an existing document. title is the short label, summary is the one-line gist shown next to it, and body is the markdown implementation spec an agent reads before building. Tickets created through the connector carry the same “manual” source as tickets a person adds in the app — they are hand-authored work items, not output of a generation job.

Input

string

required

Id of the Montra document the ticket belongs to (UUID).

string

required

Short title for the ticket. Trimmed; 1–300 characters.

string

One-line gist of the ticket. Trimmed; up to 1000 characters.

string

Markdown implementation spec for the ticket.

Output

object

required

Show properties

string

required

Id of the newly created ticket.

string

required

Id of the document the ticket belongs to.

string

required

Short title for the ticket.

string

required

One-line gist shown next to the title. Empty string when none was given.

string

required

Markdown implementation spec. Empty string when none was given.

string

required

todo or done. New tickets start at todo.

string

required

Opaque ordering key that places the ticket within its document. Empty for tickets created here.

number

required

Offset into the source recording, in milliseconds, that the ticket points at. 0 for tickets created here, which are not tied to a recording moment.

string

required

Id of the input whose generation produced the ticket. null for tickets created here.

string

required

ISO 8601 creation timestamp.

string

required

ISO 8601 timestamp of the last change.

Notes

The document must be in the workspace this connection is bound to; anything else reads as not found. See workspace binding.
To create the document first, use create_document.
Related: update_ticket, get_ticket, and the agent workflow guide.

Get started

Guides

Tool reference

Input

Output

Notes

​Input

​Output

​Notes

Input

Output

Notes