Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node operation creates a new Procedure Task within a specified procedure management system. It allows users to define various attributes of a task such as its name, description, assigned user(s), due date, priority, and position within the procedure. This is useful in workflow automation scenarios where tasks need to be programmatically created and managed as part of larger procedures or projects.
Practical examples include:
- Automatically creating follow-up tasks when a new procedure is initiated.
- Assigning tasks to specific users based on dynamic inputs.
- Setting priorities and due dates for tasks generated from external triggers.
Properties
| Name | Meaning |
|---|---|
| Additional Body Fields | Optional fields to customize the task creation request. Includes: |
| - Name | The name/title of the task. |
| - Description | A detailed description explaining the task. |
| - Procedure Id | Numeric ID of the procedure this task belongs to. |
| - Position | Numeric position/order of the task within the procedure. |
| - User Id | Numeric ID of the user assigned to the task. |
| - Due Date | Due date string specifying when the task should be completed. |
| - Priority | Priority level of the task. Options: Unsure, Low, Normal, High, Urgent |
| - Assigned Users | JSON array of user IDs assigned to the task (can assign multiple users). |
Output
The node outputs JSON data representing the newly created Procedure Task. This JSON typically includes all the properties sent in the request along with any additional metadata returned by the API, such as unique task identifiers or timestamps.
If the node supports binary data output, it would represent attachments or files related to the task, but no 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 for making HTTP requests to the service.
Troubleshooting
- Missing or invalid API credentials: Ensure that the API key or authentication token is correctly set up in the node credentials.
- Invalid procedure ID or user ID: Verify that numeric IDs provided correspond to existing procedures and users in the system.
- Malformed JSON in Assigned Users: The "Assigned Users" field expects a valid JSON array; invalid JSON will cause errors.
- Priority value not recognized: Use one of the predefined priority options; otherwise, the API may reject the request.
- Network or API errors: Check connectivity and API endpoint availability; ensure the base URL is correct.
Common error messages might include authentication failures, validation errors for missing required fields, or server errors if the API is unreachable.
Links and References
- No direct links available from the source code.
- Refer to the API documentation of the procedure management system for details on task creation endpoints and field requirements.