Skip to main content

Google Tasks API Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Google Tasks API location.
google_tasks_api.png

Google Tasks API

  1. Click the + icon on the Nexset that will be sent to the Google Tasks API destination, and select the Send to Destination option from the menu.

  2. Select the Google Tasks API connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Google Tasks API, and click Next; or, create a new Google Tasks API credential for use in this flow.

  3. In Nexla, Google Tasks API destinations can be created using pre-built endpoint templates, which expedite destination setup for common Google Tasks API endpoints. Each template is designed specifically for the corresponding Google Tasks API endpoint, making destination setup easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Google Tasks API destinations can also be configured manually, allowing you to send data to Google Tasks API endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Google Tasks API endpoints. Each template is designed specifically for the corresponding Google Tasks API endpoint, making destination setup easy and efficient.

Endpoint Settings​

  • Select the endpoint to which this destination will send data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your destination for this endpoint.

    Insert Task

    Creates a new task on a specified Google Tasks task list. Use this endpoint to programmatically add tasks from external data sources such as CRM records, support tickets, or form submissions.

    The request body should include at minimum a title field. Optional fields include notes, due (RFC 3339 timestamp), and status (needsAction or completed). The Google Tasks API does not support batch task creation — each task requires a separate API call.

    Update Task

    Replaces the full content of a specified task on a Google Tasks task list. Use this endpoint to overwrite all task fields with new data from an external source.

    This endpoint performs a full replacement of the task resource. All fields must be provided in the request body, as omitted fields will be cleared. Use Patch Task List if you need partial update semantics.

    Patch Task List

    Updates the authenticated user's specified task list using patch semantics, applying only the fields provided in the request. Use this endpoint to rename a task list or update its properties without overwriting unspecified fields.

    Only fields included in the request body will be updated — unspecified fields retain their current values. This is the recommended approach for updating task list titles without affecting other properties.

    Create Task List

    Creates a new task list and adds it to the authenticated user's Google Tasks account. Use this endpoint to programmatically provision task lists for new projects, users, or workflow categories.

    The newly created task list's ID is returned in the API response. Capture this ID via the Response Webhook feature if you need to reference the new list in subsequent operations.

    Move Task

    Moves a specified task to another position in the task list or to a different task list entirely. Use this endpoint to reorganize tasks programmatically as part of workflow automation.

    • Sends a POST request to the Google Tasks API move endpoint with the target position or list in the request parameters.
    • Configure the following parameters: Tasklist — the source task list ID; Task — the task ID to move; Parent — optional ID of the parent task (for subtask nesting); Previous — optional ID of the preceding task; Destinationtasklist — optional ID of the destination task list if moving to a different list.

    Moving a task to a different task list creates a new task in the destination list and deletes the original. The task ID will change after a cross-list move.

    Clear Completed Tasks

    Clears all completed tasks from a specified task list by marking them as hidden. Use this endpoint in scheduled cleanup workflows to maintain a clean, active task list.

    • Sends a POST request to the Google Tasks API clear endpoint for the specified task list.
    • Configure the following parameter: Tasklist — the unique identifier of the task list from which to clear completed tasks.

    Cleared tasks are marked as hidden and removed from the default list view, but they are not permanently deleted. This operation cannot be undone programmatically — cleared tasks cannot be restored via the API.

    Delete Task

    Permanently deletes a specified task from a Google Tasks task list. Use this endpoint to remove tasks that are no longer relevant as part of automated data lifecycle workflows.

    Task deletion is permanent and cannot be undone. Retrieve task IDs using the List Tasks in a List source endpoint before deletion.

    Delete Task List

    Permanently deletes a specified task list and all tasks within it from the authenticated user's Google Tasks account. Use this endpoint to remove obsolete task lists in automated cleanup workflows.

    Deleting a task list permanently removes all tasks within it. This action cannot be undone. Retrieve task list IDs using the List Task Lists source endpoint before deletion.

    Set Hotels Live on Google

    Activates hotels to appear live on Google travel properties for a Travel Partner account. Use this endpoint to control the live status of hotel listings programmatically.

    • Sends a request to the Google Travel Partner API to set the live status for specified hotel properties.
    • Configure the following parameters: Account Id — the Travel Partner account identifier; Live on Google — flag to set the live status; Partner Hotel IDs — the list of hotel IDs to activate or deactivate.

    This endpoint is part of the Google Travel Partner API and requires Travel Partner API access enabled in your Google Cloud project.

    Query Free Booking Links Report Views

    Queries free booking links report views with optional filtering and aggregation for a Google Travel Partner account. Use this endpoint to trigger report generation or submit report query parameters.

    • Sends a POST or query request to the Travel Partner API free booking links report endpoint.
    • Configure the following parameters: Account Name — the Travel Partner account resource name; Aggregate By, Filter, Page Size, Page Token — optional query controls.

    This endpoint is part of the Google Travel Partner API. Use the corresponding source endpoint to retrieve the results after submission.

    Query Participation Report Views

    Queries participation report views with optional filtering and aggregation for a Google Travel Partner account. Use this endpoint to submit participation report query parameters.

    • Sends a request to the Travel Partner API participation report endpoint with filtering and aggregation parameters.
    • Configure the following parameters: Account Name — the Travel Partner account resource name; Aggregate By, Filter, Page Size, Page Token — optional query controls.

    This endpoint is part of the Google Travel Partner API and requires Travel Partner API access enabled in your Google Cloud project.

    Query Property Performance Report Views

    Queries property performance report views with optional filtering and aggregation for a Google Travel Partner account. Use this endpoint to submit property performance report query parameters.

    • Sends a request to the Travel Partner API property performance report endpoint with filtering and aggregation parameters.
    • Configure the following parameters: Account Name — the Travel Partner account resource name; Aggregate By, Filter, Page Size, Page Token — optional query controls.

    This endpoint is part of the Google Travel Partner API. Combine with the Participation Report endpoint for a comprehensive hotel listing health assessment.

    Create Reconciliation Report

    Creates a new reconciliation report for a specified Google Travel Partner account with provided file contents. Use this endpoint to submit hotel booking reconciliation data to Google.

    • Sends a POST request to the Travel Partner API reconciliation reports endpoint with the report file data in the request body.
    • Configure the following parameters: Account — the resource name of the Travel Partner account; File Contents — the report data; File Name — the name of the report file; Report Name — the resource name for the new report.

    This endpoint is part of the Google Travel Partner API. Reconciliation reports are used to match Google's booking data with your own records for billing and performance verification.

    Update Brand

    Updates Travel Partner brand information including display names, icons, and approval states. Use this endpoint to manage hotel brand configurations for a Google Travel Partner account.

    • Sends a PATCH or PUT request to the Travel Partner API brands endpoint with the updated brand data.
    • Configure the following parameters: Brand Name — the resource name of the brand to update; Update Mask — the list of fields to update; additional optional fields for display names, icons, and states.

    This endpoint is part of the Google Travel Partner API. Only fields specified in the Update Mask will be modified. Display name and icon changes require Google approval before they are activated on travel surfaces.

    Create Account Link v2

    Creates a new account link between a Google Travel Partner account and an external partner account. Use this endpoint to establish programmatic linkages between Travel Partner accounts and partner systems.

    • Sends a POST request to the Travel Partner API account links endpoint with the link configuration in the request body.
    • Configure the following parameter: Account — the resource name of the Travel Partner account under which the link will be created.

    This endpoint is part of the Google Travel Partner API. The request body must include the external account reference and the desired link type. This is the v2 version of the Create Account Link endpoint.

