VictoriaOS icon

VictoriaOS

Interactúa con la API de VictoriaOS - Gestión de tareas, webhooks y más

Overview

This node integrates with the VictoriaOS API to manage tasks, webhooks, and user information. It supports operations such as listing, retrieving, creating, updating, and deleting tasks and webhooks, as well as fetching authenticated user details. This node is useful for automating task management workflows, handling webhook notifications, and accessing user subscription and usage data within VictoriaOS.

Use Case Examples

  1. List tasks with optional filters like status, project ID, importance, urgency, limit, and offset.
  2. Create a new task with a title and additional optional fields such as description, status, importance, urgency, due date, scheduled date, project ID, and estimated minutes.
  3. Update an existing task by its ID with new values for title, description, status, importance, urgency, due date, scheduled date, project ID, and estimated minutes.
  4. Delete a task permanently by its ID from VictoriaOS system management workflows to keep task lists clean and relevant.

Properties

Name Meaning
Recurso Selects the resource to interact with in VictoriaOS: tasks, webhooks, or user information.
Operación Selects the operation to perform on the chosen resource, such as listing, retrieving, creating, updating, or deleting tasks or webhooks, or getting user info.
Filtros Filters to narrow down task listings by status, project ID, importance, urgency, limit, and offset for pagination.
ID de la Tarea Unique identifier of the task for operations that require a specific task.
Título Title of the task when creating a new task.
Campos Adicionales Additional optional fields for creating a task, including description, status, importance, urgency, due date, scheduled date, project ID, and estimated minutes.
Campos a Actualizar Fields to update for an existing task, similar to creation fields but optional.
Opciones Options for listing webhooks, including limit and offset for pagination.
ID del Webhook Unique identifier of the webhook for specific webhook operations.
URL del Webhook URL where webhook notifications will be sent when creating or updating a webhook.
Eventos Events that trigger the webhook, such as task created, updated, completed, or deleted.
Campos Adicionales Webhook Additional optional fields for webhook creation, including description and active status.
Campos a Actualizar Webhook Fields to update for an existing webhook, including URL, events, description, and active status.

Output

JSON

  • id - Unique identifier of the created or retrieved resource (task, webhook, or user info).
  • title - Title of the task (if applicable).
  • description - Detailed description of the task or webhook.
  • status - Current status of the task.
  • importance - Importance level of the task.
  • is_urgent - Urgency flag of the task.
  • due_date - Due date for task completion.
  • scheduled_date - Scheduled date to work on the task.
  • project_id - Project ID associated with the task.
  • estimated_minutes - Estimated time to complete the task in minutes.
  • url - Webhook URL for notifications.
  • events - Events that trigger the webhook.
  • active - Active status of the webhook.
  • user - Authenticated user information including ID and email.
  • plan - Subscription plan details of the user.
  • rate_limits - Rate limit information for the user.
  • usage_stats - Current usage statistics of the user.

Dependencies

  • An API key credential for VictoriaOS API authentication

Troubleshooting

  • Ensure the API key credential is correctly configured and has necessary permissions to access VictoriaOS API endpoints.
  • Verify that the resource and operation parameters are correctly set to avoid invalid API requests.
  • Check that required fields such as task ID, webhook ID, or URLs are provided when needed to prevent errors.
  • Handle API rate limits by respecting the limits returned in user information to avoid request throttling.
  • If the node returns error messages related to HTTP status codes, review the API documentation for the meaning and required corrective actions.

Links

Discussion