Actions33
- Public Actions
- Public Admin Actions
- Reseller Actions
- Create New Team
- Get Team Information
- Update Team
- Remove Team From Reseller
- Update Team Avatar
- Create Team Bulk Inboxes And Users
- Get Team Users
- Add User To Team
- Remove Users From Team
- Get Team Inboxes
- Remove Team Inboxes
- Create Team Bulk Inboxes
- Assign Users To Inbox
- Remove Users From Inbox
- Get Team Whitelist Domains
- Create Team Whitelisted Domain
- Remove Team Whitelisted Domain
- Create Reseller
- Import Team Users
- Get Import Team Users Job Status
Overview
This node operation "Get Team Inboxes" under the "Reseller" resource allows users to search and retrieve inboxes associated with a specific team. It is useful in scenarios where you need to programmatically access or filter team inboxes based on a search query, such as managing customer support channels, monitoring communication streams, or integrating team inbox data into workflows.
For example, a customer support manager could use this node to fetch all inboxes related to a particular team that match certain keywords, enabling automated reporting or routing of messages.
Properties
| Name | Meaning |
|---|---|
| Team Id | The unique identifier of the team whose inboxes you want to retrieve. |
| Query | The search string used to filter inboxes within the specified team. |
| Additional Query Parameters | Optional parameters to control pagination: • Skip: Number of inboxes to skip. • Take: Number of inboxes to return. |
Output
The output will be a JSON object containing the list of team inboxes matching the search criteria. Each item in the json output typically represents an inbox with its details (such as inbox ID, name, status, etc.). If binary data were involved, it would represent attachments or files related to inboxes, but this operation focuses on JSON data only.
Dependencies
- Requires an API key credential for authentication to the external service providing the reseller/team inbox data.
- The node depends on a base URL configured via credentials to connect to the appropriate API endpoint.
- No additional external services are explicitly required beyond the authenticated API access.
Troubleshooting
- Missing or invalid Team Id: Ensure the "Team Id" property is provided and correctly corresponds to an existing team; otherwise, the API may return errors or empty results.
- Empty or malformed Query: The "Query" parameter is required; omitting it or providing invalid input might cause the request to fail or return no results.
- Pagination issues: Incorrect values for "Skip" and "Take" can lead to unexpected results or empty responses. Use sensible numbers (e.g., non-negative integers) to paginate through results.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions to access team inbox data.
- API rate limits or connectivity problems: Network issues or hitting API limits may cause errors; check network connectivity and API usage policies.
Links and References
- Refer to the API documentation of the external service managing team inboxes for detailed information on query parameters and response structure.
- n8n documentation on how to configure API key credentials and use query parameters in nodes.