Actions22
Overview
The Crowd.dev Node for n8n enables users to interact with the Crowd.dev platform, specifically targeting automations. The Automation: Destroy operation allows you to delete (destroy) a specific automation by its ID. This is useful in scenarios where you need to programmatically remove outdated or unnecessary automations from your Crowd.dev workspace as part of automated workflows.
Practical examples:
- Automatically clean up test automations after running integration tests.
- Remove automations that are no longer needed based on certain triggers or conditions in your workflow.
Properties
| Name | Type | Meaning |
|---|---|---|
| ID | String | The ID of the automation to be destroyed. Required to identify which automation will be deleted. |
Output
The node outputs a JSON object per input item:
- On success:
{ "result": "success" } - If the API returns data, it will output the response as-is in the
jsonfield. - In case of errors and if "Continue On Fail" is enabled, the output will include:
- The original input's JSON,
- An
errorfield with error details, - A
pairedItemfield indicating the index of the failed item.
Dependencies
- External Service: Requires access to the Crowd.dev API.
- Credentials: Needs a configured
crowdApicredential in n8n. - n8n Configuration: No special environment variables required beyond the credential setup.
Troubleshooting
Common Issues:
- Invalid or missing ID: If the provided ID does not correspond to an existing automation, the API may return an error.
- Authentication errors: If the
crowdApicredentials are missing or incorrect, requests will fail. - Network/API errors: Connectivity issues or API downtime can cause failures.
Error Handling:
- If "Continue On Fail" is enabled, errors are included in the output for each failed item.
- Otherwise, the workflow execution stops and throws an error, possibly including context such as the item index.