Configure Manually​

Google Tasks API destinations can also be configured manually, allowing you to send data to Google Tasks API endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.

First, select the API method that will be used for calls to the Google Tasks API from the Method pulldown menu. Common methods for Google Tasks API destination operations include:

  • POST: For creating new tasks or task lists.
  • PATCH: For partially updating existing tasks or task lists (recommended for updating specific fields without overwriting others).
  • PUT: For replacing an existing task or task list with new data.
  • DELETE: For removing tasks or task lists.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Google Tasks API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call.

    The Google Tasks API accepts and returns data in JSON format. Select JSON as the content format to ensure compatibility with the API.

API Endpoint URL​

  1. Enter the URL of the Google Tasks API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL including the protocol (https://) and any required path parameters.

    Common endpoint patterns for destination operations include:

    • Create a new task: https://tasks.googleapis.com/tasks/v1/lists/{'{tasklist}'}/tasks (POST)
    • Update an existing task: https://tasks.googleapis.com/tasks/v1/lists/{'{tasklist}'}/tasks/{'{task}'} (PATCH or PUT)
    • Create a new task list: https://tasks.googleapis.com/tasks/v1/users/@me/lists (POST)
    • Delete a task: https://tasks.googleapis.com/tasks/v1/lists/{'{tasklist}'}/tasks/{'{task}'} (DELETE)

    Replace {'{tasklist}'} with the ID of the target task list, and {'{task}'} with the ID of the specific task to update or delete.

For create (POST) operations, only the base endpoint URL is required. For update (PATCH/PUT) or delete (DELETE) operations, include the specific resource ID at the end of the URL. Task and task list IDs can be retrieved from a Google Tasks API data source configured in Nexla. For complete API reference documentation, see the Google Tasks API REST reference.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include any headers already present in the credentials. Authorization headers are handled automatically by Nexla based on your Google Tasks API credential configuration.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Google Tasks API destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

    The Google Tasks API does not have a native batch endpoint for task operations — each task must be created or updated individually. When batching is enabled, Nexla sends the batched records to the configured API endpoint using the specified grouping algorithm. For individual task operations, consider disabling batching or setting a batch size of 1 to ensure each task is processed as a separate API call.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the Google Tasks API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call, such as the newly created task ID or updated task details.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Google Tasks API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing​

After all endpoint settings have been configured, Nexla can send a test payload to the Google Tasks API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Google Tasks API using the current settings.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the Google Tasks API, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to the Google Tasks API until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.