Integrations
Vireloop publishes finished articles to your site through a connector. Pick the one that matches how your site is built. You can connect during onboarding or anytime from Sites → Add site.
Choosing a connector
| Connector | Use it when | How it publishes |
|---|---|---|
| WordPress | You self-host WordPress. | REST API + Application Passwords. |
| WordPress.com | Your blog is hosted on WordPress.com. | One-click OAuth, then the WordPress.com REST API. |
| Next.js Blog (B1) | A Next.js site you own, backed by Supabase, where Vireloop can write directly. | Direct Supabase insert, then an on-demand revalidate. |
| API Webhook (B2) | Any site — you want a clean, decoupled contract you control. | Vireloop POSTs the article to your ingest endpoint with an access token. |
| Git static blog | A file-based static blog (Astro / Next.js Markdown) with no database or CMS. | Commits a Markdown file to your GitHub repo; the push triggers your host's rebuild. |
How credentials are protected
- Every secret (application password, service-role key, access token, shared secret) is stored in Supabase Vault — never in a readable column and never in the browser.
- Connector calls run server-side only. Keys never reach the client bundle.
- Secrets are shown once at creation and cannot be retrieved again — if you lose one, generate a new one.
- Every table is row-level-security scoped by organization, and each site's credentials are separate.
Set up a connector: WordPress · Next.js Blog · API Webhook