Wedding Photographer looking for help building a Make automation for social media automation

I want a Make.com automation that:
• detects images uploaded to a Google Drive folder
• reads the wedding name from the folder
• pulls vendor tags from a Google Sheet
• generates a caption using AI
• schedules the post to Instagram using a social media scheduling app

  • potentially posts to Facebook and Pinterest as well.

Thank you in advance!!!

2 Likes

Hey Kevyn,

This is very doable in Make.com, I’ve built similar workflows for automated social media posting :+1:

Flow would look like:
• Watch Google Drive for new uploads
• Extract wedding name from folder
• Pull vendor tags from Google Sheets
• Generate caption with AI (including hashtags + tone)
• Send to a scheduler like Buffer/Later for Instagram (and optionally Facebook & Pinterest)

I can set this up end-to-end, clean and fully automated, with flexibility if you want approvals or direct posting.

I’m ready to start immediately, feel free to reach me at [email protected] so we can get this running quickly.

Cheers,
Fopefoluwa

Hello @Kevyn_Cress, welcome to make.com community, I have worked and have experience with Make.com and l will love to collaborate with you on this you can schedule a call Here and you can checkout my upwork profile Here, for my pastworks and certifications

Hey Kevyn, this is a solid use case for Make and definitely doable.

The key is structuring it as a clean pipeline: detect images → extract wedding name → pull vendor tags → generate consistent AI captions → send to a scheduler (Buffer/Later/etc.).

Most issues usually come from inconsistent captions or messy data flow, so getting that part right upfront makes it fully hands-off.

I’ve built similar systems, and once set up properly, it runs smoothly.

You can book a call with me here to discuss this better.

Are you already using a scheduler tool, or still deciding on one?

This is definitely doable in Make.com. I can set up a workflow that detects new images in Google Drive, extracts the wedding name from the folder, pulls vendor tags from Google Sheets, generates captions using AI, and schedules posts to Instagram (with options for Facebook and Pinterest as well).

I’ll make sure the workflow is reliable, structured, and easy to scale for multiple weddings.

Quick question: which scheduling tool are you planning to use for posting?

:page_facing_up: Check my profile: https://www.upwork.com/freelancers/farhana401
:telephone_receiver: Book a quick call:Calendly - Automaxion

I am still deciding on a scheduler tool. Any recommendations? Instagram is my main source of inquiries, but I’d like to post to Facebook and potentially Pinterest (using blog posts).

You can still use make.com own scheduler (scheduling the scenario to run every hour/minutes etc)

And posting to FB and Pinterest, ofcourse easily doable.

If you want you can connect with me here for quick 15 min discussion where i can guide you on call.

Hi Kevyn, welcome to the community.

For scheduling, tools like Buffer or Publer tend to work well with Make for this kind of workflow, especially if you want to schedule posts across Instagram, Facebook and Pinterest.

The automation you described is definitely achievable. A typical structure would be a trigger watching the Google Drive folder, extracting the wedding name from the folder structure, pulling the vendor tags from Google Sheets, then generating the caption with AI before sending everything to the scheduler for posting.

That way you only need to upload the photos and the rest of the workflow runs automatically.

I have built similar Make automations for content workflows and social posting systems. You can also check some of my work here in my portfolio website.

Feel free to DM me here if you’d like help setting it up or if you want to walk through the workflow.

Best regards,
Folafoluwa Stephen

Hi @Kevyn_Cress! I would love to help you with your scenarios.

We are a small team of make.com experts and have developed plenty of complex integrations. This project should not be a challenge to us.

If you are interested we would love to help you, you can schedule a call in here: Automation Discovery Call | Felipe Saucedo | Cal.com discovery or check our website www.aspirity.com

Hi!

Automating wedding content is a game-changer for saving hours of manual tagging. I’m an automation engineer, and I’ve built several “Content Factories” using Make.com and n8n that handle exactly this kind of multi-channel orchestration.

How I will build your system:

  • Smart Context: I’ll set up the trigger to watch your GDrive, pulling the “Wedding Name” directly from the folder structure to use as the primary AI context.

  • Vendor Tag Mapping: I’ll build a lookup logic in Google Sheets so the automation automatically pulls the correct Instagram handles for the photographer, florist, and venue associated with that specific wedding.

  • AI Copywriting: I’ll prompt GPT-4o or Claude 3.5 to generate engaging, “human-sounding” captions that naturally weave in the wedding story and vendor credits.

  • Multi-Channel Blast: I’ll connect your scheduling app (Buffer, Later, or Metricool) or use the Meta & Pinterest APIs directly to ensure the post hits all platforms simultaneously with optimized formatting for each.

