Access Token

Refresh Token

Todoist

Comments

One of task_id or project_id arguments is required(only for the list method).

Labels

Projects

Sections

Specific date in YYYY-MM-DD format relative to user’s timezone.

Specific date and time in RFC3339 format in UTC.

2-letter code specifying language in case due_string is not written in English.

Human defined task due date (ex.: "next Monday", "Tomorrow"). Value is set using local (not UTC) time.

A positive (greater than zero) integer for the amount of duration_unit the task will take. If specified, you must define a duration_unit.

The unit of time that the duration field above represents. Must be either minute or day. If specified, duration must be defined as well.

The task's labels (a list of names that may represent either personal or shared labels).

Task priority from 1 (normal) to 4 (urgent).

Task project ID. If not set, task is put to user's Inbox.

Tasks

Salesforce

HubSpot

Zoho CRM

Microsoft Dynamics 365

Attio

Jira

Freshsales

Keap

Asana

SugarCRM

Github

Outreach

ActiveCampaign

Capsule CRM

Salesloft

Clickup

Zendesk

Zoho Books

Agile CRM

Teamleader

Copper

Trello Connector

Close

Freshdesk

Linear

Deel

Teamwork

HiBob

# Continuous Import of Tasks to Your App

This scenario enables your application to continuously sync Tasks from any external application to your app's API. It handles the initial import of Tasks and keeps them synchronized when a Task is created, updated, or deleted in the external application.

When receiving Tasks data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

1. **Initial Import**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page.
   - Integration.app transforms the output into a consistent format compatible with your API, allowing you to save the data efficiently.

2. **Continuous Sync**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.

Continuously Import Tasks to my App

Import Tasks and receive created/updated or deleted events

# Update Task

This scenario allows your application to update a Task in any external application in the same way. 
You will pass  ID of the Task you want to update and Task fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.

## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to update Task with and configure mapping to our default model

2. **Create Task API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured and ID. You can run it for any external application via the same request.
   - When called, Integration.app transforms your Task data into a format compatible with the selected external application.
   - It then makes an API call to update the Task in that specific application.


Update Task

# Delete Task

This scenario allows your application to delete a Task from any external application. 
You will pass ID of the Task you want to delete and Integration.app will handle the rest.

## How It Works

1. **Delete Task API call**:
   - Call Integration.app REST API or SDK with ID of the Task you want to delete and Integration.app will send the correct request to the external app.


Delete Task

# Create Task

This scenario allows your application to create a Task in any external application in the same way. 
You will pass Task fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.


## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to create Task with and configure mapping to our default model

2. **Create Task API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured. You can run it for any external application via the same request.
   - When called, Integration.app transforms your Task data into a format compatible with the selected external application.
   - It then makes an API call to create the Task in that specific application.


Create Task

# Realtime Full two-way Sync of Tasks

This scenario enables your application to fully sync Tasks between your app and any external application in both directions. It handles the initial import/export of Tasks and then sends events when a Task is created, updated, or deleted on any side, as close to real-time as possible.

Task fields will be mapped from your application's schema to the application-specific schema.

## How It Works

1. **Initial Sync**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page. Integration.app transforms the output into a consistent format compatible with your API, allowing you to save and match data efficiently.
   - Make another set of requests to create Tasks in external app, if needed.

2. **Continuous Sync from External App**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events from external applications.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.


2. **Continuous Sync from Your App**:
   - You will get a single webhook URI that you will use to send events about created, updated, or deleted Tasks to Integration.app.
   - Once send, Integration.app will map the webhook payload to the format supported by external application and send the correct request


Two-way realtime sync of Tasks

Bi-directional realtime sync of Tasks with records deduplication

# Get all Tasks

This scenario enables your application to get a complete list of Tasks from any external application to your app's API in the same way. 

When receiving Tasks data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

You will call a Integration.app REST API endpoint or SDK methods to retrieve a single page of Tasks along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Tasks page by page.


Get all Tasks

Imports all Tasks from any external application to your App.

# Task Unified API

This scenario contains the complete Tasks Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Tasks while also receiving notifications on creation, updates, and deletions of Tasks in external applications. 

Integration.app will automatically manage the mapping of data to the unified schema, eliminating any concerns about differences across external applications. Additionally, you’ll have the flexibility to customize mappings for specific applications or customers, ensuring compatibility with their unique configurations when needed.


Todoist API Integration Profile

Getting Started

Data Collections

API Operations

Integration Scenarios