Actions20
Overview
This node integrates with the Linq API to manage chat-related data. Specifically, for the "Chat" resource and the "Get Many" operation, it retrieves multiple chat records from the Linq platform. Users can filter chats by phone number and paginate through results using page number and items per page parameters.
Common scenarios where this node is useful include:
- Fetching a list of all chats associated with a specific phone number.
- Retrieving paginated chat data for display or further processing in workflows.
- Integrating chat data into CRM systems or analytics pipelines.
For example, a user might want to get all chats related to a customer’s phone number to analyze conversation history or trigger follow-up actions based on recent interactions.
Properties
| Name | Meaning |
|---|---|
| Phone Number | Filter chats by a specific phone number. |
| Page | The page number to retrieve for pagination (default is 1). |
| Per Page | Number of chat items to return per page (default is 25). |
Output
The output is an array of JSON objects representing chat data retrieved from the Linq API. Each item corresponds to a chat record matching the query parameters.
- The
jsonfield contains the raw response data from the Linq API endpoint/api/partner/v2/chats. - The structure typically includes chat metadata such as chat IDs, participants, display names, timestamps, and other relevant chat details.
- This node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Linq API (
integrationToken). - The node makes HTTP GET requests to the Linq API endpoint:
https://api.linqapp.com/api/partner/v2/chats. - Proper configuration of the API key credential in n8n is necessary for successful requests.
Troubleshooting
- Rate Limit Errors: If the node throws an error indicating "Rate limit exceeded," it means too many requests were made in a short time. Wait at least 10 seconds before retrying.
- Invalid Phone Number Format: Ensure the phone number filter is correctly formatted without extra spaces; the node trims and removes spaces internally.
- Pagination Issues: If no results are returned, verify that the page number and per-page values are within valid ranges and that the phone number filter matches existing chats.
- Authentication Failures: Confirm that the API key credential is valid and has the required permissions to access chat data.
Links and References
- Linq API Documentation (general reference for API endpoints and usage)
- n8n Documentation - HTTP Request Node (for understanding how HTTP requests work in n8n)
If you need summaries for other resources or operations, feel free to ask!