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
Contact Line of Business → Delete
AI-generatedSummary
Deletes a Contact Line of Business record from Ploomes CRM. Set Resource to Contact Line of Business and Operation to Delete, then supply the required ID parameter (resourceId) — the ID of the line-of-business record to remove; it can be an expression evaluated per incoming item. The node authenticates with the Ploomes API credential and sends a DELETE request to /Contacts@LinesOfBusiness({ID}) with no request body. Because Ploomes returns an empty body on a successful DELETE, each successfully processed input item produces a confirmation object: { success: true, resource: 'contactLineOfBusiness', operation: 'delete', timestamp: '<ISO timestamp>' }. If the API returns a non-empty response body, that body is passed through instead. Failed requests are routed to the Error output (or the Timeout output for HTTP 408/504 responses); with Continue On Fail disabled, a non-timeout error throws and stops the workflow.
Inputs
None.
Output shape
{
"description": "..."
}
I need to output JSON matching the schema. Without an explicit schema, the safest is a single
descriptionfield.
