Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
This node operation retrieves all reactions associated with a specific identity across all linked platform accounts within a given project. It is useful for scenarios where you want to analyze or monitor user engagement, sentiment, or interaction patterns by collecting reaction data tied to an identity. For example, you might use this to gather all emoji reactions a user has made on messages across multiple platforms integrated into your messaging system.
Properties
| Name | Meaning |
|---|---|
| Identity ID | The unique identifier of the identity whose reactions you want to retrieve. |
| Project | The project identifier under which the identity exists and operations are performed. |
| Id | An additional id parameter (likely redundant with Identity ID in this context). |
Output
The output JSON contains the list of reactions for the specified identity aggregated from all linked platform accounts. Each item typically includes details about the reaction such as the emoji used, the message it was applied to, timestamps, and possibly platform-specific metadata. This allows downstream processing or analysis of user reactions.
The node does not explicitly mention binary data output, so it is assumed to only return JSON data.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests.
- Needs access to the MsgCore API endpoint, with the base URL provided via credentials.
- The project identifier must be valid and accessible by the authenticated user.
Troubleshooting
- Invalid Identity ID: If the identity ID does not exist or is incorrect, the API will likely return an error or empty results. Verify the ID is correct.
- Unauthorized Access: Missing or invalid API credentials will cause authentication errors. Ensure the API key credential is properly set up.
- Project Not Found: Using an incorrect project identifier may result in resource not found errors. Confirm the project name or ID is accurate.
- Empty Reaction List: If no reactions are returned, verify that the identity has reactions recorded and that the linked platforms are correctly configured.
Links and References
- MsgCore API Documentation (generic reference, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding API calls
- Messaging platform integration guides relevant to your environment