Actions34
- Activity Actions
- Deal Actions
- Funnel Actions
- Organization Actions
- Person Actions
- Product Actions
- Tag Actions
- User Actions
Overview
This node integrates with the Agendor CRM API to manage activities (tasks, calls, emails, meetings, notes) within the CRM system. Specifically, the Delete Activity operation allows users to delete an existing activity by its unique identifier.
Common scenarios for this node include:
- Automating cleanup of outdated or irrelevant activities in your CRM.
- Integrating with other workflows where activities need to be removed based on external triggers.
- Maintaining data hygiene by programmatically deleting completed or canceled tasks.
For example, you might use this node in a workflow that deletes activities related to deals that have been lost or closed, ensuring your CRM only contains relevant and active tasks.
Properties
| Name | Meaning |
|---|---|
| Activity ID | The unique identifier of the activity to delete. This is required to specify which activity should be removed from the CRM. |
Output
The output of the Delete Activity operation typically contains a JSON object representing the response from the Agendor API after attempting to delete the specified activity. Usually, for a successful deletion, the API returns an empty object or confirmation message indicating the resource was deleted.
No binary data is output by this node.
Dependencies
- Requires an API authentication token credential for Agendor CRM to authorize requests.
- The node sends HTTP DELETE requests to the Agendor API endpoint
https://api.agendor.com.br/v3/activities/{activityId}. - Proper configuration of the API token credential in n8n is necessary for successful execution.
Troubleshooting
- Missing or invalid Activity ID: If the Activity ID is not provided or incorrect, the API will return an error indicating the resource was not found. Ensure the Activity ID is correct and exists in your Agendor account.
- Authentication errors: If the API token is missing, expired, or invalid, the request will fail with an authorization error. Verify your API token credential is correctly set up in n8n.
- Network issues: Connectivity problems can cause request failures. Check your network connection and firewall settings.
- API rate limits: Excessive requests may trigger rate limiting by Agendor. Implement retry logic or reduce request frequency if needed.
Links and References
- Agendor API Documentation (official API docs for reference)
- n8n Documentation (for general guidance on using credentials and HTTP request nodes)