Actions25
Overview
The node interacts with the Whoz talent management platform, specifically allowing operations on various resources such as accounts, talents, dossiers, billing items, and tasks. For the Account resource with the Get Many operation, it retrieves multiple account records based on a list of external IDs. This is useful when you want to fetch detailed information about several accounts (companies or organizations) in bulk by specifying their external identifiers.
Practical examples include:
- Fetching multiple client company profiles at once for reporting or integration purposes.
- Retrieving updated account data filtered by modification date or including soft-deleted accounts.
- Limiting the number of returned results to optimize performance or comply with API constraints.
Properties
| Name | Meaning |
|---|---|
| External IDs | Comma-separated list of external IDs to search for. These identify the accounts to retrieve. |
| Options | Collection of optional parameters: |
| Limit | Maximum number of results to return. |
| Include Removed | Whether to include soft-deleted (removed) accounts in the results (true/false). |
| Modified Since | Only return accounts modified since this date/time (ISO 8601 format). |
Output
The output is a JSON array where each element represents an account object retrieved from the Whoz platform. Each account object contains the account's details as provided by the API, such as identifiers, names, addresses, status, and other metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for the Whoz platform.
- The node uses the Whoz API endpoints, switching between sandbox and production environments based on credential settings.
- No additional external dependencies beyond the Whoz API and n8n's HTTP request capabilities.
Troubleshooting
- Missing or invalid External IDs: The operation requires at least one external ID. Ensure the "External IDs" property is set and correctly formatted as comma-separated values.
- API authentication errors: Verify that the OAuth2 credentials are valid and have the necessary permissions.
- Rate limiting or large result sets: If requesting many accounts, consider using the "Limit" option to avoid hitting API limits or timeouts.
- Date format issues: The "Modified Since" filter must be a valid ISO 8601 datetime string; otherwise, the API may reject the request.
- Including removed accounts: Setting "Include Removed" to true will return soft-deleted accounts; if unexpected results appear, verify this setting.
Common error messages typically relate to missing required parameters or API authorization failures. Resolving them involves checking input properties and credential configurations.
Links and References
- Whoz API Documentation (general reference for API endpoints and data structures)
- n8n OAuth2 Credential Setup (for configuring API authentication)
This summary is based solely on static analysis of the provided source code and property definitions.