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
Webhook → Create
AI-generatedSummary
Create a webhook in Ploomes CRM by sending a JSON payload to POST /Webhooks, once per incoming item.
Inputs
- body — JSON payload containing the webhook properties expected by the Ploomes API. Defaults to {}. JSON strings are parsed before sending; the node does not define or validate individual webhook fields.
Output shape
API response data on the Success output, with each entry in a response value array emitted as a separate item; otherwise, the response is emitted as one item.
An empty response produces an item with success, resource, operation, and timestamp. HTTP 408 and 504 failures go to Timeout. Other failures go to Error when Continue On Fail is enabled; otherwise, execution throws. Failure items include error, statusCode, isTimeout, resource, operation, and timestamp.