HeyReach API icon

HeyReach API

Interact with HeyReach API

Overview

The "Get Chatroom" operation under the "Inbox" resource in this HeyReach API node retrieves detailed information about a specific LinkedIn conversation chatroom. This is useful for scenarios where you want to fetch the full context or metadata of a LinkedIn conversation, such as viewing message history, participants, or conversation status within an automation workflow.

Practical examples include:

  • Automatically fetching conversation details when a new message arrives to trigger further actions.
  • Integrating LinkedIn conversation data into CRM systems or customer support tools.
  • Auditing or analyzing LinkedIn conversations programmatically.

Properties

Name Meaning
Account ID The LinkedIn account ID associated with the conversation. This identifies which LinkedIn account's inbox to query.
Conversation ID The unique identifier of the LinkedIn conversation whose chatroom details are to be retrieved.

Output

The output JSON contains the detailed data of the specified LinkedIn conversation chatroom. This typically includes conversation metadata such as participants, messages, timestamps, and possibly conversation status or other relevant fields returned by the HeyReach API.

If the node supports binary data output (not indicated here), it would represent any attachments or media related to the conversation.

Dependencies

  • Requires an active HeyReach API credential configured in n8n to authenticate requests.
  • Depends on the HeyReach API service being available at https://api.heyreach.io/api/n8n.
  • The user must have valid LinkedIn account linkage within HeyReach to access conversation data.

Troubleshooting

  • Common issues:

    • Invalid or missing Account ID or Conversation ID will cause the request to fail.
    • Authentication errors if the HeyReach API credential is not set up correctly.
    • Network or API downtime may result in request failures.
  • Error messages:

    • "Unauthorized" or "Authentication failed": Check that the API key credential is valid and has proper permissions.
    • "Conversation not found": Verify that the Conversation ID is correct and belongs to the specified Account ID.
    • "Invalid input": Ensure required properties are provided and correctly formatted.

Resolving these usually involves verifying credentials, confirming input parameters, and checking API service status.

Links and References

Discussion