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
Interaction Record → Create
AI-generatedSummary
Create an interaction record in Ploomes CRM by sending the supplied JSON body to /InteractionRecords. Sends one POST request per incoming workflow item.
Inputs
- body — JSON containing the interaction record properties to create; defaults to {}. Accepts a JSON string or object and sends it directly to the API. Required entity fields are not specified by the node.
Output shape
API response data on the Success output, with each entry in an OData value array emitted as a separate item; otherwise, the response is emitted as one item.
An empty response produces a success confirmation with resource, operation, and timestamp. HTTP 408 and 504 errors go to Timeout. Other errors go to Error when Continue On Fail is enabled; otherwise, they stop execution. Error items include error, statusCode, isTimeout, resource, operation, and timestamp.