FlowsMotion — Facebook Video Automation

Client Requirements & Go-Live Checklist for the automated download → publish pipeline

n8n · NocoDB · MinIO · NCA Toolkit · Meta Graph API

Blocking — must have to publish Required data entry Confirm / decide Already done

🔴 Blocking — Facebook credentials

Required 1. Facebook Page Access Token (long-lived)

Must be a Page token (not a user token). Required permissions: pages_manage_posts, pages_read_engagement.
Recommended: generate via a Meta Business Manager System User → token is effectively non-expiring. A normal "long-lived" token expires in ~60 days and will silently break the scheduler.
Paste the token into the NocoDB facebook_pages table → access_token column.

Required 2. Facebook Page ID(s)

The numeric Page ID for each page to post to (e.g. 123456789012345).
Goes in facebook_pages.page_id. The publish workflow posts to graph.facebook.com/v19.0/{page_id}/videos.

Required 3. Meta App configuration

A Facebook App must exist and the Page connected to it (or use a System User from Business Manager).
App should be Live, or the token owner must own the target page (dev mode works for owned pages).

🟠 Required data entry — `facebook_pages` table

The Publish Scheduler looks up the page by the name you type into the Add-Video form's "Target Facebook Page" field. So at least one row must exist:

Column	Example	Notes
`page_name`	`My Brand Page`	Must exactly match what you type in the form
`page_id`	`123456789012345`	from item #2 above
`access_token`	`EAAB…`	from item #1 above
`status`	`Active`	workflow skips `Inactive` pages

Without this row, the scheduler finds the video "due" but the page lookup returns nothing → publish fails.

🟡 Confirm / decide

4. MinIO bucketWorkflows reference bucket flowsmotion-fb. Usually auto-created on first S3 upload; if MinIO policy blocks auto-create, create it in the MinIO console. 5. TimezoneHardcoded to Asia/Karachi (PKT) per spec. Confirm or tell us the real target timezone. 6. YouTube as sourceThis server's IP is 403-blocked by YouTube (Google bot protection). For YT URLs we need a yt-dlp PO Token, or accept TikTok / Instagram / Facebook / direct-MP4 only. 7. Content rightsYou must own or have rights to publish the videos. Meta flags/bans accounts for repeated copyright strikes.

🟢 Already done (no action needed)

✅ NocoDB base flowsmotion_fb + 4 tables (verified read/write): videos, facebook_pages, schedule_templates, logs
✅ Downloader service on NCA Toolkit (/v1/download) — works for TikTok / IG / FB / direct MP4
✅ MinIO S3 credential + n8n NocoDB token credential wired into workflows
✅ 3 workflows built & active: Download Worker, Publish Scheduler (PKT), Add-Video Form
✅ Retry logic (max 3 attempts, then Failed) + logging schema

☁️ Cloudflare Pages — hosting requirements

To host this requirements page (and any future client-facing front-end) on Cloudflare Pages, the following is needed:

Item	Required for	Owner
Cloudflare account ID	Create/manage the Pages project	Client / us
Cloudflare API token with `Account > Cloudflare Pages > Edit` permission	Programmatic deploy (wrangler / direct upload)	Client / us
Pages project (e.g. `flowsmotion-requirements`)	Deployment target	Created on first deploy
Custom domain (optional): `requirements.flowsmotion.com`	Pretty URL	DNS in Cloudflare
Build setting: `framework = none`, build output `/` (static HTML)	Static site	—

This page is a single self-contained index.html — no build step, no dependencies. Deploy is one command once the token exists.

To go live, send us:

Page Access Token(s) — System-User preferred
Page ID(s)
Confirmation on items #4, #5, #6 above

Once we have the token + page ID, we populate the facebook_pages row, run one live end-to-end test (download a sample → upload to your real Page), and confirm the post appears. For the public requirements page on Cloudflare Pages, we also need the Cloudflare account ID + API token (or we hand you the file for one-click deploy).