Platform · Make

Two Make.com scenarios, built for the jobs Zapier can't reach.

Make earns its place when a workflow needs branching logic, data staging, or a multi-step API call that a linear tool can't express cleanly. Below are two scenarios: a Xero-to-Asana reporting automation with a two-branch router, and an AI-powered Gmail attachment processor.

Honest framing: these are self-directed practice builds made to demonstrate platform fluency, not paid client engagements. Every screenshot below is from the real Make scenario editor — the actual module configuration, not a mockup.

2complete scenarios, each built and tested end to end

13modules in the Xero → Asana scenario, including a parallel router

AIused to analyze attachments and generate descriptive filenames

1Xero to Asana — Account Transactions Report

The client needed a General Ledger Detail report from Xero attached to a completed Asana task. Xero's API doesn't expose that exact report, so this scenario pulls Account Transactions data for the prior calendar year and reformats it into a CSV that mirrors the manual export.

Make.com scenario canvas: Asana watch completed tasks trigger, Xero API call, router splitting into two branches — an iterator writing rows to Google Sheets, and a sleep-then-read branch that aggregates the rows into a CSV, uploads it as an Asana attachment, and clears the staging sheet — Asana trigger → Xero API call → router → parallel staging/formatting branches → CSV attached back to Asana.

Trigger — a task is marked complete in the target Asana project.
Xero API call — pulls Account Transactions data scoped to Jan 1–Dec 31 of the prior year.
Router, branch 1 — iterates each transaction row and writes it into a Google Sheet as staging.
Router, branch 2 — waits for staging to finish, reads the rows back, and aggregates them into a CSV-formatted text block.
Delivery — the CSV is uploaded as an attachment to the completed Asana task, then the staging sheet is cleared for the next run.

Why the data passes through Google Sheets: Xero's API returns nested JSON, not a ready CSV. Staging each row in Sheets first keeps the formatting logic simple, makes the data easy to inspect mid-run, and gives the scenario a clean place to reset state between runs.

2Gmail Attachment AI Processing

Watches Gmail for incoming attachments, uses AI to read the content and generate a descriptive filename, stores the renamed file in Google Drive, logs the activity, and sends a completion notification — replacing manual attachment triage entirely.

Make.com scenario canvas: Gmail watch emails trigger, list attachments, upload file to analyze, AI generate response, AI generate new file name, Google Drive upload attachment, Google Sheets save logs, Gmail send notification — Gmail intake → AI analysis → AI-generated filename → Drive storage → Sheets log → email notification.

Trigger — new email detected in the watched Gmail inbox.
Retrieve — lists the attachments and media on the incoming message.
AI analysis — uploads the attachment for review, generates a content summary, then a descriptive filename from that summary.
Store & log — uploads the renamed file to Google Drive and logs the timestamp, original filename, new filename, and file type in Google Sheets.
Notify — sends an email confirming the attachment has been processed.

Want this for your business?

If the workflow needs branching, staging, or a multi-step API call, Make handles it cleanly.

We map your actual process on a free call and figure out what's worth automating first.

Book a free call →