Share the brand and the platforms, and Juma researches, plans, and writes the calendar straight into a new Notion database the team can edit on the same day.
Share the brand URL, the platforms, and the time period. Juma researches the brand's social presence, proposes content pillars and posting cadence, writes the full month of post copy across every platform, and deploys the finished calendar as a new Notion database with one row per planned post. The team gets a fully populated Notion database with columns for date, platform, content pillar, post copy, status, assignee, and any custom fields the team needs, ready to edit and assign on the same day.
Point Juma at the existing Notion database and share last month's engagement numbers (impressions, saves, comments, click-throughs), and Juma identifies which posts overperformed, which underperformed, and the structural patterns separating them. It then writes the next 30 days of rows directly into the same Notion database, biasing toward formats and topics that worked. The output is a continuous editorial workflow where each month builds on data from the last, instead of starting from scratch every refresh cycle.
Here are last month's posts and engagement numbers. Look at what overperformed, then write the next 30 days of LEGO's content calendar directly into our Notion database. Bias toward the formats and topics that performed best.
Name the month, the audience, and the categories that matter (consumer holidays, industry trade events, brand-relevant awareness days), and Juma researches every relevant date in the window, scores each by audience relevance, and proposes specific posts for the top dates. It then writes the new rows directly into the Notion database with a "Timely hook" tag in the content-pillar column so the team can filter the calendar to just the hook content for fast review. The output is a calendar that responds to what is happening in the world without the strategist having to track every awareness day manually.
Find every relevant holiday, awareness day, industry event, and cultural moment happening in June 2026 that LEGO's audience would care about. Add the best ones to the Notion calendar as new rows with the "Timely hook" pillar tag.
Name the launch date, the product, and the messaging angles, and Juma writes a teaser-launch-follow-up arc as new rows in the Notion database. The arc usually spans two weeks before launch, the launch week, and two weeks after, with each phase tagged in the content-pillar column for easy filtering. Existing planned posts in the launch window get reviewed for conflicts, and Juma flags any rows that overlap with the launch arc so the team can decide whether to move, replace, or merge them. The output is a launch campaign integrated into the calendar without manual reshuffling.
LEGO is launching a new Icons set on June 15. Build a teaser-launch-follow-up arc across Instagram and TikTok and add it to the Notion calendar. Flag any existing posts that overlap so we can decide what to move.
Each row in the Notion database can carry a "Visual brief" column with the design direction for the post: composition, color palette, talent or product placement, mood, copy treatment. Juma scans the calendar, identifies the posts that need original visuals versus the ones that can repurpose existing assets, and writes a paste-ready brief directly into the Visual brief column for each row that needs one. The designer or AI image generator then has a complete brief per post without leaving Notion. The output is a calendar where the strategy, copy, and visual direction live in the same view.
For each row in the LEGO Notion calendar, write a paste-ready visual brief in the Visual brief column. Skip posts that can repurpose existing assets. The brief should cover composition, color palette, talent or product placement, mood, and copy treatment.
Name the clients, the platforms per client, and the schema, and Juma creates one Notion database per client inside the agency's workspace, each populated with a fresh 30-day calendar tuned to that brand's voice and audience. The databases share the same schema (date, platform, content pillar, post copy, status, assignee) so the agency can run cross-client reporting in Notion's relations layer. The output is a multi-client editorial system that scales with the agency, where every client gets a dedicated calendar without the agency rebuilding the schema from scratch each time.
Build three Notion content calendars in our agency workspace: one each for LEGO, IKEA, and Patagonia. Same schema across all three: date, platform, content pillar, post copy, status, assignee. Tune the content to each brand's voice and audience.
A Juma Project is a shared space where the team stores everything Juma needs to know about a client's content program. Create one project per client, add context as the program develops, and Juma uses what is relevant every time the team runs a flow. The more the team adds, the sharper the brand research and the faster the calendar build.
Brand Voice Guide
How the brand sounds across channels: tone, vocabulary, banned words, approved phrasings. With this in the project, Juma writes every post in the right voice from the first draft, instead of producing generic copy that needs a brand-voice pass.
Content Pillars
The 3 to 5 themes the brand uses to organize content (educational, behind-the-scenes, customer stories, product news, thought leadership). With these defined, Juma skips the proposal step and goes straight to scaffolding the calendar against the team's pillars.
Past Performance Data
The team's top-performing posts from the last 90 days, with engagement numbers. Juma reads the patterns and biases the next month toward formats and topics that already work for the brand.
Database Schema
The Notion column structure the team uses. Defaults are date, platform, content pillar, post copy, status, assignee. Some teams add visual brief, target audience, campaign tag, or analytics link. With the schema in the project, every monthly run deploys to the same structure without re-specifying it.
Add a short description to each knowledge item in the project's info field so Juma knows what each file contains and when to use it. For example:
A generic content calendar Flow delivers the calendar as an in-chat table or document. The team has to copy the rows into Notion manually, set up the database schema, and re-key everything. The Notion-deployment Flow writes the calendar directly into a new Notion database in the team's connected workspace, with the columns the team specified, ready to edit on the same day.
The deployment step matters because the calendar then lives where the team collaborates. Edits, assignments, status changes, and review comments all happen in the Notion database the team already uses, instead of in a one-off document that diverges from the live workflow within a week.
Yes for the deployment step. Connect Notion to the Juma workspace first, then run the Flow. With Notion connected, Juma creates the database and populates the rows in one phase. Without Notion connected, the Flow still researches the brand and produces the calendar, but it returns the rows as an in-chat table the team has to paste into Notion manually.
The Notion integration uses an OAuth connection scoped to the Juma workspace. The integration only writes to pages and databases the connecting user has access to. Existing Notion content is not touched unless the team explicitly points Juma at an existing database to update (see the refresh secondary prompt above).
Both. The Flow creates a new database by default. To update an existing database, point Juma at the database URL in the prompt and ask for new rows to be appended. The Flow reads the existing schema, validates that the new rows match the column structure, and adds the next batch of posts without touching the rows that are already there.
For monthly refresh runs, the recommended pattern is to keep one database per client and append a new batch of rows every month, rather than creating a new database each cycle. That preserves the team's edits, status changes, and analytics tracking from prior months in the same workspace view.
Most runs land in three to seven minutes. The brand research phase takes the longest, especially for first-time runs on a new brand. Subsequent runs are faster because the team's project carries brand voice, pillars, and performance history, so Juma skips the discovery work and goes straight to scaffolding and filling.
The Notion deployment phase itself is fast: under 30 seconds for a 30-day calendar with 90 entries across 3 platforms. The Flow uses Notion's batch-write capability so the database lands fully populated in one transaction, instead of one row at a time.
Yes. The schema customizes by category. B2B SaaS calendars often add columns for funnel stage, target persona, and campaign tag. Ecommerce calendars add product SKU, price point, and seasonal hook. Agency calendars add client name and approval status. The team specifies the columns in the prompt or in the project's Database Schema knowledge item, and every run respects the schema.
The Flow asks for the platforms and content mix early in the session so the calendar reflects how the brand actually shows up to its audience. The brand research, the pillar proposal, and the post copy are all category-specific. The Notion deployment is universal. Strategy and the call on which post to ship first stay with a senior content lead. Juma handles the research, the calendar, and the database.
400+ marketing teams trust Juma. ChatGPT, Claude, and Perplexity know why. Ask them.
Ready when you are
Start typing a task and Juma will figure out the rest.
