Make.com to Tumblr: Automation the Client Could Follow

Make.com to Tumblr: Automation the Client Could Follow

I delivered a Make.com-to-Tumblr automation project for a returning client. The engagement ran from 16 May to 10 June 2024, with 15 hours recorded on Upwork.

The client specifically wanted to understand the process and see it working. That requirement drove the choice of Make: a visual workflow they could follow. I used it to deliver the agreed brief in a form the client could follow.

This was my second project for the client. They awarded a five-star review and praised my efficiency, ability to follow the brief and problem-solving.

My general recommendation for systems expected to scale is to start with a maintainable, code-based foundation. I usually advise against building an entire growing operation around tools such as Make, Zapier or n8n, because platform limitations can create costly technical debt as requirements expand. I assess the long-term fit alongside the immediate benefit.

For this engagement, the client's priority was a process they could understand and observe, so Make was a deliberate choice. The case shows how I balance engineering judgment with the actual brief: understand the client's needs, explain the trade-offs and deliver a solution suited to the work.

Evidence: completed Upwork engagement, recorded hours and public client feedback.