# One scenario or more scenarios **URL:** \ **Category:** Beginner Questions\ **Tags:** filters, ai, api\ **Created:** [May 15, 2026, 6:03pm UTC](https://community.make.com/t/one-scenario-or-more-scenarios/108991 "2026-05-15T18:03:08Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Arif\_Khan](https://avatars.discourse-cdn.com/v4/letter/a/b487fb/32.png) [@Arif\_Khan](https://community.make.com/u/Arif_Khan)\ **Post date:** [May 15, 2026, 6:03pm UTC](https://community.make.com/t/one-scenario-or-more-scenarios/108991/1 "2026-05-15T18:03:08Z")
Is it possible and practical to build this entire E-Commerce & Content AI Automation in a single Make scenario? What is the best practice for structuring this? AI customer service email automation AI-assisted DM/customer conversation handling Automated social media posting from Google Drive uploads AI-generated captions/descriptions/hashtags Platform-specific posting workflows (Instagram, TikTok, Facebook, YouTube Shorts, etc.) AI content editing/clipping workflows Workflow automations, agents, and cron jobs ---
**Author:** ![Dylan1222](https://avatars.discourse-cdn.com/v4/letter/d/0ea827/32.png) [@Dylan1222](https://community.make.com/u/Dylan1222)\ **Post date:** [July 23, 2026, 4:10pm UTC](https://community.make.com/t/one-scenario-or-more-scenarios/108991/3 "2026-07-23T16:10:03Z")
i’d split this into a few scenarios instead of one giant one one handles new assets and content ids, one creates drafts and waits for approval, then the publish scenario fans out by platform. keep customer service and DMs separate because those failures need a different owner and retry policy i work with blotato. for the social part, its Make integration can handle the multi platform publish step so you dont need a large branch for every network. still save one result per destination so a failed tiktok post cant cause instagram to publish twice