Connect First AI Employee to Wrike.

Tasks1 routeRoute 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.

Recommended route

Private First AI Employee app in Zapier

New Request in First AI Employee runs Create Task in Wrike. 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 Create Task in Wrike.

Before you start

Choose the destination folder or project.

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

Open Integrations in your First AI Employee dashboard and use the current private-app invitation shown there.
Create a Zap with New Request from First AI Employee, then choose Wrike and Create Task.
Authorize your own Wrike account and complete this account-specific requirement: Choose the destination folder or project.
Map Event ID and the caller fields you actually need, test the downstream record in the provider, then turn on the Zap.

Provider documentation

Set it up: Private First AI Employee app in Zapier

Choose the destination folder or project.

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

Create a Zap with New Request from First AI Employee, then choose Wrike and Create Task.

Authorize your own Wrike account and complete this account-specific requirement: Choose the destination folder or project.

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 Wrike 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 dashboard Browse all app guides