Actions20
Inbox → Get Many
AI-generatedOverview
The node integrates with the Reachkit API to retrieve multiple inbox records. It is designed to fetch a list of inboxes, optionally filtered by search terms and paginated. This operation is useful when you want to programmatically access and manage your inbox data from Reachkit, such as displaying all inboxes in a dashboard or processing them for analytics.
Common scenarios include:
- Retrieving all inboxes to synchronize with another system.
- Searching inboxes by keyword to find specific conversations or messages.
- Paginating through inboxes when dealing with large volumes of data.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all inbox results or limit the number of results returned. |
| Limit | Maximum number of inbox results to return (only used if "Return All" is false). |
| Additional Fields | Optional extra parameters: |
| - Page | The page number of results to retrieve (for pagination). |
| - Search | A search term to filter inboxes by matching text. |
Output
The node outputs JSON data representing the retrieved inboxes from Reachkit. The structure typically includes an array of inbox objects, each containing details about individual inbox entries such as IDs, names, statuses, or other metadata provided by the Reachkit API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Reachkit API.
- The base URL for API requests is
https://reachkit.ai/api/v1. - Proper configuration of the API key credential within n8n is necessary.
Troubleshooting
Issue: No inboxes are returned despite expecting results.
- Cause: The search term may be too restrictive or no inboxes exist.
- Solution: Try removing or broadening the search term; verify inboxes exist in Reachkit.
Issue: Error related to authentication.
- Cause: Invalid or missing API key credential.
- Solution: Ensure the API key credential is correctly set up and has proper permissions.
Issue: Pagination not working as expected.
- Cause: Incorrect page number or limit values.
- Solution: Verify that the "Page" and "Limit" properties are within allowed ranges (page ≥ 1, limit between 1 and 100).
Links and References
- Reachkit API Documentation (assumed official docs for further details on inbox endpoints)
- n8n documentation on API credentials