IT Glue Extended
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
Attachment → Update
AI-generatedSummary
Renames an existing IT Glue attachment by sending a PATCH to the parent resource's attachments relationship endpoint, and returns the updated attachment.
Inputs
- Attachment ID (required) — ID of the attachment to update.
- Resource Type (required) — Type of the parent resource that owns the attachment (configurations, contacts, documents, domains, locations, passwords, flexible_assets, ssl_certificates, checklists, checklist_templates, tickets). Used to build the request path.
- Resource ID (required) — ID of the parent resource. Used with Resource Type to build the path {type}/{id}/relationships/attachments/{attachmentId}.
- Name — New display name for the attachment. Declared optional in the UI, but the operation fails if it is empty because no other field can be updated.
Output shape
A single item containing the updated attachment, flattened: attribute keys converted from kebab-case to camelCase, plus id, type, and relationships if present.
Throws an error if Attachment ID, Resource Type or Resource ID is missing, if Name is empty ("Provide at least one field to update"), or if IT Glue returns no data. HTTP 429 responses are retried up to 3 times. With Continue On Fail enabled, errors are emitted as an item with an error message.
Examples
Example 1: Rename a file attached to a configuration after upload.
Resource Type: Configuration; Resource ID: 12345; Attachment ID: 67890; Name: "Network diagram v2.pdf"
Example 2: Rename an attachment on a document using IDs from a previous Get Many step.
Resource Type: Document; Resource ID: {{$json.resourceId}}; Attachment ID: {{$json.id}}; Name: "Signed contract"