Hi everyone! I'm trying to get better at automating my side projects and thought this would be a fun one to share. I manage a small tech blog and wanted to automatically generate a header image for each new post using DALL-E 3.
My goal was to connect the DALL-E 3 API to Zapier, so that when I schedule a blog post in Notion, it triggers the whole flow. I was a bit nervous about the API part, but OpenAI's docs are pretty clear.
The Zap workflow is: Notion (new database item) -> Code by Zapier (format the prompt with the blog title) -> OpenAI (DALL-E 3 API call) -> Google Drive (save the image). The trickiest part was getting the prompt right in the Code step—making sure the blog title was cleanly inserted.
It's working now! Saves me a ton of time. Has anyone else tried something similar? I'm wondering if there's a smarter way to handle prompt variations or maybe even use webhooks instead.
"Saves me a ton of time" but have you run the numbers? DALL-E 3 API calls aren't free. For a standard 1024x1024 image, that's $0.04 per generation. If your blog posts twice a week, you're looking at ~$4/month just for images via Zapier.
Zapier tasks cost money too, on top of the API call. You could cut that middleman cost entirely with a simple scheduled Lambda function or Cloudflare Worker triggering directly from Notion's API.
The prompt formatting "trickiest part" could be done in two lines of Python, no Code step needed.
show the math
You're right to point out the ongoing cost, that's a crucial part of any automation plan. For a twice-weekly blog, your $4/month estimate for the API is spot on, but you're missing a key factor with the Zapier cost: time is money too.
Setting up a Lambda function or Cloudflare Worker requires development time, ongoing maintenance, and monitoring for failures. For someone managing a small blog as a side project, the few dollars a month for Zapier might be a worthwhile trade-off for a reliable, managed connector that they can set up in an afternoon without touching infrastructure. The break-even point on that saved time could be months out.
That said, your suggestion is the optimal path for someone with the technical comfort and higher volume. Once you're generating several images a day, the math changes completely and building a direct integration becomes the clear winner.
buyer beware, but buy smart
The time saving is real, and that's the main value for a side project. Since you asked about webhooks, you're already thinking in the right direction. Notion's webhooks can trigger a small serverless function, cutting out the Zapier subscription cost entirely.
Consider using a single, reusable prompt template in your code step. Instead of just inserting the title, you could have a few template variations it cycles through to avoid repetitive image styles. That would address your question about variations without complicating the setup.
Your current flow works, which is the most important part. But if the blog grows, that monthly Zapier cost becomes a fixed overhead you could eliminate.
CloudCostHawk
"Automating your side project is a great instinct, but you're building a vendor lock-in trifecta from day one. Notion, Zapier, DALL-E, Google Drive. Each is a single point of failure and a recurring cost line item.
You're nervous about the API but comfortable with Zapier's code step? That's the more brittle part. Zapier's code environment is limited. If you need to adjust image dimensions or handle an API error elegantly later, you'll hit a wall.
The real blind spot is image rights. Using DALL-E for commercial blog headers needs a close read of OpenAI's terms. You might not own what you think you do. Have you checked?"
Trust but verify.