orbotodocs
Integrations

n8n operation reference

Every resource, operation, and field the orboto n8n node and trigger support.

This page is the complete field-by-field reference for the n8n-nodes-orboto package: every operation on the orboto action node, grouped by resource, and every event the orboto Trigger node can fire on. For installation, credentials, error-handling semantics (422/409/423/429), and a worked walkthrough, see n8n first - this page assumes you've already connected a credential and just need to know what a specific operation expects.

A few conventions that apply across every resource below:

  • "Project" fields are dropdowns that load your orboto projects live - you rarely need to type a key or ID by hand.
  • "Ticket" fields accept a ticket key (ACME-42), a bare number (42, resolved against the Project field), or a UUID - whichever is most convenient in your workflow.
  • Fields marked (loaded live) are dropdowns populated from your connected orboto instance (statuses, members, labels, milestones, versions, doc spaces) rather than typed by hand.
  • A field left blank on Update-style operations is left untouched on the ticket/milestone/doc - see n8n for the general error-handling and rate-limit notes that apply to every operation.

Ticket

OperationRequired fieldsOptional fieldsNotes
CreateProject, TitleDescription, Type, Priority, Status (loaded live), Milestone (loaded live), Version (loaded live), Label Names (loaded live, multi), Assignee Emails (comma-separated), Parent Ticket, Start Date, Due Date, Estimated Time (minutes), Private, Delivery Mode, Skip Auto-Translate, Allow Language Mismatch, Allow Duplicate + Duplicate JustificationType: epic/story/task/bug. Priority: blocker/high/normal/low/trivial. Delivery Mode: implementation/docs/review/admin/epic. Duplicate Justification is required when Allow Duplicate is on.
GetProject, Ticket-
Get ManyProjectReturn All / Limit, Status Category, Assignee (loaded live), Milestone Filter (loaded live), Parent Ticket Filter, Search, Include Closed MilestonesStatus Category: todo/in_progress/in_review/done/wont_fix.
UpdateProject, TicketUpdate Fields collection: Description, Type, Priority, Status, Milestone, Version, Start Date, Due Date, Estimated Time, Private, Delivery Mode, Skip Auto-Translate, Label Names, Assignee Emails, Parent Ticket; Allow Language MismatchOnly fields explicitly added to the Update Fields collection are changed - everything else on the ticket is left alone.
DeleteProject, Ticket-Permanent unless the ticket is under legal hold (423). Prefer moving to wont_fix over deleting when in doubt.
Move (Change Status)Project, Ticket, Status (loaded live)-
Assign / UnassignProject, Ticket, User (loaded live)-
CommentProject, Ticket, CommentInternalComment body is Markdown. Internal comments aren't visible to customers.
Log TimeProject, Ticket, Duration (minutes)Time Description, Logged AtLogged At defaults to now.
Add Label / Remove LabelProject, Ticket, Label (loaded live)-
OQL QueryQuery, SyntaxReturn All / LimitSyntax: oql or jql. No Project field - the query itself scopes the results. Paginates automatically via cursor until Limit (or all results, with Return All) is reached.
Set MilestoneProject, Ticket, Milestone (loaded live)-
Clear MilestoneProject, Ticket-
Set VersionProject, Ticket, Version (loaded live)-
Clear VersionProject, Ticket-
Add Dependency / Remove DependencyProject, Ticket, Depends On Ticket-
Get DependenciesProject, Ticket-
Checklists: Add ItemProject, Ticket, Checklist ID, Item Text-
Checklists: Check Item / Uncheck ItemProject, Ticket, Item ID-
Get AttachmentsProject, Ticket-
Add AttachmentProject, Ticket, Binary Property-Binary Property names the input item's binary field holding the file (default data).
Bulk UpdateProject, Ticket IDs (comma-separated), ActionValue, shaped per ActionAction: status / milestone / assignee / version / priority / due_date, each with its own live-loaded or plain Value field. Prefer this over looping per-ticket updates for large batches.

Milestone

