All integrations

Connect First AI Employee to Microsoft To Do.

Tasks2 routesRoute facts checked August 28, 2026

This page shows every cataloged route for this app and marks the most capable working path. The recommended route works through automation you configure and own.

You authorize and keep control of the provider account. No page view means an account is connected.

Private First AI Employee app in Zapier

New Request in First AI Employee runs Find or Create Task in Microsoft To Do. This is customer-owned automation, not a native or two-way sync. The private First AI Employee app is installed from the dashboard invitation and is not searchable in Zapier’s public directory.

Every available route

More than one route is shown when it adds a real capability or gives you a customer-owned alternative. Recommended means most capable today, not already connected.

Zapier

Private First AI Employee app in Zapier

Customer setup required

Recommended route

What it does

New Request in First AI Employee runs Find or Create Task in Microsoft To Do.

Before you start

Choose the task list that receives follow-up work.

What it does not do

This is customer-owned automation, not a native or two-way sync. The private First AI Employee app is installed from the dashboard invitation and is not searchable in Zapier’s public directory.

Set it up
  1. Open Integrations in your First AI Employee dashboard and use the current private-app invitation shown there.
  2. Create a Zap with New Request from First AI Employee, then choose Microsoft To Do and Find or Create Task.
  3. Authorize your own Microsoft To Do account and complete this account-specific requirement: Choose the task list that receives follow-up work.
  4. Map Event ID and the caller fields you actually need, test the downstream record in the provider, then turn on the Zap.
Provider documentation (opens in a new tab)

n8n Cloud

Downloadable n8n Cloud workflow starter

Customer setup required

What it does

A completed call runs Create task in Microsoft To Do after you configure and enable the destination node.

Before you start

Microsoft OAuth2. Authorize Microsoft and choose the task list.

What it does not do

This route receives completed calls only. The synthetic dashboard test stops before the destination, so it proves transport but not the provider write. Event-ID replay memory is bounded best effort, and one n8n webhook URL is stored per tenant.

Set it up
  1. Download the app-specific starter from Integrations in your First AI Employee dashboard and import it into n8n Cloud.
  2. Authorize Microsoft To Do, choose the customer-owned resource, and complete this requirement: Authorize Microsoft and choose the task list.
  3. Configure and enable the destination node, then activate the workflow.
  4. Copy the production /webhook/ URL into the dashboard automation connection. Test URLs and self-hosted n8n hosts are rejected.
  5. Send the dashboard transport test, then run a real non-production completed call and confirm the destination record yourself.
Provider documentation (opens in a new tab)

Set it up: Private First AI Employee app in Zapier

Choose the task list that receives follow-up work.

01

Open Integrations in your First AI Employee dashboard and use the current private-app invitation shown there.

02

Create a Zap with New Request from First AI Employee, then choose Microsoft To Do and Find or Create Task.

03

Authorize your own Microsoft To Do account and complete this account-specific requirement: Choose the task list that receives follow-up work.

04

Map Event ID and the caller fields you actually need, test the downstream record in the provider, then turn on the Zap.

Verify the complete result

Send one synthetic New Request sample, then confirm the expected Microsoft To Do record exists exactly once before activation.

Account ownership and data boundaries

The route sends only the event fields needed for the action you configure. Provider credentials stay in the approved connection or are sealed by First AI Employee where the guide explicitly says so.

  • Your provider and automation accounts remain yours.
  • A successful transport test is not the same as a verified provider write.
  • The pages never claim a native or two-way sync unless that exact capability exists.

Ready to connect it?

Use the dashboard to authorize your account, select the customer-owned destination, and test the complete downstream result.

Open Integrations in your dashboardBrowse all app guides