# Float + Asana integration > Stop updating two systems by hand. tray.ai moves project and scheduling data between Float and Asana automatically. **Canonical page:** https://tray.ai/connectors/float-asana-integrations/ **Float connector:** https://tray.ai/connectors/float-integrations/ **Float documentation:** https://tray.ai/documentation/connectors/service/float **Asana connector:** https://tray.ai/connectors/asana-integrations/ **Asana documentation:** https://tray.ai/documentation/connectors/service/asana ## Overview Float is the resource management platform teams use to schedule work and track capacity. Asana is where tasks, timelines, and deliverables actually get managed. Together they cover the full span of project delivery — from planning who does what and when, to executing and tracking the work itself. Without an integration, you're stuck manually mirroring data across both tools, which means scheduling conflicts, capacity blind spots, and projects that drift out of step with reality. When Float and Asana run separately, resource managers and project leads are constantly playing catch-up. A new project created in Asana may never make it into Float for staffing, leaving people over-allocated or sitting idle. Meanwhile, schedule changes in Float — a team member going on leave, a project pushed back — don't automatically reach Asana task assignments or timelines. Connecting Float and Asana through tray.ai means every deadline shift, project milestone, or resource reallocation shows up in both platforms. Resource managers get an accurate picture of team capacity. Project managers always know who's assigned to what. And the whole delivery team works from one source of truth instead of two competing ones. ## Use cases ### Auto-Create Float Allocations When Asana Projects Are Launched When a new project is created in Asana and assigned to team members, tray.ai automatically generates corresponding resource allocations in Float. Capacity is reserved in Float the moment work is committed to in Asana, so double-booking stops before it starts and resource managers have immediate visibility into new demand. No more manually transcribing start dates, end dates, and assignees from one tool to the other. - Capacity is reserved in Float as soon as Asana projects go live - Eliminates manual data entry across both platforms - Prevents double-booking and resource conflicts from day one ### Sync Asana Project Deadlines to Float Schedule Blocks When due dates on Asana projects or milestones change, tray.ai automatically adjusts the corresponding allocation end dates in Float. Resource managers don't have to monitor Asana for every deadline change — Float stays accurate on its own. Teams always see an up-to-date picture of how long projects will run. - Float schedules stay accurate when Asana deadlines shift - Resource managers don't have to monitor Asana for date changes - Reduces the risk of scheduling gaps or unexpected capacity overruns ### Create Asana Tasks When Float Projects Are Added or Updated When a new project or phase is added in Float, tray.ai can create the corresponding projects or task sections in Asana, pre-populated with the right assignees, start dates, and due dates. This is especially useful for agencies and consultancies that plan resourcing in Float before standing up the full project structure in Asana. The integration closes the gap between resource planning and task execution. - Asana project scaffolding is created automatically from Float data - Assignees and timelines are pre-populated, saving setup time - Bridges resource planning and operational delivery ### Notify Teams in Real Time When Assignments Change in Either System When a resource is reassigned in Float or a task owner changes in Asana, tray.ai can trigger notifications to relevant stakeholders via Slack, email, or directly within Asana as task comments. Everyone stays informed without having to check both tools. Silent reassignments stop causing confusion. - Real-time alerts when assignments change in Float or Asana - Reduces miscommunication from silent reassignments - Stakeholders stay informed without switching between tools ### Track Capacity Utilization Against Asana Task Completion By combining Float's allocation data with Asana's task completion status, tray.ai can surface whether actual project progress lines up with scheduled resource investment. When Asana tasks close ahead of or behind schedule, tray.ai can update Float allocations accordingly, keeping capacity forecasts grounded in real delivery pace. This gives operations leaders a concrete basis for staffing decisions instead of gut feel. - Capacity forecasts reflect actual Asana delivery pace - Float allocations adjust automatically as Asana tasks close - Gives operations leaders a concrete view of team efficiency ### Automatically Archive Float Allocations When Asana Projects Are Completed When an Asana project is marked complete or moved to a completed section, tray.ai automatically closes or archives the related allocation blocks in Float. Stale allocations stop inflating utilization data, and capacity freed up by finished projects is immediately visible for future scheduling. - Stale allocations are removed as soon as Asana projects close - Available capacity surfaces immediately for future planning - Keeps Float utilization reporting clean and trustworthy ### Onboard New Team Members Across Float and Asana Simultaneously When a new employee or contractor is added to your workforce management system, tray.ai creates their user profile in both Float and Asana at the same time, applying the right team memberships, project access, and role settings in each tool. This eliminates the common onboarding gap where someone gets set up in one system but forgotten in the other. - New users are provisioned in both tools in a single automated workflow - Role and team settings are applied consistently across both platforms - New hires can contribute immediately without setup delays ## Templates ### New Asana Project → Create Float Allocation Automatically creates a resource allocation in Float whenever a new project is created in Asana, mapping project owner, team members, start date, and due date to the corresponding Float fields. Connectors used: Asana, Float ### Asana Deadline Change → Update Float Allocation End Date Monitors Asana for due date changes on projects or milestones and automatically updates the corresponding Float allocation end dates to match the new timeline. Connectors used: Asana, Float ### Float Project Added → Create Asana Project with Tasks When a new project is added in Float, this template automatically creates a corresponding project in Asana, generates default task sections, and assigns team members based on the Float allocation data. Connectors used: Float, Asana ### Asana Project Completed → Archive Float Allocation Automatically archives or closes the matching Float allocation when an Asana project is marked complete, keeping resource utilization data accurate and freeing up visible capacity. Connectors used: Asana, Float ### Float Reassignment → Update Asana Task Assignee and Notify When a resource is reassigned on a Float allocation, this template updates the corresponding task assignee in Asana and sends a notification to both the outgoing and incoming assignees. Connectors used: Float, Asana ### Weekly Float Capacity Report Enriched with Asana Task Status Generates a weekly summary report combining Float allocation data with current Asana task completion rates, giving leadership a unified view of team capacity versus actual delivery progress. Connectors used: Float, Asana ## Challenges Tray.ai solves ### Mapping Users Consistently Between Float and Asana Float and Asana each maintain their own user records with no shared identifier between them. Reliably matching a Float team member to their Asana counterpart gets tricky in organizations with contractors, shared emails, or inconsistent naming conventions. **How Tray.ai helps:** tray.ai lets you build a lookup step that matches Float people to Asana users by email, name, or a custom reference field stored in either system. You can also maintain a mapping table in a tray.ai data store that works as a persistent cross-reference, so user matching stays accurate even when display names differ between platforms. ### Handling Partial Allocations and Multi-Phase Projects Projects in Float are often split into phases or partial allocations across multiple team members, while Asana organizes work as tasks, sections, and milestones. There's no clean one-to-one structural match between Float allocations and Asana tasks, which makes automated syncing prone to incomplete or duplicated records. **How Tray.ai helps:** tray.ai's workflow logic lets you define custom mapping rules that translate Float phases into Asana sections, or Float allocation segments into individual Asana task groups. Conditional branches let you handle multi-phase projects with different logic per phase, so the right structure gets created in Asana regardless of how the Float allocation model is set up. ### Avoiding Duplicate Projects and Allocations from Bidirectional Syncing When changes can originate in either Float or Asana, a naive bidirectional sync can trigger circular updates — a change in Float updates Asana, which fires a webhook back to Float, creating an infinite loop or duplicate records. This is one of the most common failure modes in two-way integrations, and it's painful to untangle. **How Tray.ai helps:** tray.ai lets you implement idempotency checks and loop-prevention logic at every step. By storing the source of the last update in a tray.ai data store and checking it before processing each event, you can make sure automated sync updates don't get re-processed. Custom deduplication logic prevents duplicate projects or allocations from appearing during high-frequency sync windows. ### Keeping Custom Fields in Sync Across Both Platforms Many teams extend both Float and Asana with custom fields — client names, billing codes, project types, priority flags — that matter for reporting and workflow routing. These fields are platform-specific with no automatic correspondence, so important metadata gets lost when records are created or updated via automation. **How Tray.ai helps:** tray.ai's data transformation capabilities let you map custom fields from Float to their Asana equivalents explicitly, using field name lookups and value translation tables where needed. When custom field schemas change in either system, you update the mapping logic centrally in tray.ai without rebuilding the entire workflow. ### Managing API Rate Limits During Bulk Sync Operations Organizations with large teams or high project volumes can trigger bulk sync operations — a quarterly resource planning cycle, for example — that fire a high volume of API calls to both Float and Asana in a short window. Both APIs have rate limits, and hitting them mid-sync means partial updates and inconsistent data across both platforms. **How Tray.ai helps:** tray.ai handles API rate limiting through built-in retry logic, configurable request throttling, and error handling that catches rate-limit responses and queues retries with appropriate backoff intervals. For large bulk operations, tray.ai batches requests and spreads them across time windows to stay within API limits, so even large-scale syncs complete without corrupting data in either system. ## 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/