Keep going
Every workflow on Rundown University, free for 7 days
Members get all guides, courses, live sessions, and $1,000+ in partner perks.
Guides The Rundown AI published jun 4, 2026
In this guide, you will learn how to build a custom content calendar in Manus that plans, generates, and updates each week of social posts for you. The finished system gives you a simple one-page calendar you can review in Manus, while the generated posts and assets are saved back into Google Drive.
You will build a simple one-page HTML content calendar in Manus.
The calendar will:
Pro tip: If you use Instagram, connect it too. Manus can use it for brand context and, depending on your setup, help with posting.
Once the skill works, ask Manus to turn it into a weekly automation.
Use this:
Create a weekly automation that runs this skill.
Every week, generate the next seven days of social posts from the brand documents in Google Drive.
Update the HTML content calendar and save the generated posts and assets back into Google Drive.
Before scheduling it, show me:
- when it will run
- which Google Drive folder it will use
- what it will update in the calendar
- where the generated posts and assets will be savedThat is the bigger pattern: Google Drive holds the brand context and finished assets, Manus runs the weekly planning process, and the HTML calendar gives you a visual dashboard for what is coming next.
Start by creating a Google Drive folder for this content calendar.
Add any brand documents Manus should learn from. You do not need a giant strategy archive. A small input pack is better:
The goal is to give Manus enough context to sound like your brand and plan around a real campaign.
If you already have clean brand docs, use those. If you do not, add the best materials you have and let Manus tell you what is missing.
Open Manus and connect Google Drive from the Connectors page. Choose Google Drive, authorize your account, and then create a new Manus project for this calendar.
Once Drive is connected, Manus can read the files in your project folder and save generated posts or assets back into Drive.
That is the part that makes this workflow useful. The calendar lives in Manus, but the actual work files live somewhere your team can access.
Pro tip: If you connect multiple services, keep the task focused. Toggle on the connectors Manus actually needs for this project so it does not wander into unrelated context.
Now ask Manus to build the simple calendar interface.
Use this prompt:
Build a simple one-page HTML content calendar that I can use as a visual planning dashboard for one week of content at a time.
Use the brand documents in my Google Drive folder to generate post titles, captions, and needed assets for [Instagram, LinkedIn, X, email].
Show each post and asset in the calendar page, and save the generated posts and assets back into Google Drive.Be specific about the channels you actually use. If you only post on LinkedIn and Instagram, remove X and email from the prompt.
Pro tip: Say simple one-page HTML content calendar, not full app or SaaS app. In the demo, Manus started going bigger and tried to turn the workflow into a full app with more moving parts. That looked impressive, but it also created more debugging.
For this guide, stay simple. You want a calendar you can open, review, and refresh. You do not want to spend the rest of the afternoon programming.
Once the page works, ask Manus to generate the first week of posts based on the brand assets in Google Drive.
Use this prompt:
Generate the first week of posts for this content calendar.
Base the ideas on the brand documents and assets in my Google Drive folder.
For each post, include:
- channel
- post title
- caption
- CTA
- asset needed or generated
- status
Show every post in the HTML calendar page, and save the generated posts and assets back into Google Drive.After Manus finishes, check two places:
That second check matters. A calendar preview is nice, but the real payoff is having the actual files in Drive where you can use them, review them, or share them with a team.
When the first week looks right, turn the working process into one Manus skill.
Use this:
Turn this planning and generation process into one reusable Manus skill.
The skill should:
- read the brand documents from this Google Drive folder
- generate one week of social posts
- update the one-page HTML content calendar
- save the generated posts and assets back into Google Drive
- keep the workflow lightweight and avoid turning this into a full SaaS appThis is the point where the system becomes more than a one-off prompt. Next time, you should be able to run the skill instead of rebuilding the calendar from scratch.
Keep the skill focused on the repeatable part: plan one week, update the calendar, save the outputs. Do not make it repeat one-time setup steps like connecting Google Drive or creating the project.
Keep going
Members get all guides, courses, live sessions, and $1,000+ in partner perks.