Connect (DuabaConnect) — The Social / Marketing / AI & Automation Engine

Social media management + AI-powered automation, self-serve or done-for-you.

DuabaConnect (“Connect”) is the social-media management and AI-powered automation engine of the Duaba ecosystem. It pairs Postiz-powered social management with a no-code n8n automation marketplace, and offers both as a product you run yourself or a service Duaba runs for you.

Live at duabaconnect.com.

Explore this section

Two service models

The same backend serves both. In the database a client’s SocialLink.mode is either selfserve (they drive their own Postiz workspace through the OIDC bridge) or managed (Duaba operates Postiz under one operator account, one Postiz “Customer”/group per client).

What it does

Unified social workspace

Connect manages social accounts across platforms through Postiz (via its public API): auto-detect connected accounts, publish, schedule, and read analytics (impressions, engagement, followers) in one place. See Self-Serve.

AI content creation & scheduling

AI-assisted content generation and scheduling, with a first-class content calendar. Campaigns turn a product into a stream of review-ready posts; a dual-mode scheduler both generates the next batch and auto-publishes due posts.

Content request & approval workflow

For the managed service, clients submit content requests and approve work through a dedicated, read-only-friendly approval surface before anything ships. See Managed Service.

Automations Marketplace

The centrepiece: pre-built, parameterized n8n workflows that deploy one-click:

• Subscription (always-on) or one-time (run-once) billing per workflow.
• Outputs are ingested back via webhooks into Connect.
• An Automation Studio provides the catalog, deploy/config, run history, and usage analytics.

The marketplace draws its workflows from the monorepo’s shared automation layer (/ai-automations).

The engine’s role: embedded in other apps

Connect is also an engine other apps embed on behalf of their own clients. Sellub, for example, can offer a seller “run a product campaign” or “deploy this automation” button — backed entirely by Connect via the API-key-gated /api/connect/* surface and the @duabalabs/connect-client SDK. Connect never stores the integrator’s catalog; every call carries a clientRef (the integrator’s stable id for the end client).

Identity & single sign-on

Connect owns its own Parse user base and bridges to Postiz with an OAuth/OIDC flow:

/connect/authorize → postiz_oauth_authorize (cloud fn) → one-time code → Postiz /oauth/token

So a single login spans both DuabaConnect and Postiz.

Billing & entitlements

Billing runs through Sellub (Paystack, GHS):

• Plan subscriptions — e.g. Starter GHS 29/mo, Growth GHS 79/mo.
• Workflow-level subscriptions and one-time payments.
• An order registry fed by Sellub webhooks drives entitlements.

See Billing & Plans.

Architecture

How it connects to the ecosystem

• DPS — Connect provisions itself as a DPS tenant and uses DPS Parse cloud functions for auth and hosting.
• Sellub — Connect uses Sellub for payments and subscriptions; Sellub webhooks feed its order registry.
• ai-automations — the marketplace draws its deployable workflows from this shared layer.
• Postiz — Connect consumes Postiz for all social account management and publishing.

Source repos

• duabalabs/duabaconnect-landing — landing
• apps/duabaconnect — Connect backend (Parse Server 9 + Express, DPS tenant)
• apps/ai-automations — shared n8n workflows + AI tooling

Status