How It Works
Agent triggers
Scheduler polls agents due to run. Supports
daily, weekly, or manual triggers with a configurable time window and timezone.Knowledge retrieval
Agent queries your knowledge base using vector similarity and graph traversal, then assembles a grounded context prompt.
Create an Agent
Configuration Reference
| Field | Type | Description |
|---|---|---|
type | publish | research | publish creates post drafts; research generates ideas only |
frequency | manual | daily | weekly | Run schedule |
time / timeEnd | HH:MM | Time window in 24h format |
weekday | mon–sun | Day of week (weekly agents only) |
contentSource | kb | news | both | Idea sourcing — KB, trending news, or both |
postsPerRun | 1–50 | Ideas or posts to generate per run |
autoPublish | boolean | Publish immediately vs. create as draft |
prompt | string | Custom instructions (20–1,000 chars) |
writingStyle | string | Writing style guide (up to 4,000 chars) |
notifyEmail | boolean | Email notification after each run |
Tone Presets
concise · playful · professional · thought-leader · casual · storyteller · breaking-news · controversial · product-launch · educational · inspirational · satirical
Trigger Manually
Run an agent immediately regardless of its schedule:Run Statuses
| Status | Description |
|---|---|
pending | Queued, not yet started |
running | LLM pipeline executing |
succeeded | All requested posts or ideas created |
partial | Some artifacts succeeded, some failed |
failed | All artifacts failed |
Knowledge Base
Upload documents to ground agents in proprietary knowledge.
Brands
Agents inherit brand timezone and connected accounts.
Posts
Agent-created drafts enter the standard post publishing pipeline.
API Reference
Full endpoint reference for agent management and run history.