AvantGuard - WebhookSite icon

AvantGuard - WebhookSite

AvantGuard - WebhookSite

Actions100

Overview

This node operation updates an existing procedure task by its ID. It allows modifying various attributes of a task such as its name, description, completion status, assigned users, priority, due date, and position within the procedure. This is useful in workflow automation scenarios where tasks need to be dynamically updated based on external triggers or data changes, for example:

  • Marking a task as completed when a related event occurs.
  • Changing the assigned user or priority of a task based on new information.
  • Updating the due date or description to reflect changes in project requirements.

Properties

Name Meaning
Id The unique identifier of the procedure task to update (required).
Additional Body Fields Optional fields to update on the task:
- Name The name/title of the task.
- Description A detailed description of what the task entails.
- Completed Boolean flag indicating if the task is marked as completed.
- Procedure Id The ID of the procedure this task belongs to.
- Position The order/position of the task within the procedure.
- User Id The ID of the user assigned to the task.
- Due Date The due date for completing the task (string format).
- Priority The priority level of the task. Options: Unsure, Low, Normal, High, Urgent.
- Assigned Users JSON array of user IDs assigned to the task.

Output

The node outputs JSON data representing the updated procedure task object returned from the API after the update operation. This typically includes all the task's properties reflecting the latest state post-update.

If the node supports binary data output, it would represent any associated files or attachments related to the task, but no such binary output is indicated here.

Dependencies

  • Requires an API key credential for authenticating requests to the backend service managing procedure tasks.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on an OpenAPI-based client library internally to perform the HTTP PATCH or PUT request to update the task.

Troubleshooting

  • Missing or invalid Id: The update operation requires a valid task ID. Ensure the "Id" property is set and corresponds to an existing task.
  • Invalid field values: Providing incorrect data types (e.g., string instead of number) for fields like procedure_id or user_id may cause errors.
  • Authentication errors: Verify that the API key credential is correctly configured and has permissions to update procedure tasks.
  • Network or API errors: Check connectivity and API endpoint availability. Review error messages for HTTP status codes like 400 (bad request), 401 (unauthorized), or 404 (not found).
  • JSON parsing issues: For the "Assigned Users" field, ensure the JSON array is well-formed; otherwise, parsing errors may occur.

Links and References

Discussion