Actions32
- Assignment Actions
- Client Actions
- Project Actions
- Report Actions
- Task Actions
- Time Actions
- Timecard Actions
- Webhook Actions
Overview
This node integrates with the Everhour API to manage tasks within projects. Specifically, the Task Create operation allows users to create a new task inside a specified project. This is useful for automating task management workflows, such as adding tasks dynamically based on external triggers or data sources.
Practical examples include:
- Automatically creating tasks in Everhour when new issues are created in a bug tracker.
- Adding tasks to projects based on form submissions or customer requests.
- Integrating task creation into broader project management automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Project ID | The identifier of the project where the new task will be created. |
| Task Name | The name/title of the task to be created. |
| Estimate (Seconds) | Optional time estimate for the task, expressed in seconds. |
Output
The output is a JSON object representing the newly created task as returned by the Everhour API. It typically includes details such as the task's unique ID, name, associated projects, and any estimates set.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"id": "string",
"name": "string",
"projects": ["projectId"],
"estimate": {
"total": 0
},
// ... other task properties from Everhour API
}
Dependencies
- Requires an API key credential configured in n8n to authenticate with the Everhour API.
- The node uses the Everhour API base URL from the credential configuration.
- Network access to the Everhour API endpoint is necessary.
Troubleshooting
- Authentication errors: Ensure that the API key credential is correctly set up and has sufficient permissions.
- Invalid Project ID: If the project ID does not exist or is incorrect, the API will return an error. Verify the project ID before running the node.
- Missing required fields: Both Project ID and Task Name are mandatory. Omitting these will cause the node to fail.
- Estimate format: The estimate must be a number representing seconds. Providing invalid types may cause errors.
Common error messages:
"Unauthorized": Check API credentials."Project not found": Verify the project ID."Validation failed": Check that all required parameters are provided and valid.