Integrations Overview
Integrations let you connect external services to your Vivreal group. Once connected, you can manage products, publish social content, and sync data — all without leaving the portal.
How Integrations Work
Vivreal uses a manifest-driven integration system. Each integration is defined by a manifest file that declares its authentication method, configuration fields, capabilities, and available actions. This means every integration follows a consistent setup and management experience.
When you connect an integration, Vivreal stores the credentials securely within your group. All team members with the appropriate permissions can then use the integration's features.
Available Integrations
| Integration | Type | Auth Method | Sync | Publish | Analytics |
|---|---|---|---|---|---|
| Stripe | Payments | API key | Yes (products) | n/a | Orders + balance |
| X (Twitter) | Social | OAuth 2.0 | On demand | Yes | Placeholder (see below) |
| Social | OAuth 2.0 (Instagram Login) | On demand | Yes | Placeholder | |
| Social | OAuth 2.0 (incl. Company Pages) | On demand | Yes | Placeholder | |
| Social | OAuth 2.0 (Pages, via Facebook Login) | On demand | Yes | Placeholder | |
| TikTok | Social | OAuth 2.0 | On demand | Yes | Placeholder |
| Mailchimp | OAuth 2.0 | On demand | Yes (campaigns) | Audience-level |
Engagement metrics are placeholder for socials
Per-post engagement counts on social pages currently render as --. The OAuth bind, posting, scheduling, and per-account targeting are all live; what's missing is the cron that polls each platform's analytics API to backfill likes / impressions / reposts on published posts. This is on the roadmap.
Multi-account per channel
A single channel on one group can hold multiple connected accounts — for example, one personal LinkedIn account that admins three Company Pages. When you publish, you pick which account (and, for LinkedIn, which org page) to post from. The portal exposes this via the account picker on the post composer; the MCP server exposes it as list-channel-accounts + accountId on create-channel-post.
Connecting an Integration
Navigate to Integrations
Open the Integrations page from the sidebar. You will see a grid of available integrations with their status.
Select an Integration
Click on the integration you want to connect. This opens its configuration page with setup instructions.
Provide Credentials
Depending on the integration, you will either enter an API key or go through an OAuth authorization flow to grant Vivreal access.
Configure Settings
After connecting, review the integration-specific settings. For example, Stripe lets you choose which products to sync, while social integrations let you select posting preferences.
Integration Capabilities
Each integration can provide different capabilities depending on its manifest:
- Sync — Pull data from the external service into your collections (e.g., Stripe products).
- Publish — Push content from Vivreal to the external platform (e.g., social media posts).
- Analytics — View engagement metrics and performance data within the portal.
Webhooks are an outbound, developer-facing system — configured separately
Vivreal's webhooks feature is not an integration capability. It's an outbound delivery system you configure as a developer: you register your own HTTPS endpoint, and Vivreal POSTs JSON events to it whenever content in your group changes. This is independent of which third-party integrations (Stripe, social, etc.) you have connected.
Documentation for the webhooks system lives in the developer section:
- Webhooks overview — setup, signature verification, retries.
- Event types — full list of events Vivreal emits.
- Payload schemas — body format and examples.
Sync your data regularly
Connected integrations can sync data on demand. Visit the integration's settings tab and click Sync to pull the latest data from the external service.
Managing Integrations
From each integration's page, you can:
- View synced content — Browse products, posts, or other items pulled from the service.
- Update credentials — Rotate API keys or re-authorize OAuth connections.
- Disconnect — Remove the integration entirely from your group.
Disconnecting removes synced data
When you disconnect an integration, any synced collection objects associated with it will remain in your collections, but the live connection is severed. Re-connecting requires a fresh authorization.
Next Steps
- Set up Stripe for payments and product management.
- Connect social media accounts for cross-platform publishing.