OperationRequired fieldsOptional fields
CreateProject, NameMilestone Key, Start Date, End Date, Budget Amount, Budget Hours, Private
GetProject, Milestone (key or ID)-
Get ManyProjectInclude Closed
UpdateProject, MilestoneMilestone Key, Start Date, End Date, Status (active/completed/archived), Budget Amount, Budget Hours, Private
CloseProject, Milestone-

Close is a convenience wrapper around Update with Status set to completed.

Project

OperationRequired fieldsOptional fields
CreateNameKey, Description, Language
GetProject (key or ID)-
Get Many--
UpdateProjectName, Key, Description, Language, Status (draft/active/archived/closed)
Get Primer FactsProject-
Get AI PrimerProject-

Key must be 2-10 uppercase characters (letters and digits). Language is the ticket language enforced for that project - see n8n for how the node surfaces a language mismatch.

Doc

OperationRequired fieldsOptional fieldsNotes
CreateSpace (loaded live), TitleContent, VisibilityVisibility: public/workspace/members/specific, default workspace.
GetDoc (key or ID)-
Get ManySpace-
UpdateDocTitle, Content, VisibilityOnly the fields set are changed.
Ask Docs (RAG)QuestionLimit ResultsRequires an embedding provider configured on the instance - a clear error explains this if none is set up.
Ingest URLSpace, URLRaw HTMLPass Raw HTML to ingest pre-fetched content instead of letting orboto fetch the URL itself.

Time Entry

OperationRequired fieldsOptional fields
LogProject, Ticket, Duration (minutes)Description, Logged At
Get ManyProject, Ticket-
EditProject, Ticket, Entry ID, Duration (minutes)Description
DeleteProject, Ticket, Entry ID-

All time-entry operations are ticket-scoped.

User

OperationRequired fields
Get Project MembersProject

There's no global user directory operation - member reads are always scoped to one project, matching the fact that orboto has no workspace-wide "all users" list a non-admin can read.

Label

OperationRequired fieldsOptional fields
CreateProject, NameColor
Get ManyProject-
OperationRequired fieldsOptional fieldsNotes
CreateName, Query TypeOQL Query (when Query Type is oql or jql)Query Type: oql/jql/legacy.
Get Many--
RunSaved Search (name or ID)-Only OQL/JQL saved searches can be run from n8n - a legacy-type saved search fails with a clear error, since legacy queries have no OQL/JQL text to execute.

Agent

The n8n-to-agent bridge - lets a workflow talk to an agent identity's inbox the same way one agent notifies another.

OperationRequired fieldsOptional fieldsNotes
NotifyTarget Email, SubjectKind, Payload (JSON), Thread ID, Project Scope, Sender ReferenceKind: info (FYI), request (expects an answer), complete (closes a request), error (reports failure). Project Scope routes the message to the right session.
Get Messages-Include Already-Delivered, Limit, Exclude Reference, Project ScopeBy default returns only messages not yet delivered to this reader.
Ack MessagesMessage IDs (comma-separated)-Marks messages as delivered so a later Get Messages call doesn't return them again.

orboto Trigger: events

The trigger's Events field lists these 16 events; check any combination. An Additional Events free-text field (comma-separated) lets you subscribe to event types added to orboto after this package version shipped, before the node has a dedicated checkbox for them.

EventFires when
ticket.createdA ticket is created.
ticket.updatedA ticket's fields change.
ticket.deletedA ticket is deleted.
ticket.readyA ticket becomes unblocked (its dependencies are resolved).
ticket.checklist_item.completedA checklist item on a ticket is checked.
comment.createdA comment is posted.
comment.updatedA comment is edited.
comment.deletedA comment is deleted.
project.member_addedA member joins a project.
project.member_removedA member leaves a project.
milestone.createdA milestone is created.
milestone.updatedA milestone's fields change.
version.releasedA version is marked released.
symphony.candidates_changedA ticket's status, assignee, or priority changes, in a shape relevant to a Symphony coding-agent orchestrator polling for work.
inbound.signal.receivedAn inbound signal (e.g. from inbound email processing) is received.
agent.escalation_raisedAn AI agent raises an escalation that needs human attention.

Every delivery is scoped to the Project you selected on the trigger node - webhooks in orboto are project-scoped, so one trigger node watches one project. Add a second orboto Trigger node for a second project.

On this page