Actions22
Overview
The Crowd.dev Node for n8n enables you to interact with the Crowd.dev platform, specifically to update information about a member. The "Member: Update" operation allows you to modify details such as platform, usernames, display name, emails, organizations, tags, tasks, notes, and activities associated with an existing member in your Crowd.dev community.
Common scenarios:
- Keeping member profiles up-to-date when new information is available.
- Syncing user data from other systems (e.g., CRM, email platforms) into Crowd.dev.
- Managing organizational or activity associations for members programmatically.
Practical example:
You might use this node to automatically update a member's profile when they change their email address in another system, or to add new tags/activities based on their recent interactions.
Properties
| Name | Type | Meaning |
|---|---|---|
| ID | String | The unique identifier of the member to update. |
| Platform | String | The platform for which to check member existence (e.g., GitHub, Twitter). |
| Username | Collection | One or more key-value pairs representing usernames on different platforms. |
| Display Name | String | A UI-friendly name for the member. |
| Emails | Collection | One or more email addresses associated with the member. |
| Joined At | DateTime | The date the member joined the community. |
| Organizations | Collection | List of organizations associated with the member. Each can include name, URL, description, logo, employees, and members. If an organization does not exist, it will be created. |
| Tags | Collection | List of tag IDs associated with the member. |
| Tasks | Collection | List of task IDs associated with the member. |
| Notes | Collection | List of note IDs associated with the member. |
| Activities | Collection | List of activity IDs associated with the member. |
Output
The node outputs a JSON object reflecting the result of the update operation. The structure typically includes the updated member data as returned by the Crowd.dev API. If the API call returns no data, the output will be:
{
"result": "success"
}
If the API returns member data, the output will mirror the fields provided by the API, which may include all or some of the properties listed above.
Dependencies
- External Service: Requires access to the Crowd.dev API.
- Credentials: You must configure the
crowdApicredential in n8n with appropriate API keys or tokens for authentication.
Troubleshooting
Common issues:
- Missing or invalid credentials: Ensure that the
crowdApicredential is set up correctly in n8n. - Invalid Member ID: If the provided ID does not correspond to an existing member, the update will fail.
- Incorrect property formats: Ensure collections (like emails, organizations, etc.) are structured as required.
Error messages:
"NodeOperationError": Indicates a problem during execution, such as invalid input or API errors. Check the error message for specifics."result": "success"but no data: The update was accepted, but the API did not return any content. This is normal if the API uses 204 No Content responses.
How to resolve:
- Double-check all required fields, especially the ID and Platform.
- Review the API credentials and permissions.
- Validate the format of collection-type properties.