Reference
Customize
Almost everything per client lives in the Config node. The notes below are the safe changes. Anything that alters who can post should stay a deliberate edit.
#Posting workflow Config
| Want to… | Change |
|---|---|
| Use your own Sheet or tab name | google_sheet_id, queue_sheet_name (must match the tab exactly) |
| Point at a different Facebook Page | Connect that Page in Zernio, then set zernio_account_id (and zernio_profile_id) |
| Post fewer or more rows per run | max_posts_per_run (default 5). Also respect Zernio's 25 posts/hour/account and Facebook's daily cap of 100 |
| Turn on caption polish | Activate AI Caption Polish (optional), add an OpenAI credential, edit ai_model and ai_brand_voice |
| Check the queue more or less often | Open Every 15 Minutes and change the interval. Publishing is still required for the schedule to fire |
| Retry a failed row | Fix the caption or image, set status back to approved. See idempotency before changing id |
| Alert someone on failure | Add Slack, email, or Telegram after Log Error to Sheet in the error handler |
| Pause publishing | Unpublish the posting workflow. Manual runs still work |
#Several clients
Duplicate the posting workflow for each client. Give each copy its own Config, Sheet, and Zernio profile/account. You can share one Error Handler or give each client their own error_log. If you use one Zernio API key, rate limits and billing belong to that whole team.
#Optional planner
In the planner Config you can change brand voice, content pillars, posts_per_week, preferred times, timezone (Asia/Manila by default), ai_provider, image_provider, and the per-provider model ids. Set image_provider = none for captions only.
Do not list a paid OpenRouter image model as a fallback on a :free caption request if you want that caption call to stay free — use the two Config fields separately, as the kit already does.
#Later platforms
Zernio can post to more networks, but Select Due Approved Posts currently keeps only rows whose platform includes facebook, and the publish body sends a single facebook entry. Instagram, LinkedIn, and others are a deliberate workflow change, not a hidden switch.