Actions22
Overview
The Crowd.dev Node for n8n enables you to interact with the Crowd.dev platform, specifically to create new tasks. This node is useful in automation scenarios where you want to programmatically add tasks to your Crowd.dev workspace based on triggers or workflows—such as creating a task when a new lead is added, or when an event occurs in another system.
Practical examples:
- Automatically create a follow-up task when a new community member joins.
- Assign tasks to specific users when certain activities are detected.
- Log tasks related to user engagement or support requests.
Properties
| Name | Type | Meaning |
|---|---|---|
| Name | String | The name of the task. |
| Body | String (multi-line) | The body or description of the task. |
| Status | String | The status of the task (e.g., open, closed, in progress). |
| Members | Array of Strings | Members associated with the task; each element is a member ID. |
| Activities | Array of Strings | Activities associated with the task; each element is an activity ID. |
| Assigneess | String | Users assigned to the task; should be a comma-separated list or array of user IDs. |
Output
The node outputs a JSON object representing the result of the task creation operation. The structure typically includes:
On success:
{ "result": "success" }or the full response from the Crowd.dev API, which may include details about the created task (such as its ID, name, status, etc.).
On error (if "Continue On Fail" is enabled):
{ ...originalInput, "error": <errorObject>, "pairedItem": <itemIndex> }
If the API returns an array, each item will be output as a separate JSON object.
Dependencies
- External Service: Requires access to the Crowd.dev API.
- API Key/Credentials: You must configure the
crowdApicredential in n8n. - n8n Configuration: No special environment variables required beyond standard credential setup.
Troubleshooting
Common Issues:
- Missing or invalid credentials: Ensure that the
crowdApicredential is correctly set up in n8n. - Invalid input data: Supplying incorrect types (e.g., non-string values for IDs) may cause API errors.
- API errors: If the Crowd.dev API returns an error, it will be surfaced in the node's output or as a thrown error if "Continue On Fail" is not enabled.
Error Messages:
"result": "success"but no task appears: Check that all required fields are filled and valid.NodeOperationError: Indicates a problem with the API call or input data. Review the error message for specifics.- Errors with
context.itemIndex: These help identify which input item caused the failure.