Actions25
Overview
This node operation retrieves multiple billing items from the Whoz talent management platform. It allows filtering billing items based on various criteria such as dossier ID, workspace ID, month, type of billing item, modification date, and whether to include soft-deleted items. This operation is useful for scenarios where you need to list or analyze billing data in bulk, for example, generating reports, auditing billing records, or integrating billing information into other systems.
Properties
| Name | Meaning |
|---|---|
| Filters | Collection of filters to narrow down the billing items returned: |
| - Dossier ID | Filter billing items by a specific dossier (opportunity/deal) ID |
| - Workspace ID | Filter billing items by a specific workspace ID |
| - Month | Filter billing items by month in YYYY-MM format |
| - Type | Filter by billing item type; options are: Billing, Turnover Recognition |
| - Modified Since | Return only billing items modified since this date |
| - Include Removed | Boolean flag to include soft-deleted (removed) billing items |
| Options | Additional options for controlling the result set: |
| - Limit | Maximum number of billing items to return |
| - Offset | Number of billing items to skip before starting to return results |
Output
The output is a JSON array where each element represents a billing item object retrieved from the Whoz platform. Each billing item contains fields describing its details such as IDs, dates, types, amounts, and status. The exact structure depends on the Whoz API response but typically includes identifiers, timestamps, monetary values, and related metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Whoz talent management platform via an OAuth2 API credential.
- The node uses the Whoz API endpoints, with base URL switching between sandbox and production environments depending on the credential configuration.
- Proper API authentication credentials must be configured in n8n for this node to function.
Troubleshooting
- Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Incorrect filter values (e.g., malformed dates or unknown IDs) may result in empty responses or errors.
- Exceeding API rate limits could lead to request throttling errors.
- Error messages:
- Errors thrown by the Whoz API are caught and rethrown with descriptive messages.
- If the node encounters an unknown resource or operation, it throws an error indicating the unsupported action.
- Resolution tips:
- Verify that the API credentials are correctly set up and have necessary permissions.
- Double-check filter inputs for correct formatting.
- Use smaller limits or add offsets to paginate large datasets.
- Enable "Continue On Fail" in the node settings to handle partial failures gracefully.
Links and References
- Whoz Talent Management Platform
- Refer to the Whoz API documentation for detailed billing item schema and available filters (not included here).