Sandbox Automation — Activepieces Clone (Sandbox Only)

Flows

4

FB • IG • TikTok • YT

Runs (sandbox log)

0

stored locally

Success rate

—

simulated

Connections set

0/7

manual tokens

Platform distribution

FB

35%

IG

30%

TT

25%

YT

10%

Same pipeline as your workers: dedupe → store latest → forward to webhook → tables lookup → reply.

Recent runs

How this sandbox maps to Activepieces

Trigger
Catch Webhook (FB Page feed, IG comments, TikTok comment_key)

Step 1 — Code
Extract comment, caption, name, video_id, hashtags, isReel…

Router
REELS vs FEED / fallback photo branch

Delay
90–180s random (human-like)

Tables
Find Records where Caption == {{caption}}

Reply Code
Build Kinyarwanda reply + POST to Graph / TikTok / YT

Flows (4 preloaded from your automations)

instagram commentor

PIECE_TRIGGER → CODE → ROUTER → DELAY → TABLES → CODE

Step inspector

Click a step on the canvas.

Sandbox only: paste test tokens manually. They stay in localStorage key: sandbox_connections on this machine. Nothing is sent anywhere except when you press Test. For production later we will use Cloudflare Workers secrets, not this UI.

Bulk actions

Fields: verify_token • page_id • fb_page_token • ig_token • ig_account_id • fb_webhook • ig_webhook • tiktok_username • tiktok_webhook • youtube_api_key • github_pat • graph_version

Q&A Table Caption → Answer

Lookup simulator (like Tables Find Records)

Incoming caption Operator

—

Webhook tester

Webhook URL (your Activepieces / Worker URL) Payload (JSON)

Response

—

Verify-token & Graph helpers

Verify token (must match Worker VERIFY_TOKEN) Worker base URL (for GET verification)

—

Graph API quick test

—

Runs / Logs (local)

Reply generator (from your flows)

Name Answer Comment

—

Library

Cloudflare — Pages + Workers (frontend first, logic later)

Account ID (from your credentials file — safe to paste here, stays local) Pages project name R2 S3 endpoint (auto-built)

Do NOT paste your API token / R2 secret into this UI. Set them as env vars in your terminal only:
$env:CLOUDFLARE_API_TOKEN="…" (PowerShell) then npx wrangler pages deploy .

Deploy steps (PowerShell)

# 1) one-time: allow scripts + login via token (token stays in terminal, not in code)
# Set-ExecutionPolicy -Scope CurrentUser RemoteSigned
$env:CLOUDFLARE_API_TOKEN="PASTE_TOKEN_HERE_FOR_THIS_SESSION_ONLY"
$env:CLOUDFLARE_ACCOUNT_ID="PASTE_ACCOUNT_ID"

# 2) from this folder:
cd "C:\Users\Herve\Desktop\sandbox-automation-frontend"
npx wrangler pages deploy . --project-name=sandbox-automation

# 3) later when backend logic is added (Workers + KV + R2):
# wrangler kv:namespace create WEBHOOK_KV
# wrangler secret put FACEBOOK_TOKEN
# wrangler deploy

Future backend wiring (kept as placeholders)

functions/api/health.js
already included — test endpoint for Pages Functions

Worker: webhook receiver
will reuse your worker.js: verify → dedupe (KV) → forward

KV: WEBHOOK_KV
processed:{platform}:{id} + latest payload

R2
store logs / table CSV backups via S3 API