Xero to Asana Transaction Export Automation
Make.comBusiness operationsUse an Asana task event to retrieve Xero transactions, stage rows in Sheets, and upload an aggregated attachment back to Asana.
- Platform
- Make.com
- Focus
- Business operations
- Evidence available
- Original screenshot
Project overview
This Make.com scenario bridges a completed-task event in Asana with a Xero API operation, temporary tabular staging and an attachment handoff. The scenario title identifies an intended CSV export, while the actual formatting settings are not visible.
Business problem
Accounting exports and the tasks requesting them often live in separate tools, requiring manual retrieval, file preparation and attachment handling.
Automation solution
Watch completed Asana tasks, call Xero, split the work into an iteration/write branch and a delayed read/aggregate/upload/clear branch using Google Sheets as staging.
Simplified process summary. Explore the architecture below for branches and decision logic.
Workflow evidence
Original image, preserved in full. Enlarge and zoom to read individual nodes.
Workflow architecture
Trigger & input
Asana Watch Completed Tasks is the first visible module. It connects directly to Xero Make an API Call, then a Router.
Processing & output
- Asana Watch Completed Tasks initiates the scenario and Xero Make an API Call retrieves the selected accounting data. The Xero endpoint, account and transaction selection are hidden.
- The Router’s first branch contains an Iterator followed by Google Sheets Add a Row.
- The second branch contains Tools Sleep, Google Sheets Get Range Values and Tools Text aggregator.
- Asana Upload an Attachment follows aggregation, then Google Sheets Clear Values from a Range. The scenario title says “Upload CSV to Asana”; delimiter, headers and final file contents are not shown.
Conditional logic
A Router separates row iteration from delayed aggregation and upload. Sleep is visible on the second branch; its duration and any branch filters are not exposed. The screenshot cannot establish concurrency safety or that all expected rows were collected before upload.
Key features
- Completed-task entry from Asana
- Xero API integration
- Iterator-based spreadsheet staging
- Delayed aggregation into an attachment
- Asana upload and subsequent staging-range clearing
Technical challenges
The visible design must coordinate writes with a later read and clear operation. Sleep and two routes are present, but timing configuration, simultaneous-run isolation, empty data and safe retry behavior are not documented. Green module markers alone cannot validate the exported file’s completeness.
Business value
Intended to bring an accounting export back into the task where it is needed and reduce manual file handoffs. No accuracy, time-saving or deployment results are claimed.
Project status
Testing & limitations
Test execution shown
The original canvas shows green completion markers on displayed modules, including attachment upload and range clearing. This is a captured test indication, not independent verification of CSV contents, accounting accuracy or production reliability.
Source: Kyle’s original workflow screenshot and project brief. The visible canvas has been reviewed; exported configuration, output contents and production run history have not been independently verified.
Limitations & next steps
What needs verification: resolve these open questions before treating this design as a verified implementation.
- Asana task selection and Xero API endpoint/parameters
- Iterator mappings, spreadsheet range and aggregation format
- Sleep duration, overlapping runs and safe clearing/retry rules
- Uploaded file contents and production verification