Task Completed Event

The Task Completed event is triggered whenever a task is marked as completed in the WeGoDoo application. When this event occurs, a webhook will send the following JSON payload to the configured endpoint:

JSON Payload Example

{

  "event_type": "task_completed",

  "timestamp": "2024-11-27T12:11:11",

  "data": {

    "task_id": "2023101",

    "list_id": "998877",

    "list_name": "Weekly Objectives",

    "task_name": "Submit Quarterly Budget Report",

    "note": "Ensure all projections are accurate and updated",

    "due_date": "2024-11-30",

    "mark_as_important": true,

    "created_by": {

      "user_id": "john.doe@example.com",

      "username": "John Doe"

    },

    "completed_by": {

      "user_id": "jane.smith@example.com",

      "username": "Jane Smith"

    },

    "assigned_to": {

      "user_id": "alice.walker@example.com",

      "username": "Alice Walker"

    },

    "verify_by": {

      "user_id": "michael.brown@example.com",

      "username": "Michael Brown"

    }

  }

}

Field Descriptions

• event_type: The type of event that triggered the webhook (task_completed in this case).
• timestamp: The time the event occurred in ISO 8601 format.
• data: Contains detailed information about the completed task:
  
  • task_id: Unique identifier of the task.
  • list_id: Unique identifier of the list containing the task.
  • list_name: Name of the list containing the task.
  • task_name: Name of the completed task.
  • note: Additional notes or context provided for the task.
  • due_date: The due date for the task in ISO 8601 format.
  • mark_as_important: Boolean flag indicating if the task is marked as important.
  • created_by: Information about the user who originally created the task:
    
    • user_id: Email ID of the task creator.
    • username: Name of the task creator.
  • completed_by: Information about the user who completed the task:
    
    • user_id: Email ID of the user who marked the task as completed.
    • username: Name of the user who marked the task as completed.
  • assigned_to: Information about the user to whom the task was assigned:
    
    • user_id: Email ID of the assigned user.
    • username: Name of the assigned user.
  • verify_by: Information about the user responsible for verifying the task:
    
    • user_id: Email ID of the verifier.
    • username: Name of the verifier.

• Related Articles

• Task Updated Event

  The Task Updated event is triggered whenever a task is updated in the WeGoDoo application. When this event occurs, a webhook will send the following JSON payload to the configured endpoint: JSON Payload Example { "event_type": "task_updated", ...

• Task Created Event

  The Task Created event is triggered whenever a new task is created in the WeGoDoo application. When this event occurs, a webhook will send the following JSON payload to the configured endpoint: JSON Payload Example { "event_type": "task_created", ...

• Task Deleted Event

  The Task Deleted event is triggered whenever a task is deleted in the WeGoDoo application. When this event occurs, a webhook will send the following JSON payload to the configured endpoint: JSON Payload Example { "event_type": "task_deleted", ...

• Task Verified Event

  The Task Verified event is triggered whenever a task is verified in the WeGoDoo application. When this event occurs, a webhook will send the following JSON payload to the configured endpoint: JSON Payload Example { "event_type": "task_verified", ...

• Task Comment Event

  The Task Comment event is triggered whenever a new comment is added to a task in the WeGoDoo application. When this event occurs, a webhook will send the following JSON payload to the configured endpoint: JSON Payload Example { "event_type": ...