Actions22
Overview
This node allows you to create an Activity for a Member in Crowd.dev, an open-source suite of community and data tools. The node is designed to log or track specific activities performed by members on various platforms (such as Discord, Slack, etc.), associating them with metadata like type, timestamp, platform, and more.
Common scenarios:
- Tracking when a member posts a message or comment on a platform.
- Logging user actions such as joining a channel, reacting to a post, or other engagement events.
- Integrating activity data from external sources into Crowd.dev for analytics or automation.
Practical example:
You can use this node in an n8n workflow to automatically record every time a user sends a message in a Discord channel, storing the message ID, content, and associated metadata in Crowd.dev.
Properties
| Name | Type | Meaning |
|---|---|---|
| Member | string | The ID of the member that performed the activity. Required. |
| Type | string | Type of activity (e.g., message, reaction, join). Required. |
| Timestamp | dateTime | Date and time when the activity took place. Required. |
| Platform | string | Platform on which the activity took place (e.g., Discord, Slack). Required. |
| Title | string | Title of the activity. Optional. |
| Body | string | Body/content of the activity. Optional. |
| Channel | string | Channel where the activity occurred. Optional. |
| Source ID | string | The ID of the activity in the platform (e.g., message ID in Discord). Required. |
| Source Parent ID | string | The ID of the parent activity in the platform (e.g., parent message ID in Discord). Optional. |
Output
The node outputs a JSON object representing the result of the API call to Crowd.dev. The structure typically mirrors the created activity's details as returned by the Crowd.dev API. If the API does not return a response, the output will be:
{
"result": "success"
}
If the API returns an array of results, each item will be output as a separate JSON object.
Note: If an error occurs and "Continue On Fail" is enabled, the output will include an error field with error details alongside the original input.
Dependencies
- External Service: Requires access to the Crowd.dev API.
- Credentials: You must configure the
crowdApicredential in n8n for authentication. - n8n Configuration: No additional environment variables are required beyond the credential setup.
Troubleshooting
Common issues:
- Missing Required Fields: If required properties (Member, Type, Timestamp, Platform, Source ID) are missing, the node will throw an error.
- Invalid Credentials: If the
crowdApicredential is not set up correctly, authentication errors will occur. - API Errors: Any errors returned by the Crowd.dev API (such as invalid IDs or network issues) will cause the node to fail unless "Continue On Fail" is enabled.
Error messages:
"Missing required property": Ensure all required fields are filled."Authentication failed": Check your Crowd.dev API credentials."Network error": Verify connectivity to the Crowd.dev API endpoint.