Build with Caroush

Example workflows

Connect real tools into carousel, publishing and automation workflows.

Take the docs with youMarkdown for your editor or agent.
Download guide

The Tool reference below and catalog.json are generated directly from ToolCatalog. Each entry includes its strict input schema, structured output schema, required scope, read/write behavior, browser approval and background-handler flag. Unknown arguments are rejected. queued_handler=false does not imply a finished output: some fast handlers enqueue the existing native job themselves.

Implemented groups:

  • Account: identity, authorized workspace, credits, plan/quota settings and operation status.
  • Products: list/get/create/update/delete, safe URL detail fetching and stored product assets.
  • Content and search: bounded listing/search, drafts, text creation, image-post creation from existing owned assets, reading and deletion.
  • AI: real caption/hook/hashtag variations and UGC on-screen hook generation through the shared text services.
  • Carousels: available design systems, full generation, saved outline, current results, targeted regeneration, checkpoint retry and human approval.
  • Media: list/search/get saved owned images and videos. An asset ID refers to the database asset, not a filesystem path.
  • Social and schedules: safe connected-account list, delivery records, publishing and scheduling existing content.
  • Automations: draft/create/update/enable/disable/delete/run, configuration and run history for carousel and video generation, including 2×2, single fade and AI UGC.
  • Analytics: real saved account/post metrics and highest-viewed content from Caroush-published deliveries.
  1. list_products → choose a product; list_carousel_formats → choose an available format.
  2. generate_carousel with the product ID, supported slide count, design and a new idempotency UUID.
  3. Poll get_carousel until generation is complete. Read the generated slides and copy.
  4. Request approve_carousel; the user reviews and approves it in Caroush.
  5. Use list_connected_social_accounts to select the owned LinkedIn destination.
  6. schedule_post with the existing post ID and explicit timestamp. The user reviews the exact destination and date; poll the returned operation and schedule.

Carousel generation follows the saved product's niche and editorial profile. A generic prompt without a product does not bypass product selection. Use the selected tool's schema for exact field names, limits and enum values.

Learn from performance

Use get_account_analytics and get_best_performing_content, then read relevant saved posts. The agent can reason over these results and draft fresh captions with generate_captions. It can create a real new carousel from the existing product. Do not call invented campaign or content-variation tools.

Create a draft with create_automation. Choose kind=video or kind=carousel and the actual configuration options in the schema. For video, configuration.type is ugc-video, grid-video or fade-video; the corresponding template_id values are ugc-video, 2x2-grid and single-fade. UGC requires an owned stored 3–15-second CTA video; use cta_asset_id rather than a URL or local path. Presenter and library-pool management remains in Studio; reuse valid configured IDs or inspect an existing automation with get_automation rather than inventing IDs. Then request enable_automation or one run_automation. The user approves it, and native pipelines enforce credits, subscription, presenter, CTA, social-account and media rules.

These generation automations support daily configured times and manual occurrences, not arbitrary cron/RSS/webhook/event graphs. Existing legacy folder scheduling is a different system; it is not silently translated to new generation definitions.