Social Engine Setup — Supabase Migrations

This tool requires backend setup before it works end-to-end. The UI tabs (Overview / Calendar / Compose / Analytics) read from Supabase tables defined in the migration below. Without the migration applied + edge functions deployed + admin user logged in, the tabs render but show empty states or auth errors. Use this page to set them up.

Step 1

Apply the Supabase migration

Run migrations/66_social_engine_foundation.sql against your Supabase project. It creates the social_accounts, social_posts, social_post_targets, social_metrics, and social_attribution tables plus indexes and RLS policies.

supabase db push migrations/66_social_engine_foundation.sql

Or paste the SQL directly into the Supabase SQL editor.

Step 2

Deploy the edge functions

Three Deno-based edge functions handle publishing, metrics, and attribution:

social-publisher — posts to FB/IG/LinkedIn/TikTok
social-metrics-pull — daily snapshot of impressions/clicks per post
social-attribute-signup — links inbound signups to UTM campaign

Deploy via:

supabase functions deploy social-publisher
supabase functions deploy social-metrics-pull
supabase functions deploy social-attribute-signup

Set the SOCIAL_TEST_MODE secret to TRUE initially — the publisher logs only and never posts until that flag is flipped.

Step 3

Connect at least one network

Insert a row into social_accounts with the platform handle, OAuth tokens, and publish_enabled = true. The Overview tab pulls connection state from this table.

Step 4

Import the content calendar

The starter calendar (03-CONTENT-CALENDAR.csv) has 60+ pre-written posts across EN/DE/ES/FR/IT/PT. Use the Import CSV button on the Overview tab to load them as drafts, then schedule from Calendar.

Source files