Social and CMS integrations
Build reviewable social and CMS recipes around Hoko's shared engine.
Scope
The social and CMS recipes cover WordPress, Typefully, Buffer, Publer, Metricool, SocialPilot, Sprout, Webflow, and Ghost. Local recipes produce a provider request and durable reconciliation state. They do not claim that a post was published until a provider receipt exists.
Required inputs
- provider account, workspace, site, or profile;
- provider API key, OAuth grant, or customer-owned MCP connection;
- Hoko API key with only the scopes used by the recipe;
- provider record ID and an idempotency key;
- draft or review mode where the provider does not support safe publishing.
Boundary
Provider credentials stay in the provider connection or customer-owned host. The shared Hoko engine handles authentication, authorization, usage, rate limits, link creation, and reconciliation. An uncertain provider write must be reconciled by external identity before retrying.
See the Apps catalog, automation guide, and the social/CMS package README for provider-specific fields.