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
Product Group → Create
AI-generatedSummary
Creates a new product group in Ploomes CRM by sending a POST request with a user-supplied JSON body to the /Products@Groups endpoint of https://api2.ploomes.com.
Inputs
- Body (JSON) — JSON object with the product group's properties (e.g. Name), sent as the POST request body. Defaults to {}, which would send an empty object, so include the fields the Ploomes API requires. Accepts a JSON string (parsed before sending) or an object/expression. Evaluated per input item.
Output shape
One item on the Success output per input item, containing the JSON returned by the Ploomes API. If the response has a value array, each element becomes its own item. If the response is empty, a stub item is returned: { success: true, resource, operation, timestamp }.
The node has three outputs: Success, Error, and Timeout. Failed requests produce an item with error, statusCode, isTimeout, resource, operation and timestamp on the Error output. HTTP 408/504 responses go to Timeout instead. Without 'Continue on Fail', a non-timeout error stops the workflow. Invalid JSON in the body also lands in the error path. Requires the ploomesApi credential. The cache settings apply only to Get Many, not to Create.
Examples
Example 1: Create a new product group named 'Software Licenses'.
Resource: Product Group; Operation: Create; Body (JSON): {"Name": "Software Licenses"}
Example 2: Create a product group for each incoming row from a spreadsheet.
Resource: Product Group; Operation: Create; Body (JSON) as an expression such as {{ JSON.stringify({ Name: $json.groupName }) }}. The node runs once per input item.
