Browserflow for LinkedIn icon

Browserflow for LinkedIn

Automate LinkedIn with Browserflow

Overview

This node integrates with the Browserflow API to automate various LinkedIn-related tasks, including exporting LinkedIn chat history. Specifically, the Export LinkedIn Chat History operation retrieves messages from a LinkedIn conversation given a profile URL. This is useful for users who want to archive or analyze their LinkedIn chats programmatically.

Common scenarios include:

  • Exporting chat history for CRM or customer support follow-up.
  • Analyzing communication patterns with LinkedIn contacts.
  • Backing up important conversations automatically.

Example: Given a LinkedIn profile URL, the node fetches the last N messages exchanged in the chat with that contact.

Properties

Name Meaning
LinkedIn URL The LinkedIn profile URL to get chat history from.
Number of Messages Specify how many recent messages to retrieve. If left blank, all available messages will be fetched.

Output

The node outputs a JSON array where each item contains the chat history data retrieved from the LinkedIn profile specified. The exact structure depends on the API response but generally includes message details such as sender, timestamp, and message content.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the Browserflow service to authenticate requests.
  • The node makes HTTP POST requests to the Browserflow API endpoint https://app.browserflow.io/api/linkedin-get-chat-history.
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing LinkedIn profile URL: Ensure the URL is correct and publicly accessible.
    • API authentication errors: Verify that the API key credential is correctly set and has sufficient permissions.
    • Network or connectivity problems: Check internet connection and API availability.
  • Error messages:

    • Errors include HTTP status codes and descriptive messages returned by the API.
    • Example error: "An error with status 401 occurred" indicates unauthorized access due to invalid API key.
    • Resolution: Recheck API key credentials and update if necessary.

Links and References

Discussion