# Microsoft To Do integrations: task lists and tasks > Create a task list, create a task and create a checklist item in Microsoft To Do. **Canonical page:** https://tray.ai/connectors/microsoft-to-do-integrations/ **Categories:** Operations **Connects through:** HTTP Connector ## Overview Microsoft To Do is Microsoft's task list app, where people organize tasks into lists with due dates, reminders, checklists, and links back to source items. Tray.ai connects to Microsoft To Do through the HTTP Connector, so your workflows can call the Microsoft To Do API alongside the rest of your stack. ## Use cases ### Task lists Read, create, update, and delete task lists in Microsoft To Do from any Tray.ai workflow. The Microsoft To Do API covers calls such as list task lists and create a task list. - List task lists - Create a task list - Get a task list ### Tasks Read, create, update, and delete tasks in Microsoft To Do from any Tray.ai workflow. The Microsoft To Do API covers calls such as list tasks and create a task. - List tasks - Create a task - Get a task ### Checklist items Read and create checklist items in Microsoft To Do from any Tray.ai workflow. The Microsoft To Do API covers calls such as list checklist items and create a checklist item. - List checklist items - Create a checklist item ### Linked resources Read and create linked resources in Microsoft To Do from any Tray.ai workflow. The Microsoft To Do API covers calls such as list linked resources and create a linked resource. - List linked resources - Create a linked resource ## Challenges Tray.ai solves ### Keeping Microsoft To Do credentials out of logs A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots. **How Tray.ai helps:** Store Microsoft To Do credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output. ### Going from the Microsoft To Do API docs to a working call Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand. **How Tray.ai helps:** Paste a cURL example from the Microsoft To Do API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you. ### Handling files and non-JSON responses Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload. **How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads. ## Frequently asked questions ### Does Tray.ai connect to Microsoft To Do? Yes. Tray.ai connects to Microsoft To Do through the HTTP Connector, which calls the Microsoft To Do API directly. Any call the Microsoft To Do API documents can run as a step in a Tray.ai workflow. ### How does Tray.ai authenticate with Microsoft To Do? The Microsoft To Do API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request. ### Can I get a dedicated Microsoft To Do connector? Microsoft To Do runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Microsoft To Do connector from the Microsoft To Do API. ## Learn more - Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/ - Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/ - Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/ - Book a demo: https://tray.ai/contact/