Actions22
Overview
This node allows you to create or update an Activity in Crowd.dev, associating it with a Member. It is designed for scenarios where you want to log community activities (such as messages, posts, or events) and link them to specific members within your community platform. This is useful for tracking engagement, building member profiles, and analyzing community interactions.
Practical examples:
- Logging a new message posted by a user on Discord or Slack.
- Recording when a member joins a channel or participates in an event.
- Updating activity details if the same action occurs again.
Properties
| Name | Type | Meaning |
|---|---|---|
| Member | fixedCollection | Details about the member associated with the activity, including username, display name, emails, and join date. |
| Type | string | The type of activity (e.g., "message", "join", etc.). Required. |
| Timestamp | dateTime | The date and time when the activity took place. Required. |
| Platform | string | The platform where the activity occurred (e.g., "Discord", "Slack"). Required. |
| Title | string | The title of the activity. |
| Body | string | The body/content of the activity. |
| Channel | string | The channel where the activity happened. |
| Source ID | string | The unique identifier of the activity in the source platform (e.g., message ID). Required. |
| Source Parent ID | string | The unique identifier of the parent activity in the source platform (e.g., parent message ID). |
Member (fixedCollection) sub-properties:
- Username: Key-value pairs representing usernames on different platforms.
- displayName: UI-friendly name of the member.
- Emails: List of email addresses for the member.
- Joined At: Date when the member joined the community.
Output
The node outputs a json object for each processed item. The structure depends on the API response from Crowd.dev:
- On success, the output will contain the data returned by the Crowd.dev API for the created or updated activity.
- If the API returns no data, 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 error information.
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 for authentication. - n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
Common Issues:
- Missing Required Fields: If required fields like "Type", "Timestamp", "Platform", or "Source ID" are missing, the node will throw an error.
- Invalid API Credentials: If the
crowdApicredential is not set up correctly, authentication will fail. - API Errors: Any errors returned by the Crowd.dev API (e.g., invalid data, rate limits) will cause the node to fail unless "Continue On Fail" is enabled.
Error Messages:
"Missing required parameter": Ensure all required properties are provided."Authentication failed": Check your Crowd.dev API credentials."API request failed": Review the error details for more information; may indicate network issues or invalid data.