Actions22
Overview
This n8n custom node integrates with Crowd.dev, an open-source suite of community and data tools. Specifically, for the Activity resource and its default operation, the node allows you to create or log activity events from various platforms (such as Discord, Slack, etc.) into Crowd.dev. This is useful for tracking user engagement, message exchanges, or any significant actions across different channels and platforms.
Common scenarios:
- Logging messages or interactions from chat platforms into Crowd.dev for analytics.
- Tracking user activities (like posts, comments, reactions) in a unified community dashboard.
- Automating the ingestion of platform-specific activity data for further processing or reporting.
Practical example:
Automatically record every new message posted in a Discord channel as an activity in Crowd.dev, including details like timestamp, platform, channel, and message content.
Properties
| Name | Type | Meaning |
|---|---|---|
| Type | String | Type of activity (e.g., message, comment, reaction). |
| Timestamp | DateTime | Date and time when the activity took place. |
| Platform | String | Platform on which the activity occurred (e.g., Discord, Slack). |
| Title | String | Title of the activity (optional; e.g., subject or summary). |
| Body | String | Body/content of the activity (optional; e.g., message text). |
| Channel | String | Channel where the activity happened (e.g., channel name or ID). |
| Source ID | String | The unique ID of the activity in the source platform (e.g., message ID in Discord). |
| Source Parent ID | String | The ID of the parent activity in the platform (e.g., parent message ID; optional). |
Output
The node outputs a JSON object for each processed item. The structure typically mirrors the response from the Crowd.dev API or confirms success. Possible output structures:
- On success, if the API returns data:
{ "result": "success" } - If the API returns an array, each element is output as a separate JSON object.
- If the API returns a single object, it is passed through as-is.
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.
- API Key/Credentials: Needs valid Crowd.dev API credentials configured in n8n under the credential type
crowdApi. - n8n Configuration: No special environment variables required beyond standard credential setup.
Troubleshooting
Common issues:
- Missing or invalid credentials: Ensure that the Crowd.dev API credentials are correctly set up in n8n.
- Required fields missing: Fields like Type, Timestamp, Platform, and Source ID are mandatory. Omitting them will result in errors.
- API errors: If the Crowd.dev API returns an error (e.g., invalid data, rate limits), the node will throw an error unless "Continue On Fail" is enabled.
Error messages:
"Missing required property": Check that all required properties are provided."Invalid credentials": Verify your Crowd.dev API key and permissions."API request failed": Inspect the error details for more information; may indicate network issues or incorrect endpoint usage.