Actions22
Overview
The Crowd.dev Node for n8n enables you to create or update a "Member" resource in the Crowd.dev platform. This operation is useful for synchronizing user/member data between your systems and Crowd.dev, ensuring that member profiles are up-to-date or created as needed. Common scenarios include onboarding new community members, updating existing member information, associating members with organizations, tags, tasks, notes, or activities, and managing their metadata.
Practical examples:
- Automatically add or update a member when they join your Slack workspace.
- Sync CRM contacts as Crowd.dev members, including their emails, organizations, and tags.
- Enrich member profiles with additional details such as joined date, associated tasks, or activities.
Properties
| Name | Type | Meaning |
|---|---|---|
| Platform | String | Platform for which to check member existence (e.g., GitHub, Twitter). Required. |
| Username | Collection | Key-value pairs representing usernames on various platforms. |
| Display Name | String | UI-friendly name of the member. |
| Emails | Collection | List of email addresses associated with the member. |
| Joined At | DateTime | The date when the member joined the community. |
| Organizations | Collection | Organizations associated with the member. Each can include name, URL, description, logo, employee count, and member IDs. |
| Tags | Collection | Tags associated with the member. Each element is a tag ID. |
| Tasks | Collection | Tasks associated with the member. Each element is a task ID. |
| Notes | Collection | Notes associated with the member. Each element is a note ID. |
| Activities | Collection | Activities associated with the member. Each element is an activity ID. |
Output
The node outputs a JSON object for each processed item. The structure depends on the response from the Crowd.dev API:
- On success, the output will typically be the full member object as returned by the API, containing all relevant fields (such as IDs, names, emails, organizations, etc.).
- If the API returns no content, the output will be:
{ "result": "success" } - In case of errors and if "Continue On Fail" is enabled, the output will include the original input and an error field.
Note: The node does not output binary data.
Dependencies
- External Service: Requires access to the Crowd.dev API.
- API Credentials: You must configure the
crowdApicredential in n8n. - n8n Configuration: Ensure the node has network access to the Crowd.dev API endpoint.
Troubleshooting
Missing or Invalid Credentials:
Error: "No credentials found" or authentication errors.
Resolution: Make sure thecrowdApicredential is set up correctly in n8n.Invalid Input Data:
Error: "Bad Request" or validation errors from the API.
Resolution: Check that all required fields (like Platform) are provided and formatted correctly.Network/Connection Issues:
Error: "Request failed with status code 500" or timeout errors.
Resolution: Verify network connectivity and the availability of the Crowd.dev API.Unexpected Output Structure:
If the output is{ "result": "success" }but you expect more data, the API may not have returned any content.
Resolution: Double-check the input parameters and ensure the member exists or is being created as expected.