Actions25
Overview
This node integrates with the Whoz talent management platform to create new tasks within a specified workspace and dossier. It is useful for automating task creation workflows related to project or talent management, such as assigning work items, setting deadlines, and managing task priorities. For example, you can automatically create a task when a new project milestone is reached or assign tasks to team members based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Name | The name/title of the task to be created. |
| Dossier ID | Identifier of the associated dossier (opportunity/deal) under which the task will be created. |
| Workspace ID | Identifier of the workspace where the task belongs. |
| Additional Fields | Optional extra fields to provide more details about the task: - External ID: Identifier from an external system. - Description: Detailed description of the task. - Type: Task type (Request, Assignment, Position). - Priority: Task priority level (Low, Medium, High, Urgent). - Start Date, End Date, Due Date: Relevant dates for the task. - Assignee IDs / Assignee External IDs: Comma-separated lists of assignees. - Owner ID / Owner External ID: Identifiers for the task owner. - Project ID / Project External ID: Associated project identifiers. - Tags: Comma-separated list of tags for categorization. |
| Budget & Workload | Optional budget and workload-related fields: - Budgeted Days: Number of days budgeted. - Budgeted Revenue Value & Currency. - Budgeted Cost Value & Currency. - Target Daily Rate Value & Currency. |
| Requirements | Optional requirements for the task: - Expected Skills: Comma-separated skill names. - Expected Qualifications: Comma-separated qualification names. - Required Experience Years: Minimum years of experience. - Location: Physical location or work site. - Remote Work Allowed: Boolean indicating if remote work is permitted. |
Output
The node outputs a JSON object representing the newly created task as returned by the Whoz API. This includes all task details such as its unique identifier, name, associated dossier and workspace IDs, additional metadata, budget/workload information, and requirements if provided. The output does not include binary data.
Dependencies
- Requires an active connection to the Whoz talent management platform via an OAuth2 API credential.
- The node uses the Whoz API endpoints, switching between sandbox and production environments based on credential configuration.
- Proper API authentication credentials must be configured in n8n for this node to function.
Troubleshooting
- Missing required fields: The node validates that "Name", "Dossier ID", and "Workspace ID" are provided. Omitting these will cause errors.
- API errors: Errors returned from the Whoz API (e.g., invalid IDs, permission issues) will be surfaced. Check that all referenced IDs exist and that the API key has sufficient permissions.
- Invalid date formats: Dates should be provided in ISO 8601 format; incorrect formatting may cause request failures.
- Comma-separated lists: Assignee IDs, external IDs, and tags must be properly comma-separated without trailing commas.
- If the node fails and "Continue On Fail" is disabled, execution will stop immediately on error.
Links and References
- Whoz Talent Management Platform
- Whoz API Documentation (assumed, check actual docs for details)
- n8n OAuth2 Credential Setup Guide (for configuring API access)