1. Reference
  2. Integrations

​
Integrations

Alfa’s publishing surface is organized per brand. That means each brand can have its own publishing destination and settings rather than forcing the entire workspace through one CMS connection.

​
Current Direct Publishing Path: WordPress

WordPress is the most complete setup flow in the current app.

​
What You Configure

  • WordPress site URL
  • WordPress username
  • WordPress application password
  • whether the post should land as a draft or publish immediately

​
What the Flow Supports

  • test connection
  • save credentials per brand
  • disconnect and reconnect later
  • publish completed articles directly from the article workspace

If you want editorial review before going live, keep WordPress configured in draft mode and use Alfa as the drafting and export layer.

​
Other Destinations Listed in Alfa

The settings surface also lists additional targets:

  • Webflow CMS
  • Ghost
  • HubSpot CMS
  • Shopify Blog
  • Next.js
  • API / Webhooks
  • Alfa-hosted blog

These appear in the product surface as Pro-oriented publishing paths. WordPress is the clearest current implementation.

​
API and Webhook Workflows

If your stack is custom, Alfa’s export formats plus API/Webhooks positioning give you two ways forward:

  • export files from the UI or CLI
  • connect Alfa to your own downstream publishing automation

​
When to Use Which Path