Actions79
- Lead Status Actions
- Pipeline Actions
- Template Actions
- Lead Actions
- Contact Actions
- Activity Actions
- Meeting Search Actions
- Opportunity Actions
- Opportunity Status Actions
- Integration Link Actions
- Smart View Actions
- Comment Actions
- Email Template Actions
- Task Actions
- User Actions
- Custom Field Actions
Overview
This node integrates with the Close.com CRM platform, allowing users to perform various operations on different CRM resources. Specifically, for the Template resource with the Delete operation, it enables users to delete an existing email or SMS template by specifying its type and unique identifier. This is useful for maintaining and cleaning up templates that are no longer needed or relevant.
Practical examples include:
- Removing outdated marketing email templates.
- Deleting SMS templates that are deprecated or replaced.
- Automating template lifecycle management as part of a larger workflow.
Properties
| Name | Meaning |
|---|---|
| Template Type | The type of template to delete. Options: "Email" (email template), "SMS" (SMS template). |
| Template ID | The unique identifier of the template to delete. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm successful deletion or provide error details if the operation failed. The output does not include binary data.
Example output JSON might look like:
{
"success": true,
"id": "template_id_deleted"
}
or in case of failure:
{
"error": "Template not found"
}
Dependencies
- Requires an API key credential for authenticating with the Close.com CRM API.
- The node depends on the Close.com API being accessible and the user having appropriate permissions to delete templates.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Template ID: Ensure the Template ID provided exists and is correct.
- Insufficient permissions: The API key used must have rights to delete templates.
- Network or API errors: Check connectivity and API status.
Error messages:
"The resource "template" is not known!"— This indicates an invalid resource parameter; ensure "Template" is selected.- Errors returned from the API such as "Template not found" or permission denied should be handled by verifying input parameters and credentials.
To resolve errors, verify the Template Type and Template ID inputs, check API credentials, and ensure the Close.com service is operational.