Why connect Ninety and Asana

Many teams run on EOS with Ninety to track commitments from Level 10 Meetings, but execute detailed project work in Asana. Without integration, team members spend time copying To-Dos between systems, updating status in both systems, and manually synchronizing due dates.

Zapier bridges this gap by automating the information flow between platforms. You can create workflows that keep commitments visible where work happens, ensure accountability translates into execution, and eliminate duplicate data entry.

Who should use this integration

This integration works best for teams and individual contributors who:

• Create To-Dos in Ninety during Level 10 Meetings and track detailed execution in Asana.
• Need accountability from EOS meetings to flow into day-to-day project management.
• Want team members to work primarily in Asana while keeping leadership visibility in Ninety.
• Use Asana for client projects or creative workflows that require more granular task management than Ninety provides.

Common workflows for Asana and Ninety with Zapier

1. Sync new To-Dos to Asana projects

• What it does: When you create a To-Do in Ninety during a meeting, it automatically appears as a task in your Asana project.
• Why it matters: Commitments made in meetings flow directly into your execution system. Team members see their Level 10 commitments alongside other project work without switching contexts or remembering to manually create tasks.
• Best for: Teams who want EOS commitments visible in Asana where detailed project work happens.
• What you'll need: One Zap per user that creates Asana tasks when To-Dos are created on a specific Ninety team.

2. Bring Asana tasks into Ninety as To-Dos

• What it does: When someone assigns you a task in Asana, it creates a corresponding To-Do in Ninety on your team.
• Why it matters: Important tasks from project work surface in Ninety, where leadership reviews accountability. Your team's Level 10 Meetings reflect both internally-set commitments and project-driven work.
• Best for: Teams who need visibility into Asana work during Ninety meetings without manually reporting status.
• What you'll need: One Zap per user, with a filter that syncs only tasks assigned to you (to prevent creating To-Dos for your entire team's Asana tasks).

3. Keep status synchronized between platforms

• What it does: When you mark a To-Do complete in Ninety, the corresponding Asana task updates automatically. When you complete an Asana task, the related To-Do in Ninety marks complete.
• Why it matters: One source of truth for completion status. You can update either system and trust that the other reflects current reality. No more "wait, did you finish that or just mark it done in Asana?"
• Best for: Teams who complete work in Asana but report progress in Ninety meetings.
• What you'll need: Two Zaps — one that updates Asana when Ninety To-Dos change, and one that updates Ninety when Asana tasks change.

4. Sync due date changes

• What it does: When you change a due date in either platform, the other platform updates to match.
• Why it matters: Schedules stay aligned without manual coordination. When project timelines shift in Asana, your Ninety commitments adjust automatically.
• Best for: Teams where project deadlines drive Level 10 commitments.
• What you'll need: Update Zaps that monitor due date changes in both directions (typically part of the status sync workflow above).

5. Two-way sync with automatic ID tracking

• What it does: Creates complete bidirectional synchronization — new items flow both directions, updates sync automatically, and completion status stays aligned. The workflow embeds unique IDs to match records across platforms.
• Why it matters: This is the most comprehensive approach. Once configured, you can create and update work in either system with confidence that the other platform reflects the current reality. Great for teams who need both platforms to be equally reliable.
• Best for: Teams committed to using both platforms long-term who want seamless integration.
• What you'll need: Four Zaps per user — two for creating items (one direction each) and two for updating items (one direction each). This is the workflow documented in our detailed step-by-step guide.

Important caveat: This workflow requires careful setup. The ID tracking system ensures updates modify the correct tasks rather than creating duplicates.

Prerequisites

Before building Asana-Ninety workflows, you'll need:

• A Zapier account (free plan works for basic automation; paid plans offer more tasks per month and advanced features).
• An active Ninety account with team member/managee permissions or higher that's assigned to one or more teams in the Directory.
• An Asana account (free or paid) with at least one project.

Each team member creates their own Zapier connection. You can't build Zaps that manage other users' To-Dos.

Tips for successful implementation

• Start with one user as a test. Have a single team member build the full workflow and validate it works correctly before rolling it out to the entire team. This catches configuration issues early and helps you document the process for others.
• Consider filters. When creating To-Dos from Asana tasks, always filter to only sync tasks assigned to you. Without this filter, every team member's Asana tasks become To-Dos in Ninety, creating noise and confusion.
• Test with real data. Zapier provides sample data during setup, but always test your Zaps with actual To-Dos and tasks before turning them on. Sample data doesn't always capture edge cases, such as missing due dates or special characters in titles.
• Document your setup. When team members configure their own Zaps, provide a checklist or template to ensure consistency. This makes troubleshooting easier when someone's workflow stops working correctly.