Actions126
- Account Actions
- City Actions
- Contact Actions
- Contact Line of Business Actions
- Contact Number of Employees Actions
- Contact Origin Actions
- Contact Product Actions
- Contact Relationship Actions
- Contact Status Actions
- Contact Type Actions
- Country Actions
- Currency Actions
- Deal Actions
- Deal Loss Reason Actions
- Deal Pipeline Actions
- Deal Stage Actions
- Deal Status Actions
- Department Actions
- Document Actions
- Document Template Actions
- Field Actions
- Field Entity Actions
- Field Options Table Actions
- Field Options Table Option Actions
- Field Type Actions
- Interaction Record Actions
- Operation Actions
- Order Actions
- Order Stage Actions
- Phone Type Actions
- Product Actions
- Product Family Actions
- Product Group Actions
- Product Part Actions
- Quote Actions
- Quote Approval Status Actions
- Relative Date Actions
- Role Actions
- State Actions
- Tag Actions
- Task Actions
- Task Email Reminder Actions
- Task Repeat Interval Unit Actions
- Task Type Actions
- Team Actions
- User Actions
- User Profile Actions
- Webhook Actions
- Webhook Action Actions
Tag → Update
AI-generatedSummary
Updates a Tag record in Ploomes CRM via PATCH request.
Inputs
- resourceId (required) — The ID (or Key for Fields) of the resource
- body — JSON body to send with the request. For updating records, include the entity properties to update here.
Output shape
The API response body, typically the updated tag record, passed through n8n item JSON.
No OData query parameters are applied; the operation sends a PATCH to /Tags({resourceId}) with the provided body JSON. The resourceId parameter is required; body defaults to {} if omitted. Tag is a full CRUD resource, so update is supported alongside getAll, create, and delete.
Examples
Example 1: Update a tag's name
Set resourceId to the tag's ID, and body to { Name: 'New Tag Name' }.