Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
This node interacts with the "GateKit" API to retrieve all reactions associated with a specific identity across all linked platform accounts within a project. It is useful for scenarios where you want to analyze or monitor user engagement by fetching reaction data (such as emoji reactions) tied to an identity in messaging platforms integrated via GateKit.
For example, you might use this node to:
- Collect all reactions made by a user to messages across multiple platforms.
- Aggregate reaction data for analytics or reporting purposes.
- Trigger workflows based on user reactions.
Properties
| Name | Meaning |
|---|---|
| Identity ID | The unique identifier of the identity whose reactions you want to retrieve. |
| Project | The project identifier within which the identity exists and operations are performed. |
| Id | An additional id parameter (likely redundant with Identity ID, but required by the API). |
Output
The node outputs JSON data containing all reactions for the specified identity across all linked platform accounts. The structure corresponds to the API response from the endpoint:
GET /api/v1/projects/{project}/identities/{id}/reactions
The output JSON typically includes details about each reaction such as the message it relates to, the type of reaction (e.g., emoji), timestamps, and possibly platform-specific metadata.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the GateKit API.
- The node expects the base URL of the GateKit API to be configured in the credentials.
- The project identifier must correspond to an existing project in GateKit.
- The identity ID must be valid and exist within the specified project.
Troubleshooting
- Invalid Identity ID: If the provided identity ID does not exist, the API will likely return a 404 error. Verify the ID is correct.
- Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Ensure the API key is correctly set up.
- Project Not Found: Using an incorrect project identifier may result in errors. Confirm the project exists and the user has access.
- Empty Results: If no reactions are returned, verify that the identity has reactions recorded; otherwise, the result will be empty.
- Parameter Confusion: The presence of both "Identity ID" and "Id" properties might cause confusion. Both are required by the API routing but should be set to the same value representing the identity's ID.
Links and References
- GateKit API Documentation (hypothetical link)
- GateKit Platform Overview
Note: This summary is based solely on static analysis of the provided source code and property definitions.