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

**URL:** <https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486>\
**Category:** Hire Help\
**Tags:** ai\
**Created:** [March 26, 2026, 7:15pm UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486 "2026-03-26T19:15:31Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevyn\_Cress](https://avatars.discourse-cdn.com/v4/letter/k/77aa72/32.png) [@Kevyn\_Cress](https://community.make.com/u/Kevyn_Cress)\
**Post date:** [March 26, 2026, 7:15pm UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/1 "2026-03-26T19:15:31Z")

</div>

I want a [Make.com](http://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!!!

---

<div class="post-metadata">

**Author:** ![Gabriel\_Akinola](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/gabriel_akinola/32/83825_2.png) [@Gabriel\_Akinola](https://community.make.com/u/Gabriel_Akinola)\
**Post date:** [March 26, 2026, 7:26pm UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/4 "2026-03-26T19:26:15Z")

</div>

Hey Kevyn,

This is very doable in [Make.com](http://Make.com), I’ve built similar workflows for automated social media posting 👍

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 [fopefoluwaakinola@gmail.com](mailto:fopefoluwaakinola@gmail.com) so we can get this running quickly.

Cheers,  
Fopefoluwa

---

<div class="post-metadata">

**Author:** ![Pathfinder\_Automate](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/pathfinder_automate/32/92144_2.png) [@Pathfinder\_Automate](https://community.make.com/u/Pathfinder_Automate)\
**Post date:** [March 26, 2026, 7:28pm UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/5 "2026-03-26T19:28:23Z")

</div>

Hello @Kevyn_Cress, welcome to [make.com](http://make.com/) community, I have worked and have experience with [Make.com](http://make.com/) and l will love to collaborate with you on this you can schedule a call [Here](https://calendly.com/taiwo-pathfinderautomationsolutions/30min) and you can checkout my upwork profile [Here](https://www.upwork.com/freelancers/~01446d60f782215efa), for my pastworks and certifications

---

<div class="post-metadata">

**Author:** ![Greatness\_Solutions](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/greatness_solutions/32/93374_2.png) [@Greatness\_Solutions](https://community.make.com/u/Greatness_Solutions)\
**Post date:** [March 26, 2026, 7:39pm UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/6 "2026-03-26T19:39:17Z")

</div>

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](https://calendly.com/philipadeniji655/) to discuss this better.

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

---

<div class="post-metadata">

**Author:** ![Farhan\_Ahmed](https://avatars.discourse-cdn.com/v4/letter/f/b5a626/32.png) [@Farhan\_Ahmed](https://community.make.com/u/Farhan_Ahmed)\
**Post date:** [March 26, 2026, 7:42pm UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/7 "2026-03-26T19:42:01Z")

</div>

This is definitely doable in [Make.com](http://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?

📄 Check my profile:[https://www.upwork.com/freelancers/farhana401](https://www.upwork.com/freelancers/farhana401)  
📞 Book a quick call:[Calendly - Automaxion](https://calendly.com/automaxion-meet)

---

<div class="post-metadata">

**Author:** ![Kevyn\_Cress](https://avatars.discourse-cdn.com/v4/letter/k/77aa72/32.png) [@Kevyn\_Cress](https://community.make.com/u/Kevyn_Cress)\
**Post date:** [March 26, 2026, 7:42pm UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/8 "2026-03-26T19:42:50Z")

</div>

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).

---

<div class="post-metadata">

**Author:** ![alasless](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/alasless/32/70776_2.png) [@alasless](https://community.make.com/u/alasless)\
**Post date:** [March 26, 2026, 7:56pm UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/9 "2026-03-26T19:56:37Z")

</div>

You can still use [make.com](http://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.

> **[15 Min Meeting | Alasless Automation | Cal.com](https://cal.com/alasless/15min)**
>
> 15 Min Meeting

---

<div class="post-metadata">

**Author:** ![Folafoluwa\_Olaneye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/folafoluwa_olaneye/32/91924_2.png) [@Folafoluwa\_Olaneye](https://community.make.com/u/Folafoluwa_Olaneye)\
**Post date:** [March 26, 2026, 8:36pm UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/10 "2026-03-26T20:36:01Z")

</div>

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.](https://mavin-collins.my.canva.site/flowedge-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

---

<div class="post-metadata">

**Author:** ![Felipe-Aspirity](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/felipe-aspirity/32/53142_2.png) [@Felipe-Aspirity](https://community.make.com/u/Felipe-Aspirity)\
**Post date:** [March 27, 2026, 12:48pm UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/11 "2026-03-27T12:48:44Z")

</div>

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

We are a small team of [make.com](http://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](https://cal.com/aspirity/discovery?utm_source=make) discovery or check our website [www.aspirity.com](http://www.aspirity.com)

---

<div class="post-metadata">

**Author:** ![mikedev](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/mikedev/32/89712_2.png) [@mikedev](https://community.make.com/u/mikedev)\
**Post date:** [April 4, 2026, 11:32am UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/12 "2026-04-04T11:32:46Z")

</div>

> [@Kevyn\_Cress](#):
>
> I want a [Make.com](http://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!!!

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](http://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/](https://mikedevai.netlify.app/)

**Let’s get this live:**

- **WhatsApp:** [+375293761570](https://www.google.com/search?q=https://wa.me/375293761570)

- **Telegram:** [@hely\_chatbots](https://www.google.com/search?q=https://t.me/hely_chatbots)

---

<div class="post-metadata">

**Author:** ![TinyOpsStudio](https://avatars.discourse-cdn.com/v4/letter/t/7bcc69/32.png) [@TinyOpsStudio](https://community.make.com/u/TinyOpsStudio)\
**Post date:** [May 17, 2026, 12:17am UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/13 "2026-05-17T00:17:29Z")

</div>

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 [support@tinyopsstudio.com](mailto:support@tinyopsstudio.com) with the Sheet headers, one sample folder shape, and the scheduler app you prefer.

---

<div class="post-metadata">

**Author:** ![tester\_u](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/tester_u/32/92375_2.png) [@tester\_u](https://community.make.com/u/tester_u)\
**Post date:** [June 15, 2026, 7:01am UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/14 "2026-06-15T07:01:23Z")

</div>

Hi,

I can help with this.

I’ve recently built a very similar [Make.com](http://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](http://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.

---

<div class="post-metadata">

**Author:** ![Kathryn\_L\_Burrough](https://avatars.discourse-cdn.com/v4/letter/k/e95f7d/32.png) [@Kathryn\_L\_Burrough](https://community.make.com/u/Kathryn_L_Burrough)\
**Post date:** [June 19, 2026, 7:15am UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/15 "2026-06-19T07:15:31Z")

</div>

> [@Kevyn\_Cress](#):
>
> I want a [Make.com](http://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!!!

What you’re describing is a pretty classic content pipeline automation, and it’s actually very doable in [Make.com](http://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](https://latenode.com/integrations/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.

---

<div class="post-metadata">

**Author:** ![tamhn](https://avatars.discourse-cdn.com/v4/letter/t/e95f7d/32.png) [@tamhn](https://community.make.com/u/tamhn)\
**Post date:** [July 14, 2026, 9:21am UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/16 "2026-07-14T09:21:07Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![nigelyong](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/nigelyong/32/94320_2.png) [@nigelyong](https://community.make.com/u/nigelyong)\
**Post date:** [October 20, 2026, 7:39pm UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/17 "2026-10-20T19:39:20Z")

</div>

Kevyn, to your scheduler question: if Instagram is the main one, you can skip a separate scheduler at first and post straight from Make with the Instagram for Business module, then the Facebook Pages and Pinterest modules for the others. Drive watch \> Sheets lookup for vendor tags \> AI caption \> a Sheet row with an Approved status \> a scheduled scenario that only publishes Approved rows. That gives you scheduling without another tool. If you’d rather post to Instagram only and have it copied to Facebook and Pinterest automatically, I built PostOnce.to for that: it crossposts in about 10 minutes, and there’s a 7-day free trial.

---

<div class="post-metadata">

**Author:** ![Runze\_Shenrunzeworks](https://avatars.discourse-cdn.com/v4/letter/r/919ad9/32.png) [@Runze\_Shenrunzeworks](https://community.make.com/u/Runze_Shenrunzeworks)\
**Post date:** [October 23, 2026, 11:44am UTC](https://community.make.com/t/wedding-photographer-looking-for-help-building-a-make-automation-for-social-media-automation/106486/18 "2026-10-23T11:44:34Z")

</div>

Hi Kevyn — I’m Runze, I run RunzeWorks, a small automation studio. Drive folder drops → read the wedding name → pull vendor tags from Sheets → AI caption → schedule out to Instagram (and later Facebook/Pinterest) is a clean Make build, and I’ve engineered the pieces already.

Transparency: we’re a new studio, so instead of client work under NDA, here are the builds that map to yours — happy to walk you through any on a call or send a Loom:

- Airtable-backed reporting engine (Make + Google Sheets): multi-source pull and row matching — same discipline as reading a Sheet of vendor tags against a folder name.

- Error-logged operations pipeline (Make): validation → routing → status write-back with retries — so a failed post never silently disappears, which matters when a gallery is supposed to go live on a schedule.

- AI front-desk agent (n8n + GPT-4 + Twilio): the same kind of AI step your caption generation needs, already running in production-style form.

\*\*Fixed price: US$300. Timeline: 5–7 working days\*\* from the day you share a sample folder structure and your Sheets tag list. Milestones: 30% to start, 40% when it runs on your test data, 30% at handover.

Scope of that price: watch the Drive folder, parse the wedding name, match vendor tags from your Sheet, generate the caption with AI (you approve the prompt and tone first — it will sound like you, not like a robot), schedule to Instagram via a scheduling tool you already use or one I set up (Buffer or Later, your call), and a simple log so you can see what posted and when. Facebook and Pinterest are the same modules switched on — I’ll include them if your scheduling tool’s plan covers them, and if not I’ll quote them separately before doing anything.

You also get a written walkthrough in plain language — where the files live, how the caption prompt works, and how to pause or reschedule any post yourself. You won’t need me for routine changes.

One honest note: Instagram scheduling through third-party tools needs a business/creator account connected to the scheduling tool — if your account is personal, that’s a five-minute switch on your side and I’ll walk you through it.

Reply here with a sample folder and your tag list, and I’ll send the one-page plan within 24 hours. If you’d rather start smaller, I do a paid mapping session (US$50, credited to the build) first.

Runze — RunzeWorks
