IT Glue Extended
Search and manage IT Glue documentation: organizations, configurations, contacts, passwords (create/rotate — values never returned to AI), documents, flexible assets, SSL certificates, tickets, and more. Use for IT asset lookup, MSP documentation, password rotation, and config inventory.
Actions153
- Attachment Actions
- Checklist Actions
- Checklist Template Actions
- Configuration Actions
- Configuration Interface Actions
- Configuration Status Actions
- Configuration Type Actions
- Contact Actions
- Contact Type Actions
- Country Actions
- Document Actions
- Domain Actions
- Expiration Actions
- Export Actions
- Flexible Asset Actions
- Flexible Asset Field Actions
- Flexible Asset Type Actions
- Group Actions
- Location Actions
- Log Actions
- Manufacturer Actions
- Model Actions
- Operating System Actions
- Organization Actions
- Organization Status Actions
- Organization Type Actions
- Password Actions
- Password Category Actions
- Platform Actions
- Region Actions
- Related Item Actions
- SSL Certificate Actions
- Ticket Actions
- User Actions
- User Metric Actions
Document → Publish
AI-generatedSummary
Publishes an IT Glue document by ID by sending a PATCH that sets its published attribute to true, and returns the updated document.
Inputs
- Document ID (required) — ID of the IT Glue document to publish. The node throws an error if it is empty.
- Document Resource (required) — Must be left as
Document(the default). ChoosingSectionorImagemakes the operation fail with the error "publish is only valid for documentResource 'document'".
Output shape
A single item containing the updated document. Attributes are flattened to camelCase keys and sit alongside id, type, and relationships when IT Glue returns them.
If IT Glue returns no data, the node throws an error. API errors (401, 403, 429 and others) are raised as node errors, and 429 responses are retried up to 3 times. With Continue On Fail enabled, a failed item outputs
{error: message}instead.
Examples
Example 1: Publish a draft document after a workflow creates it
Resource: Document, Operation: Publish, Document Resource: Document, Document ID: {{$json.id}} (from the preceding Create node)