Self-Serve
In the Self-Serve model you run your own social presence and automations from the DuabaConnect dashboard. You sign in with your DuabaConnect account, connect your social platforms, generate and schedule content with AI, and track how it performs — all yourself.
Prefer to have Duaba run it for you? See the Managed Service.
1. Connect your social accounts
Connect manages your social accounts through Postiz. From the Social tab of the dashboard you authorize the platforms you want to publish to. Behind the scenes a single DuabaConnect login also grants Postiz access through the OIDC bridge, so you never manage a second login.
Supported platforms (per the SDK’s SocialPlatform type):
| Platform | Key |
|---|---|
instagram | |
facebook | |
| TikTok | tiktok |
| X | x |
linkedin | |
| YouTube | youtube |
pinterest | |
| Threads | threads |
Connecting platforms (OAuth per platform) is the one social capability still served by Postiz today. Publishing and generation already run behind pluggable provider seams (postiz | n8n | direct), so Connect can drop Postiz platform-by-platform without changing your workflow.
2. AI content creation & scheduling
Connect’s content engine is calendar-first. There are two ways content lands on your calendar:
Product campaigns
Point a campaign at a product and Connect generates a stream of posts for it. A campaign captures:
- the product (name, description, image, price, link);
- the platforms to publish to;
- a media type —
imageorvideo; - a frequency (posts per week) and an optional brief that steers tone and copy.
A campaign scheduler runs about every 15 minutes. When a campaign is due it emits its next batch (one post per platform) as review-ready drafts, then advances the next-due time by 7 days / frequencyPerWeek. Image posts are ready immediately; video posts may show generating while an async job finishes, then flip to ready.
Campaign posts are not auto-published. They stop at ready for you to review. You publish a ready post yourself (the “resend for posting” action) — this is deliberate, so nothing ships without a look.
The content calendar
The calendar generalizes campaign output into a first-class scheduled post you can also create directly. A scheduled post auto-publishes at its time. Post statuses:
| Status | Meaning |
|---|---|
draft | Created, not yet ready |
generating | Async media (e.g. video) in flight |
ready | Media in, awaiting your review (campaign posts stop here) |
scheduled | Approved/scheduled — auto-publishes when due |
published | Live on the platform |
failed | Publish failed |
One cron drives both: it generates the next campaign batch and publishes any scheduled post whose time has come (recurring posts clone their next occurrence). The dashboard surfaces this as a FullCalendar view in the “Calendar” tab.
3. Automations
From Self-Serve you also browse the Automations Marketplace, deploy a parameterized n8n workflow in one click, run it, and read its outputs. That flow has its own page — see Automations Marketplace.
4. Analytics
For connected accounts Connect reads back platform analytics through Postiz and surfaces them as KPIs:
- Impressions
- Engagement
- Followers
These are pulled best-effort from the Postiz analytics endpoint; when Postiz is unreachable the workspace degrades gracefully (you keep your calendar and drafts, the KPI tiles simply show zero).
Status: the social control plane, campaign generation loop, calendar, and the OIDC bridge are working. Deeper per-platform analytics ingestion is planned (it rides on the in-house Connections work in the social-engine roadmap).