awork

Overview

This node integrates with the awork API to automate task management within projects. Specifically, for the "Project Task" resource and the "Set Custom Field" operation, it allows users to update a custom field on a specified project task by providing the task ID, the custom field definition ID, and the new text value for that field.

Common scenarios include:

• Automatically updating task metadata based on external triggers or workflow conditions.
• Synchronizing custom task fields with data from other systems.
• Enriching tasks with additional information dynamically during workflow execution.

For example, you might use this node to set a priority label or status note on a task after receiving input from another system or user action.

Properties

Output

The node outputs JSON data representing the updated task object as returned by the awork API after setting the custom field. This typically includes the task's current state with the updated custom field values.

If the node supports binary data output (not indicated here), it would represent any file attachments or related binary content associated with the task update.

Dependencies

• Requires an active connection to the awork API via an API key credential configured in n8n.
• The node uses the base URL https://api.awork.com and expects JSON-formatted requests and responses.
• Proper permissions on the awork account are necessary to modify project tasks and their custom fields.

Troubleshooting

• Invalid Task ID: If the provided task ID does not exist or is incorrect, the node will fail to find the task. Verify the task ID is correct and accessible.
• Invalid Custom Field Definition ID: Using an incorrect or non-existent custom field definition ID will cause errors. Ensure the ID corresponds to a valid custom field for the project.
• Insufficient Permissions: The API key used must have rights to edit tasks and custom fields; otherwise, permission errors will occur.
• Empty Text Value: Providing an empty string may clear the custom field or cause validation errors depending on the API rules.
• API Rate Limits or Connectivity Issues: Network problems or hitting API rate limits can cause failures; check connectivity and API usage quotas.

Links and References

• awork API Documentation
• n8n Documentation on Creating Custom Nodes