Automate Vendor Assignments from CSV with Make.com IntegrationAutomate Vendor Assignments from CSV with Make.com Integration
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
A CSV file doesn't look like much. A few hundred rows, some columns. Someone on the finance team sends it every morning and expects vendors to be assigned by afternoon.
What's actually required to make that happen automatically is more interesting.
I built a Make.com scenario that picks up a CSV from an incoming email, parses each row individually, hits an external API for every vendor assignment, handles response errors per row, and routes failures to a separate notification path — all without any manual input. 38 modules total. 2,880 executions per month.
The tricky part wasn't the API calls. It was building reliable per-row error handling at volume. If row 47 fails, rows 1–46 and 48–300 should still process. A naive "run it top to bottom" approach breaks the whole batch on the first error. We had to build a forgiving iterator that logs failures independently and continues.
The other thing people underestimate: email is not a reliable trigger. Attachments arrive encoded differently across email clients. We added normalization logic early in the pipeline before the parser ever sees the data.
End result: a team that spent 2+ hours on manual vendor assignments now reviews a summary report instead.
"Just automate the CSV" is almost never as simple as it sounds — and that's usually where the interesting engineering is.
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started