Actions7
Overview
The Export LinkedIn Chat History operation in the "Browserflow for LinkedIn" n8n node allows users to automate the retrieval of chat (message) history from a specific LinkedIn profile. This is particularly useful for sales, recruitment, or networking professionals who need to archive, analyze, or process their LinkedIn conversations outside of the LinkedIn platform.
Practical examples:
- Exporting all messages exchanged with a lead for CRM integration.
- Backing up important LinkedIn conversations for compliance or record-keeping.
- Analyzing communication patterns with contacts for business intelligence.
Properties
| Name | Type | Meaning |
|---|---|---|
| LinkedIn URL | String | The LinkedIn profile URL to get chat history. This should be the full URL of the contact whose chat history you want to export. |
Output
The node returns the exported chat history as JSON data. While the exact structure depends on the Browserflow API response, you can expect the output to include message details such as sender, timestamp, and content for each message exchanged with the specified LinkedIn profile.
Example output structure:
{
"messages": [
{
"sender": "John Doe",
"timestamp": "2024-05-01T12:34:56Z",
"content": "Hello, how are you?"
},
{
"sender": "You",
"timestamp": "2024-05-01T12:35:10Z",
"content": "I'm good, thanks!"
}
// ... more messages
]
}
Note: The actual field names may vary depending on the API's implementation.
Dependencies
- External Service: Requires access to the Browserflow API.
- API Key: You must configure valid Browserflow API credentials in n8n under the name
browserflowApi. - n8n Configuration: No additional environment variables are required beyond the API key setup.
Troubleshooting
Common issues:
- Invalid or missing LinkedIn URL: Ensure the LinkedIn URL is correct and points to a valid profile.
- Authentication errors: If your API key is invalid or missing, the node will fail to connect to Browserflow. Check your credentials configuration.
- Rate limits or API restrictions: Excessive requests may trigger rate limiting by Browserflow or LinkedIn.
- LinkedIn session/authentication issues: If Browserflow cannot access your LinkedIn account, ensure your Browserflow setup is correctly authenticated with LinkedIn.
Possible error messages:
"401 Unauthorized": Check your Browserflow API credentials."400 Bad Request": The LinkedIn URL may be malformed or missing."500 Internal Server Error": Temporary issue with Browserflow; try again later.