Linq icon

Linq

Interact with Linq API
Join our community

Actions20

Overview

This node interacts with the Linq API to manage chat messages and their reactions among other resources. Specifically, for the Chat Message - Get Reaction operation, it retrieves the reaction associated with a particular chat message by its ID. This is useful in scenarios where you want to monitor or respond to user reactions on messages within a chat, such as tracking emoji responses or feedback.

Practical examples include:

  • Fetching the current reaction on a message to display it in a dashboard.
  • Automating workflows based on specific reactions (e.g., triggering an alert if a message receives a "thumbs up").
  • Aggregating reactions for analytics or reporting purposes.

Properties

Name Meaning
Chat Message ID The unique identifier of the chat message whose reaction you want to retrieve.

Output

The node outputs a JSON object containing the data returned from the Linq API about the reaction on the specified chat message. The structure depends on the API response but typically includes details such as the type of reaction and possibly the users who reacted.

No binary data output is involved in this operation.

Example output JSON might look like:

{
  "reaction": "👍",
  "user_id": "12345",
  "timestamp": "2024-01-01T12:00:00Z"
}

Dependencies

  • Requires an API key credential for authenticating with the Linq API.
  • The node makes HTTP requests to https://api.linqapp.com/api/partner/v2/chat_messages/{chatMessageId}/reaction.
  • Ensure the API key has permissions to access chat message reactions.
  • No additional environment variables are required beyond the API credential.

Troubleshooting

  • Rate Limit Exceeded: If the node throws an error indicating rate limit exceeded, wait at least 10 seconds before retrying.
  • Invalid Chat Message ID: Providing an incorrect or non-existent chat message ID will result in an error from the API. Verify the ID is correct.
  • Authentication Errors: Ensure the API key credential is valid and has not expired.
  • Network Issues: Check connectivity to the Linq API endpoint.

Links and References

Discussion