Integration boundaries
Explore the channels. Keep your accounts out of the demo.
Seven recognizable platform contexts, one simulated workspace. Connections here change saved demo state—not permissions, OAuth tokens, or anything on your social accounts.
A channel directory,
with the limits included.
All channels below are simulated. Caption limits are application rules for this demo, not a guarantee of the latest platform API capabilities.
| Sample channel | Demo caption limit | What to evaluate | Connection status |
|---|---|---|---|
| 2,200 characters | Video metadata, explicit audience, interaction choices, music consent, and commercial disclosure. | Simulated only | |
| 2,200 characters | Prepare a caption and visual content plan; no media is uploaded to Instagram. | Simulated only | |
| 280 characters | Compose concise text within the demo caption limit; no thread delivery or API access. | Simulated only | |
| 3,000 characters | Plan professional content and its review; no member or organization permissions requested. | Simulated only | |
| 5,000 characters | Plan video content and captions; no upload, channel authorization, or live analytics. | Simulated only | |
| 5,000 characters | Explore content preparation; no Page token, Page selection, or actual posting. | Simulated only | |
| 500 characters | Prepare a short-form post; no account authorization or live thread delivery. | Simulated only |
Platform names and marks identify the context of sample content. They do not imply affiliation, approval, or a live integration.
Connection lifecycle
Disconnect should stop the plan. Not erase the work.
Disconnecting a demo channel moves its unpublished reviewed, approved, and scheduled content back to draft and clears schedules. Draft content and published history remain.
Reconnect when you are ready to continue. Each affected post needs a fresh review and schedule; reconnection does not restart the queue.
Real accounts are different.
There is no OAuth flow in the public demo. A connect action cannot access a real account, and a disconnect action cannot revoke an existing platform grant.
If you need to remove a real app authorization, use that platform’s account settings. Our deletion guide explains the distinction between demo data and external permissions.
Read disconnect & deletion guidanceTikTok decisions stay explicit.
The demo models consent-sensitive steps without posting a video. These are sample constraints; a live integration must fetch current creator information and respect platform review requirements.
- 01 / Media
Preview your source.
Use the sample video or a local MP4/WebM up to 100 MB. Demo duration must be readable, greater than zero, and no more than 180 seconds.
- 02 / Audience
Choose who sees it.
Privacy has no preselected value. Comments, duet, and stitch begin disabled, leaving the decision to the creator.
- 03 / Disclosure
Make the relationship clear.
Identify promotional or branded content. Branded content cannot use private visibility; the demo does not silently change the audience.
- 04 / Consent
Review before proceeding.
Confirm music rights and applicable policy terms. A saved plan is still only a plan; a demo publish never uploads the video.
What a live integration would need.
Do not treat a familiar logo as proof of production readiness. Any live rollout needs separately implemented and reviewed account authorization, provider approvals, token handling, and operational safeguards.
- Authorization: provider-supported OAuth, least-privilege scopes, consent, and revocation handling.
- Delivery: current media constraints, rate limits, idempotency, retries, and a visible failure policy.
- Governance: data retention, account ownership, access review, and platform-policy compliance.
- Evidence: confirmed provider access and end-to-end tests before describing a channel as live.
Test the workflow. Not your account credentials.
Try the full workflow in your own temporary workspace. No social account, payment details, or real content required.