Make.com Creatomate Automation Build Needed

@rajat07me

The critical part here is not just connecting Make to Canva, but proving first that Canva Pro can reliably update your existing animated Arabic templates and export both MP4 and image files without breaking branding, music, fonts, or watermark layers. I’d start with that POC exactly as you described, because if Canva’s available API endpoints or export behavior have limits, it’s better to confirm that early before building the full daily workflow. I’ve worked on Make-based automations where the real challenge was not the scenario builder itself, but handling platform constraints, retries, and fallback actions cleanly so the workflow stays usable in production. This setup is a good fit for that kind of approach since your end goal is simple operationally—3 finished assets per day in Drive—but the success depends on preserving existing design behavior inside Canva rather than rebuilding assets manually. - Are your Canva templates already structured with replaceable text/background elements, or do some parts sit inside grouped/locked elements that may affect automation? - For the incoming text/data, will Make receive it from a sheet, form, database, or another source? - Do you want the ClickUp task to include the failed payload and error reason so manual correction is easier?

@sarimshoaib1425

Hey, that's doable, and smart to start with the PoC first. Canva's API can autofill templates and export, so proving that works before you commit to anything bigger is the right call. Genuinely can have the PoC ready within a few days to confirm it before we scope the full daily pipeline. Let's do it.

@tyronet2

You’re approaching this correctly by proving Canva Pro automation capability before committing to the full workflow or upgrading the account. I’ve built API-driven automation with Make.com-style workflows, Google services, content pipelines, and error/retry handling, so I’d start with a focused POC against one of your existing Canva templates. The test will verify whether the available Canva APIs can replace Arabic text and backgrounds while preserving branding, fonts, animation, watermark and music, then automatically export both MP4 and PNG/JPG. Once verified, I’ll build the production workflow for 3 designs per day, save outputs to Google Drive, add controlled retries, and create a ClickUp task only when retries fail. I’ll keep the workflow modular and documented so templates and content can be changed later without rebuilding the automation.

@shayankhan333

The PoC is the right call here, Canva's public API currently supports template autofill and export, but MP4 export and preserving embedded audio on video templates is where most builds hit a wall. I'll wire the Make scenario against your Pro account first, autofill an Arabic text template, export MP4 plus PNG, drop to Drive, and add the retry-then-ClickUp branch. 1) Are your video templates built with Canva's native animations, or do they include uploaded audio tracks? 2) Where does the daily text come from, a Sheet, Airtable, or webhook? Cheers Shayan

@rosscarter1011

Hi, The critical part of this automation is proving that Canva Pro exposes the existing template elements in a way that allows Arabic text and backgrounds to change without disturbing the watermark, music, fonts, or animations. The POC should therefore test the actual template, not just whether Canva can create or export a design. That will reveal early whether the required elements remain editable and whether MP4 plus image exports can complete reliably before building the full Make workflow. Once confirmed, the retry and ClickUp fallback can sit around the production flow, with Google Drive receiving files only after successful exports. Can the existing Canva templates be shared for the POC, and are the text and background elements already separate editable elements rather than flattened artwork?

@DeveloperStation

Hi, Smart to make the proof of concept the first gate. The real risk here is that Canva's Connect API does not expose full video render and export the way the editor does. Autofill can swap text and images in a template, but MP4 export with your music and animations may not be reachable through the API on Pro, which is exactly what the PoC should tell us before anyone pays for Enterprise. Quick question: are your templates Canva video designs, or static designs you animate at export? We build automation flows and AI-driven pipelines in-house, including a system that runs multi-step business workflows with retries and task fallbacks. BD Automation: internal MangoCoders workflow engine First step I'd take: run one template through Make to Google Drive and report exactly what exports. Fixed as a milestone so you only release on that result. Sound right? Adil

@mikes126

The Proof of Concept is the right first step here — I’d verify the Canva API can actually modify your existing template and export both MP4 + PNG/JPG before building the full Make workflow. I can build this around Make + Canva + Google Drive, with the workflow structured as: Receive Arabic content → update template text/background → preserve existing branding/music/fonts/animations → export MP4 + image → save to Drive. For reliability, I’ll also add automatic retries and a ClickUp task only after repeated failure, so the daily 3-video process stays hands-off. I would start by testing one of your real Canva Pro templates rather than assuming an Enterprise upgrade is required. The POC will establish exactly what Canva’s current API permits for your template and which parts, if any, need an alternative approach. One important question: can you share one sample Canva template and an example of the text/background data that Make will receive?

@Cruz1217

Arabic right to left text often breaks when the Canva edit call replaces placeholders, so I’ll test the placeholder format first. I’ll call the Canva edit endpoint with the template ID, inject Arabic strings and background color, then fire export calls for MP4 and PNG. If the export succeeds, Make will move the files straight to Google Drive, and any failure will trigger the retry logic. A common mistake is assuming the API returns a ready file instantly; it usually needs a short polling loop. To avoid that, I’ll add a small wait and check loop before pulling the download URLs, so the workflow won’t fire a false error. You’ll get three videos and matching images each day saved to Drive, with a ClickUp task only when a real persistent error occurs.

@leeroyk1

The challenge of automating video and image production from Canva while maintaining brand integrity is critical for your project's success. Because my background bridges full-stack web development, backend automation, and data optimization, I make sure whatever piece I build for you perfectly aligns with your overall business goals. My approach will focus on creating a reliable, scalable automation that ensures seamless text and background updates while preserving your existing design elements. By implementing robust error handling, I will ensure that any failures trigger automatic retries and, if necessary, create ClickUp tasks for resolution. You can view my verified work samples attached directly to my freelancer profile portfolio items. What specific requirements do you have regarding the text formatting and design elements for the Arabic content? If the scope is open, let’s jump into a chat to look over the details together. Worst-case scenario? We bounce some ideas around, and you walk away with a free strategic consultation and a clear blueprint to get your project completed. Talk soon, Lee-Roy

@spidey56

I've built double-entry ledger systems and multi-tenant SaaS backends (Node/Express, PostgreSQL, JWT auth) before, and I want to flag scope vs. budget honestly: a Tally-equivalent with payroll, GST e-filing, and native mobile apps is a multi-month build, not a fixed-price job at this range. I'd propose starting with a scoped Phase 1 — company setup, voucher-style invoicing, ledgers, and a balance sheet drill-down, web-only — so you can validate the approach before committing to inventory, payroll, and mobile. Happy to share past work and discuss a realistic phased budget.

@abrahamdev

Hi, I like that you’ve made the POC the first step instead of assuming the Canva API will do everything you need. That’s the right way to approach this. I’d test one of your actual templates first, including the Arabic text, background changes, exports, and preservation of the existing branding, music, fonts and animations. Once that works, the Make workflow can be built around the confirmed Canva capabilities, with Google Drive, retries, and ClickUp handling. Happy to take it from there.

@jtolbert0175

Hi com automation setup integrated with Canva to streamline image and video processing workflows. com’s API integration capabilities to automate interactions with Canva, ensuring seamless data transfers and actions within the workflow. My hands-on experience with building API-driven automation on similar platforms makes me a strong fit for this project. com) that automated image manipulation and processing tasks, improving process efficiency. com for workflow automation—it’s a powerful choice for scaling tasks. I can help bring this project to fruition and would be glad to walk you through how we can integrate it smoothly with Canva. Let’s discuss your specific needs and see how we can enhance your automation setup. Thanks, Jonathan