Actions14
- AutoCPH Actions
- Linkedin Actions
- Person Actions
- Project Actions
- Reply Actions
Overview
This node integrates with the Leadspicker API to manage projects, persons, replies, and LinkedIn-related data. Specifically, for the Delete Project operation, it allows users to delete an existing project by specifying its unique project ID.
Typical use cases include:
- Cleaning up or removing obsolete projects from your Leadspicker account.
- Automating project lifecycle management within workflows.
- Integrating project deletion as part of larger automation processes involving Leadspicker data.
Example: You have a project that is no longer needed, and you want to remove it automatically when certain conditions are met in your workflow. This node can be configured to delete that project by providing its ID.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project to delete |
Output
The node outputs JSON data representing the response from the Leadspicker API after attempting to delete the specified project. Typically, this will confirm successful deletion or provide error details if the deletion failed.
The output JSON structure depends on the API's response but generally includes status information about the deletion request.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Leadspicker API via an API key credential configured in n8n.
- The node uses HTTP requests to communicate with Leadspicker endpoints.
- No additional external dependencies beyond the API access are required.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Project ID will result in an error from the API.
- Network connectivity issues may prevent the node from reaching the Leadspicker service.
- Insufficient permissions associated with the API key could block project deletion.
Error Messages:
"The operation "delete" is not supported for Project resource."— indicates a misconfiguration or unsupported operation; ensure the operation is set correctly.- API errors related to authorization or invalid IDs will be returned as error messages in the node output.
Resolution Tips:
- Verify the Project ID is correct and exists in your Leadspicker account.
- Check that the API key credential has the necessary permissions.
- Ensure network connectivity and that the Leadspicker API endpoint is reachable.
Links and References
- Leadspicker API Documentation (general reference for API endpoints and usage)
- n8n Documentation on Creating Custom Nodes