SMB Pulse

Plan this month's content around what sells

Build the month's content around the products that are selling, hold back a product that draws complaints, see stock and missing photos before anything is promoted, and approve the posts that go ahead.

Pick a use case and follow its guide

Plan this month's content around what sells

0 of 6 steps done

Sign in to try the demo
  1. Step 1. Open Operations, then campaigns.start_from_sales. Type the month's discount code in discount_code and its tracking tag in utm_tag, and press Call campaigns.start_from_sales. Under ANSWERED, the draft names two or three products to push (pushed), the slow products to bundle (bundled), and, listed apart under troubled, any product drawing complaints, which is never pushed. Every product it considers with under two weeks of stock cover is listed in flagged, with its stockout date in stockout_dates, read from the stock plan. The draft is stored with status draft; nothing is sent. Open campaigns.start_from_sales

  2. Step 2. Open Operations, then campaigns.plan_calendar. In campaign_id, type the id the previous step returned. In channels, type instagram_feed and press Enter, then email and press Enter. Leave start_date empty to start on the campaign's own window start, and press Run campaigns.plan_calendar. When the run turns SUCCEEDED, rows holds the campaign's calendar: the growth marketer chooses which product goes on which channel, and the app sets the days (Monday, Wednesday and Friday), each row's path (design for a picture channel, text_only for email) and any same-product, same-day conflict. design_rows and text_only_rows count them. Planning again replaces the calendar. Nothing is published. Open campaigns.plan_calendar

  3. Step 3. Open Operations, then campaigns.asset_manifest. In campaign_id, type the campaign's id and press Call campaigns.asset_manifest. Under ANSWERED, each design row of the calendar lists its image slots: a photo on file, or missing when no photo of that product exists. A missing slot is never filled with another product's photo, and the row is not ready for design until you choose what to do with it. Open campaigns.asset_manifest

  4. Step 4. Open Operations, then content.calendar, and press Run content.calendar. The run turns SUCCEEDED. The growth marketer proposes rows for the four weeks after the shop's as-of date, and the app adds only the slots the calendar does not already hold. A row you have edited or deleted is never rewritten, every price is the shop's own, and two rows for one product on one day are flagged. Nothing is published. Open content.calendar

  5. Step 5. Open Operations, then content.draft_posts. In as_of, type the moment to draft from (for example 2026-09-14T09:00:00-07:00), and press Run content.draft_posts. The run appears under the button and turns SUCCEEDED in about a minute. Under drafts, each coming calendar row has one draft in its channel: an email draft has a subject, a preheader and a body, and a design_request draft has a caption and hashtags. Each price is the shop's own. A draft written without voice samples carries a note saying so. The growth marketer words each draft, so the wording differs from run to run. Nothing is posted or stored. Open content.draft_posts

  6. Step 6. Open Workflows, then content-posts, and press New run. The run drafts one post for every calendar row after the shop's as-of date and stops at review_posts. In the Runs tab, press Open decision. The table reviewed_posts lists every draft, each with selected true. Press Remove on any post that should not go ahead and press Save under the table; check that approval_meta holds your user id, press Save under it, then Resume. The run turns SUCCEEDED, and post_result records each post left in the table as simulated_post, with its channel and a label saying where it would be sent. A post whose time has passed, or one that is held, is refused by name. Nothing is posted. Open the content-posts workflow

Did it fit your work?