Automations are recipes. A recipe says when something should run, what source material it should use, what draft should be created, and whether the result should stay for review, become a draft, or be scheduled.
The basic shape
- Trigger: what starts the run. Examples: run manually, run on a schedule, or run when a new feed item arrives.
- Optional filter: skip items that do not match the recipe. Example: only items containing "workshop".
- Pick context: choose a Library or Feed item to use as the source.
- Draft: ask bbuddy to create the post copy for selected platforms.
- Optional approval: pause until you approve or reject the run.
- Post step: save to Suggestions, save as draft, schedule, or publish depending on the recipe and your mode.
Automation screen
- Create: starts a new recipe.
- Left rail: lists your automations and shows their latest status.
- Active toggle: turns a recipe on or off. Paused recipes do not run automatically.
- Run now: tests the selected recipe immediately.
- Delete: permanently removes the recipe.
- Run history: shows recent runs and whether they finished, failed, paused, or are waiting for approval.
- Run detail: opens the details for a specific run so you can understand what happened.
Triggers
- Manual: only runs when you click Run now. Best for testing.
- Scheduled: runs at a recurring time such as daily or weekly.
- Feed item new: runs when a chosen Feed source imports a new item.
Common recipes
- New article to suggestion: when a new RSS item arrives, draft a post and save it to Suggestions.
- Upcoming event reminder: pick the next upcoming event and schedule a post a set number of days before it starts.
- Daily library quote: once per day, pick a Library item tagged as a quote and create a short post.
- Manual campaign helper: run manually, pick the newest saved Feed item, draft variants, and leave them for review.
Review and approval
A recipe can pause for human approval. When a run pauses, review it from the run history and approve or reject the waiting step. This is useful when a source is broad, a claim needs review, or a post may mention time-sensitive facts.
Scheduling from event dates
Event-based automations work best when the Feed item has event metadata. If bbuddy knows the event start date, it can schedule a post before or after that date. If the event date is missing, keep the recipe review-first so you can choose the timing manually.
How to ask bbuddy for an automation
- "Create an automation that drafts a LinkedIn post when a new article lands in my feed."
- "For every new workshop in this RSS feed, schedule an Instagram post 7 days before the event."
- "Every Monday at 9:00, create one Facebook suggestion from my saved Library facts."