I don’t just connect nodes; I build systems with Error Handling. If a vendor tag is missing in your sheet, the system will ping you on Telegram/Slack instead of posting an empty tag.

You can see my complex backend architectures and my own automated booking system in action here: https://mikedevai.netlify.app/

Let’s get this live:

This is a good Make use case. The fragile part is not the caption prompt; it is reliably tying each Drive folder to the right wedding name, vendor tag set, scheduler target, and post status without accidentally publishing the wrong gallery.

I would model one canonical wedding record first: Drive folder ID, wedding name, selected image set, vendor rows from the Sheet, caption draft, scheduler destination, and publish/draft status. Then the scenario can test missing tags, renamed folders, duplicate uploads, and scheduler failures before anything goes live.

For a first milestone I would prove: upload a small image batch, fetch the matching vendor tags, generate one caption, and create a scheduled draft in the social scheduling app. TinyOps Studio can do a fixed $149 audit and hand over the scenario map plus edge cases. If useful, email [email protected] with the Sheet headers, one sample folder shape, and the scheduler app you prefer.

Hi,

I can help with this.

I’ve recently built a very similar Make.com automation that monitors uploaded content, uses AI to generate captions and hashtags, and automatically publishes content across social media platforms.

Your workflow would be something like:

• Detect new images in Google Drive
• Read the wedding/event name from the folder structure
• Pull vendor information from Google Sheets
• Generate captions using AI
• Schedule posts to Instagram
• Optionally extend posting to Facebook and Pinterest

I have experience with Make.com, Google Drive, Google Sheets, OpenAI integrations, webhooks, and social media automation workflows.

I’d be happy to discuss the exact posting and scheduling requirements and provide an estimate.

Feel free to DM me.

What you’re describing is a pretty classic content pipeline automation, and it’s actually very doable in Make.com as long as you structure the data flow cleanly from the start.

The key is to treat Google Drive as the trigger layer, but not the “source of truth” for metadata. In most setups like this, the folder name (wedding name) is parsed first, then used as a key to look up everything else in the Google Sheet (vendor tags, hashtags, captions context, etc.). That keeps things consistent even if files get moved around.

A typical breakdown would be:

Drive trigger: new image in folder
Parse folder name: extract wedding/event identifier
Google Sheets lookup: vendor tags + metadata
AI step: generate caption + hashtags based on structured input
Scheduler module: send to Instagram (and optionally queue for other platforms)

For multi-platform posting (Instagram, Facebook, Pinterest), the main complexity is usually not the automation itself but adapting the same caption format to different content expectations per platform. Pinterest in particular tends to perform better when captions are more keyword-driven rather than social-style.

If you plan to scale this beyond a few clients, it’s worth thinking early about a unified content object (one structured payload that feeds all channels), instead of rebuilding logic per platform. Some people also extend these pipelines with tools like integrate pinterest workflows to keep Pinterest posting synchronized with the same asset pipeline rather than treating it as an afterthought.

Once that structure is in place, the whole system becomes surprisingly maintainable instead of turning into a chain of fragile scenarios.

Do not let the first image uploaded to Drive start the posting workflow. Wedding galleries tend to arrive in batches, and Make can fire while the rest of the files are still uploading. That is how you end up with a caption built from 2 photos or 3 scheduled posts for the same wedding.

Use the Drive folder ID as the wedding key, not just the folder name. Let the watch scenario update one row for that folder, then add a simple approval state in the Sheet. I would use something like Collecting, Ready, Approved, Publishing, Published, and Failed. You can mark Ready yourself when the gallery is complete. At approval time, freeze the selected images, caption, vendor handles, and scheduled time so a later Sheet edit cannot quietly change a post that is already queued.

For captions, give the model the couple’s approved details plus the vendor records, but ask for a few versions and choose one. Instagram brings you inquiries, so I would keep that review step. The opening line and photo selection will matter more than generating a huge hashtag block. Missing vendor handles should stop the run and send you a note instead of publishing partial credits.

On the scheduler question, blotato fits this shape because it has an official Make module and can publish to instagram, facebook, and Pinterest. The annoying detail is media access: pass a public direct image URL, not a Google Drive preview page. If the Pinterest account is new, warm it up manually before connecting any scheduler.

Get one approved instagram post all the way through and write the post ID back to the Sheet. Rename a folder during the test and leave a vendor row blank. After those behave properly, break one upload on purpose before turning on the facebook and Pinterest routes