Contacts
Capture, import, and maintain the contact database that you will later segment and target.
CSV Upload + Field Mapper
Column Mapping
| CSV Column | Include | Target Key | Type | DB Status | Create Field | Options (comma-separated) |
|---|
| First Name | Last Name | Company | Website | Youtube |
|---|
Add Contact
Explore Contacts
Filter contacts by any visible field, sort by any column, then save a segment definition.
Record Count: 0
Segments
View, edit, and manage all saved segments.
Segment Editor
Campaigns
Assemble channels, audiences, messaging, assets, and build components into deployable campaigns.
Channel Field Rules
Choose a channel, then define which fields are shown and which mechanics fields are required.
Visible Mechanics
Required Mechanics
Visible Content
Saved Campaigns
| Actions |
|---|
Acquire
Acquire pulls source material into APP from web and platform channels before it is organized into contacts, messaging, and assets.
Acquisition Hub
APP
Acquire: Web
Capture source material and structured data from websites before organizing it into contacts, messaging, and assets.
Existing Jobs
| Job ID | Stage | URL | Updated | Actions |
|---|
Direct Ingest (No Workflow)
Use this to directly fetch and parse website pages now. It bypasses create/approve/execute workflow.
Direct Ingest Runs
| Run ID | Source | Succeeded | Failed | Finished |
|---|
Parsed Pages
| URL | Title | Emails | Phones | Snippet |
|---|
{}
Advanced: Request/Response JSON
Request Preview
{}
Response
{}
Acquire: YouTube
Acquire data from a YouTube video page and extract description, hashtags, playlists, and transcript.
YouTube Acquire Runs
|
|
|||||||
|---|---|---|---|---|---|---|---|
| Created | Video Title | Channel | Category | Tags | Transcript | Actions |
Video Details
-
Description
No video loaded yet.
Hashtags
-
Transcript
No transcript loaded yet.
Comments
No comments loaded for this video.
Advanced: Raw YouTube JSON result
{}
Edit YouTube Run
Bulk Edit YouTube Runs
No runs selected.
YouTube Comments
-
|
|
Showing: 0 | |||||
|---|---|---|---|---|---|---|
| Date | Video Title | Author | Comment | Type | Likes | Replies |
YouTube Categories
| Actions |
|---|
Create YouTube Category
Edit YouTube Category
Acquire: Instagram
Instagram acquire module placeholder.
Acquire: Tiktok
Tiktok acquire module placeholder.
Acquire: Facebook
Facebook acquire module placeholder.
Acquire: X
Harvest recent X posts by query/hashtags, optionally include replies, and store runs for later analysis.
X Harvest Runs
| Run ID | Created | Query | Posts | Replies | Errors | Actions |
|---|
Run Detail
| Type | Tweet ID | Author | Created | Text |
|---|
{}
Acquire: Reddit
Provide a subreddit link/name or specific post link. APP will harvest posts (and comments for post mode) and store runs for later analysis.
Reddit Harvest Runs
| Run ID | Created | Mode | Target/Subreddit | Posts | Comments | Actions |
|---|
Run Detail
| Type | ID | Author | Score | Text/Title |
|---|
{}
Acquire: Quora
Quora acquire module placeholder.
Acquire: Substack
Substack acquire module placeholder.
Acquire: Medium
Medium acquire module placeholder.
Promote
Promote is the outbound scheduler and coordination layer. Use it to send campaigns out across channels, queue delivery, and manage timed release activity.
Engage
Engage is the response layer. Use it to review inbound replies, comments, and follow-up conversations generated by your promotions.
Engage: Inbox
Unified response inbox placeholder.
Engage: Email
Email response workspace placeholder.
Engage: Social
Social response workspace placeholder.
Engage: Messages
Direct message response workspace placeholder.
Engage: Comments
Post a comment to a Reddit discussion by providing a post/comment URL or a Reddit thing ID.
{}
Engage: Discussion
Threaded discussion response workspace placeholder.
Promote: Email
Select an unsent email campaign, set delivery details, then send immediately or schedule delivery.
{}
Promote: Social
Build a social drop from a Social campaign, choose platforms, review/edit each platform draft, then queue or publish.
Publisher Status
Social Platforms
Queue & History
{}
| Platform | Status | Scheduled | Published | Post | Remote ID | Actions |
|---|
Promote: Messaging
Messaging promotion module placeholder.
Promote: Comments
Comments promotion module placeholder.
Promote: Discussion
Discussion promotion module placeholder.
Promote: Streaming
Streaming promotion module placeholder.
Promote: Podcasts
Podcasts promotion module placeholder.
Messaging
Messaging organizes reusable copy into shared categories and a structured content library for campaigns, pages, and engagement.
Content
Messaging: Content
Use the content library to move between short-form, social, and long-form messaging assets.
Manage Messaging Content
Open a content editor to run full CRUD for that messaging type.
| Type | Family | Editor |
|---|---|---|
| Headlines | Short Form | |
| Sub-headings | Short Form | |
| Taglines | Short Form | |
| Pitches | Short Form | |
| Subject Lines | Short Form | |
| Tweets | Social | |
| Posts | Social | |
| Articles | Long Form | |
| Reports | Long Form | |
| White Papers | Long Form | |
| eBooks | Long Form | |
| Descriptions | Support Copy | |
| Transcripts | Support Copy | |
| Comments | Support Copy | |
| Hashtags | Support Copy | |
| Calls to Action | Support Copy |
Messaging: Content Types
Create a content type by name and family. The app will generate its editor table and add it to Messaging Content automatically.
| Enabled | Actions |
|---|
Messaging: Articles
Saved Articles
| Actions |
|---|
Messaging: Tweets
Saved Tweets
| Actions |
|---|
Messaging: Posts
Post writing workspace placeholder.
Messaging: Pitches
Create, import, edit, and organize reusable pitches that can later be assigned to campaigns and other messaging workflows.
Saved Pitches
| Actions |
|---|
Bulk Edit Pitches
No pitches selected.
Messaging: Comments
Comment writing workspace placeholder.
Messaging: Hashtags
Hashtags By Campaign
Messaging: Headlines
Create, import, edit, and organize reusable headlines that can later be assigned to campaigns and other messaging workflows.
Saved Headlines
| Actions |
|---|
Bulk Edit Headlines
No headlines selected.
Messaging Categories
Choose a category to open the content library in that category context, or use Manage Categories to edit the category list.
Manage Messaging Categories
| Actions |
|---|
Create Messaging Category
Edit Messaging Category
Messaging: Sub-headings
Create, import, edit, and organize reusable sub-headings that can later be assigned to campaigns and other messaging workflows.
Saved Sub-headings
| Actions |
|---|
Bulk Edit Sub-headings
No sub-headings selected.
Messaging: Taglines
Create, import, edit, and organize reusable taglines that can later be assigned to campaigns and other messaging workflows.
Saved Taglines
| Actions |
|---|
Bulk Edit Taglines
No taglines selected.
Messaging: Reports
Saved Reports
| Actions |
|---|
Messaging: White Papers
Saved White Papers
| Actions |
|---|
Messaging: eBooks
Saved eBooks
| Actions |
|---|
Messaging: Descriptions
Description writing workspace placeholder.
Messaging: Transcripts
Transcript writing workspace placeholder.
Messaging: CTAs
CTA writing workspace placeholder.
Assets
Assets organizes reusable media and PDFs. Start with an asset type or jump straight into a category-specific library view.
Asset Types
Categories
Manage Assets
Manage the reusable media and PDFs that support campaigns, pages, and publishing.
Add Single Asset
Add Multiple Assets
|
|
|||||||
|---|---|---|---|---|---|---|---|
| Thumbnail | Actions | ||||||
Add Asset
Asset Categories
Choose a category to open the asset library filtered to that category.
Manage Asset Categories
| Actions |
|---|
Create Category
Edit Category
Assets: Images
Images module placeholder.
Assets: Video
Video module placeholder.
Assets: Audio
Audio module placeholder.
Channels
Define the publishing and outreach destinations where campaigns and engagement will run.
| Channel | User Name | Password | Actions |
|---|
Add Channel
Edit Channel
Builder
Build the reusable infrastructure layer: templates, forms, pages, extension tools, and agents.
Builder: Themes
Create reusable named themes and persist color, style, and asset settings in Supabase.
Theme Builder
Palette
Styles
1
12
0
0
Assets
Preview
Theme Library
| Feature Image | Logo Square | Name | Palette | Styles | Updated | Actions |
|---|
Consolidation Targets
| Area | Current Controls | Persistence | Target Consolidation |
|---|
Builder: Pages
Manage saved page definitions, filter the library, sort columns, and edit records in bulk.
| Actions |
|---|
Bulk Edit Pages
No pages selected.
Create Page
Page Preview
Visual Page Editor
Click any highlighted element to open an inline editor next to that item. You can leave multiple editors open, then save all changes together.
Thank You
Builder: Forms
Assemble reusable forms from a form template, PDF, CTA, and confirmation behavior. Save them for use throughout the platform.
Create Form
Form Preview
Saved Forms
| Actions | |||||||
|---|---|---|---|---|---|---|---|
| No saved forms yet. | |||||||
Builder: Agents
Use OpenClaw job actions directly, or launch the API Setup Orchestrator agent preset for cross-channel provider onboarding.
Request Preview
{}
Response
{}
Agent: API Setup Orchestrator
Run the orchestrator from Builder and track setup progress across all Promote channels.
No orchestrator run loaded.
Latest Run Summary
| Channel | Provider | Configured | Manual Steps | Actions |
|---|
| Phase | Agent-Owned Work | Human-Minimum Work | Output |
|---|---|---|---|
| Inventory | Scan provider schemas, current config completeness, and channel readiness. | None | Channel readiness matrix with missing fields. |
| Preflight | Generate exact per-provider forms/checklists and validation tests. | None | Actionable setup packet per channel. |
| Credential Capture | Validate formatting, normalize endpoints, and stage secure storage plan. | Obtain external credentials/tokens where provider requires human login/2FA/captcha. | Credential intake checklist and status. |
| Verification | Run status and smoke checks, classify failures, propose remediation. | Approve/retry when provider-side approval gates are present. | Pass/fail diagnostics + next actions. |
| Handoff | Emit final report: ready channels, blocked channels, required human follow-ups. | Execute only unresolved external confirmation steps. | Go-live readiness report. |
Builder: Templates
Manage the reusable structural templates that power forms and pages.
Template Editor
Drag modules to reorder, then select content for each block.
Forms
These are the reusable form templates used as the foundation for saved forms.
Choose an email template type to pair with a theme and campaign delivery.
Pages
Select a reusable page template. The Page Builder uses this same template library.
Builder: Extensions
Browse the extension repository for specialized platform capabilities that do not need to live inside the canonical UI.
Builder: Extension Manager
Maintain a searchable extension repository with recursive parent-child taxonomy, definitions, and descriptive metadata.
| Actions | |||||
|---|---|---|---|---|---|
| No extensions yet. | |||||
Extension: Icon Builder
Icon Builder
Generate a compact icon immediately for a message, asset, campaign, or other system object.
Icon Request Preview
{}
Icon Response
{}
Generated Icon
General Tool Job
Advanced Tool Runner
Run generic internal tool jobs for extension-level operations that do not yet have dedicated UIs.
Request Preview
{}
Response
{}
Extension: Screenshot
Paste a website URL to create a `640x360` screenshot, upload it into Vercel Blob, and store it in Assets as type `Image` with category `Screenshot`.
Screenshot Response
{}
Captured Screenshot
Extension: Thumbnail
Generate an image thumbnail from the first page of a PDF file location, upload it into Vercel Blob, and store it in Assets as type `Image` with category `Thumbnail`.
Thumbnail Response
{}
Generated Thumbnail
Observe
Review outcomes, monitor activity, and analyze performance after campaigns go live.
Observe: Dashboard
Dashboard module placeholder.
Observe: Reports
Reports module placeholder.
Observe: Analysis
Analysis module placeholder.
Activity Log
—
⏳
No activity recorded yet. Actions you take in the platform will appear here.
Documentation
This section is the system manual for the Alphire Promo Platform. The process map below mirrors the operating flow: acquire inputs, organize people and reach paths, prepare message and assets, build campaign infrastructure, execute, and then observe the result. Each stage links directly to its documentation page.
→
→
+
→
→
→
System Support
Workflow
End-to-End Sequence
- Acquire gathers raw source material and structured scrape results.
- Contacts converts records into a reusable audience database and saved segments.
- Messaging, Assets, and Develop create the copy, media, pages, forms, and operational payloads that campaigns depend on.
- Campaigns assembles those reusable pieces into launch-ready records for outbound execution.
- Engage and Observe handle publishing, response, reporting, and audit visibility after launch.
Shared Patterns
How The UI Behaves
- Each top-level menu can open a dedicated page or a submenu page that focuses on one workflow.
- Most modules use in-page forms for create or update operations and tables for the saved records.
- Several operational actions require a manual confirmation checkbox before an API request can be sent.
- The app keeps the active page in browser storage so the same workspace view reopens on refresh.
Core Data
System Building Blocks
- Contacts and segments are the shared audience primitives reused across campaigns.
- Campaigns reference assets, messaging entries, pages, forms, and channels instead of duplicating them.
- Settings centralizes database credentials, API providers, agent configuration, and environment variables.
- Activity Log in Observe acts as the operational audit trail across multiple modules.
Docs: Acquire
Acquire is the intake layer. It captures external source material before that data is normalized into contacts, messaging ideas, or reusable internal records.
Main Acquire Workspace
- The main Acquire page supports the full job lifecycle: `create_job`, `preview_job`, `approve_job`, `execute_job`, and `job_status`.
- Operators can define source URLs, paging depth, snippet size, request metadata, and an approval decision before sending the request.
- Manual confirmation is required for API execution-sensitive actions.
- The jobs table provides a live list of saved acquire jobs with stage, source URL, timestamps, and action controls.
Direct Ingest
- Direct Ingest bypasses the approval workflow and runs an immediate page fetch plus parse operation.
- Inputs include one source URL, a page cap, a body snippet length, and a separate manual confirmation checkbox.
- The interface stores and displays completed ingest runs with success and failure counts.
- Parsed Pages output lists page titles, extracted emails, extracted phones, and a snippet preview for quick review.
Channel-Specific Acquisition
- YouTube has a dedicated submenu page and a linked comments view, making it the most developed source-specific acquisition connector in the current UI.
- Instagram, TikTok, Facebook, X, Reddit, Quora, Substack, and Medium each have reserved acquire pages for future source-specific implementations.
- The current structure makes Acquire the staging area for expanding new acquisition connectors without changing the top-level navigation model.
Operational Output
- Advanced request and response JSON is exposed for inspection, which is useful for debugging workflow payloads.
- Acquire output is intended to feed later workflows such as contact import, asset collection, and messaging development.
Docs: Contacts
Contacts is the system of record for people and organizations. It supports direct data entry, CSV import, filtering, and segment creation for downstream targeting.
Contacts Grid
- The default Contacts page lists records with searchable columns for name, company, email, website, YouTube, and Instagram.
- Top actions open inline flows for adding a contact, importing CSVs, or moving into the exploration workflow.
- This page acts as the primary maintenance surface for the audience database.
Add Contact
- The add form supports both core identity fields and a broad set of social or publishing URLs.
- Supported channels include website, YouTube, Instagram, TikTok, Facebook, X, BlueSky, Substack, Medium, and LinkedIn.
- That structure makes the contact record useful as both a person record and a creator or brand profile.
CSV Import And Mapping
- CSV upload analyzes headers before import instead of forcing a blind upload.
- The mapper allows per-column inclusion, target-key selection, type assignment, database status checks, and optional field creation.
- A generated SQL helper can surface missing schema work before importing into `promo_leads`.
Explore And Segments
- Explore Contacts adds broader filtering, sorting, record counts, and an inline save-to-segment action.
- The Segments page is the reusable audience view for working with saved segment definitions and their resulting records.
- Segments are shared dependencies for Campaigns and other targeting workflows.
Docs: Messaging
Messaging is the copy library. It organizes reusable content blocks by format so campaigns, pages, and publishing workflows can assemble messaging without rewriting from scratch.
Content Types
- The module is organized into dedicated pages for Headlines, Sub-headings, Taglines, Pitches, Tweets, Posts, Articles, Descriptions, Transcripts, Comments, Hashtags, and Calls to Action.
- The main Messaging page serves as a launcher into those specialized content libraries.
- This structure is designed to keep copy modular so the same campaign can mix short-form and long-form assets.
Implemented Content Workflows
- Articles, Tweets, Posts, Pitches, Comments, Hashtags, Headlines, Sub-headings, Taglines, Descriptions, Transcripts, and CTAs all have dedicated page shells with back-navigation into the core library.
- The Articles and Tweets pages are the most substantial message-specific surfaces in the current interface.
- Hashtags are exposed as reusable grouped assets for campaign assembly and social publishing support.
System Role
- Campaigns reference message records such as headlines, taglines, pitches, tweets, and CTAs.
- Develop reuses messaging pieces when building pages and other conversion surfaces.
- Engage can use stored social copy so outbound publishing stays consistent with campaign definitions.
Docs: Assets
Assets manages the media library used across campaigns, pages, and publishing. It combines upload flows, categorization, filtering, and preview tools in one workspace.
Library And Filtering
- The main Assets table supports filtering by asset name, type, category, and tags.
- Visible rows can be selected in bulk, enabling future bulk edit and delete actions when multiple assets are in focus.
- Asset records store type, category, tags, size, and action controls.
Upload Workflows
- The Add Assets panel supports both single-file and multi-file uploads.
- Assets can be typed as Image, Video, Audio, or PDF before upload.
- The current upload action is wired around Vercel Blob as the storage destination.
Asset Editing And Preview
- The Add Asset page doubles as the asset edit surface with fields for name, type, category, and tags.
- The preview panel can render image, video, audio, iframe, and text-based preview states.
- Metadata such as file location, size, and dimensions is surfaced when available.
Categories And Type Shortcuts
- The Categories page manages category taxonomies per asset type.
- Dedicated create and edit pages support asset-category administration.
- Image, Video, and Audio submenu pages are currently type-specific entry points reserved for specialized views.
Docs: Channels
Channels stores the destinations where campaigns and outbound actions will run. It is the credential registry for account-level publishing and outreach targets.
Channel Registry
- The main Channels page lists each saved channel with channel name, user name, email, password field, and actions.
- This gives operators one place to audit which outbound accounts are configured.
- Campaigns reference these channel records to define where a campaign runs.
Create And Update
- The create flow collects channel name, user name, email, and password.
- The edit flow preserves the current password unless a replacement value is entered.
- The page design implies channels are durable managed resources rather than one-off campaign settings.
Operational Role
- Channels are prerequisites for campaign assembly and future multi-channel engagement features.
- The Engage social workflow currently focuses on X, but Channels provides the generalized abstraction for more destinations.
Docs: Develop
Develop is the build layer. It creates the campaign infrastructure that sits between strategy and execution: pages, forms, templates, agents, and internal tool jobs.
Pages
- The page builder combines templates, form selections, PDFs, messaging, and branded media into one page payload.
- Operators can set primary, background, and accent colors directly in the builder.
- The builder preview exposes the assembled configuration before use elsewhere.
Forms And Templates
- The form builder supports squeeze, short, and long form variants with configurable labels, colors, and required fields.
- Saved forms are listed in a reusable table, making them available to pages and campaigns.
- The Templates page provides a reusable page template library plus a preview host.
Agents
- The Agents page exposes operational agent actions including `create_job`, `preview_job`, `approve_job`, `execute_job`, and `job_status`.
- It includes request and response previews so operators can inspect exact payloads sent to the agent backend.
- Manual confirmation is required before sending sensitive agent actions.
Extensions
- The Extensions page includes specialized extension utilities such as Icon Builder, plus a generic tool job runner for custom internal operations.
- Icon Builder packages object details into a graphics-generation request so a small icon can be created for platform objects and navigation markers.
- Tool execution is driven by either a guided form or a selected tool name plus JSON input, keeping the interface flexible for new operations.
Docs: Campaigns
Campaigns is the assembly layer. It turns reusable records from other modules into deployable campaign definitions.
Mechanics
- Campaign setup starts with a campaign name and a required channel selection.
- Optional mechanics include segment, page, form object, and PDF references.
- This separation keeps delivery mechanics distinct from content choices.
Content Assembly
- Campaign content can attach a headline, blurb, pitch, tweet, CTA, primary image, primary video, and hashtag group.
- Most selectors are intentionally wired to reusable library records from Messaging and Assets.
- The campaign form is effectively the composition surface for a multi-module promotion package.
Saved Campaigns
- Saved campaigns are shown in a tabular registry with key fields visible for quick auditing.
- The page is designed to help operators compare campaign definitions before activation in Engage.
Docs: Engage
Engage is the execution layer. It is where campaigns are turned into outbound actions and channel-specific publishing workflows.
Engage Overview
- The Engage top-level page frames outbound publishing, replies, and activation work after campaigns are assembled.
- Submenu pages exist for Email, Social, Messaging, Comments, Discussion, Streaming, and Podcasts.
- This keeps the top-level model broad enough for both direct outreach and public-channel execution.
Social Publishing
- Engage: Social is an implemented queueing workflow focused on X.
- Operators can compose posts, schedule optional publish times, monitor a character counter, queue content, or publish immediately.
- A queue snapshot tracks scheduled, failed, and published counts plus connected account status.
- The `Publish Due Posts` action flushes posts that are due now or overdue.
Execution Role
- Engage consumes campaign definitions, channel credentials, and messaging assets rather than creating those records itself.
- The non-social submenu pages are currently reserved for future workflow-specific implementations.
Docs: Observe
Observe is the reporting and oversight layer. It is intended to answer what happened after outreach, publishing, and campaign execution.
Core Views
- The Observe menu is organized into Dashboard, Reports, Analysis, and Activity Log.
- Dashboard, Reports, and Analysis are current placeholders reserved for performance and analytics surfaces.
- The navigation already separates real-time monitoring from structured reporting and deeper interpretation.
Activity Log
- Activity Log is the implemented operational audit view.
- Operators can filter by action family, view counts, refresh manually, and review the log grid in one place.
- Supported filter groups include contacts, segments, campaigns, settings, OpenClaw, and acquire actions.
System Role
- Observe is the natural destination for future metrics tied to campaigns and engagement outcomes.
- It closes the loop by providing oversight after the system moves from build to execution.
Docs: Settings
Settings centralizes platform configuration. It is the administrative layer for identity, infrastructure, provider access, and system-level credentials.
General Structure
- The Settings menu includes Profile, Agents, Database, APIs, and Env Config.
- The top-level Settings page itself is currently a placeholder, while the submenu pages hold the operational settings workflows.
Database
- Database settings manage the Supabase project URL, service role key, and the primary table names used by the app.
- This page defines how the frontend points at contacts, contacts-grid, field-config, and acquire-related tables.
APIs And Agents
- API settings store provider credentials through a provider-aware dynamic form.
- The configured providers table exposes status, update timing, and saved values visibility.
- Settings: Agents is reserved for agent-specific platform configuration distinct from the Develop execution console.
Environment Configuration
- Env Config is the infrastructure secret registry and masks sensitive values while showing whether variables are set.
- Changes update runtime environment variables immediately and are designed to sync to Vercel for subsequent deployments.
- This page is the single source of truth for operational credentials used across the platform.
Meta Quickstart (No Guessing)
- Use Graph API Explorer with
GET /me/accountsto list Pages. - Choose the object where
namematches your Page name. - APP Meta > Page ID = that object
id. - APP Meta > Access Token = that object
access_token. pagingin the response is cursor metadata, not Page ID.
Instagram Account ID Mapping
- Run
GET /{PAGE_ID}?fields=instagram_business_account. - APP Instagram > Business Account ID =
instagram_business_account.id. - Instagram posting requires a campaign primary image.
- Default endpoint URL:
https://graph.facebook.com/v22.0.
Meta Family (Facebook, Instagram, Threads)
- Collect App ID and App Secret from Meta Developers.
- Generate User Access Token and long-lived token in Graph API Explorer.
- Capture Page ID and Instagram Business Account ID for IG publishing.
- Use
metafor consolidated setup orinstagram/threadsprovider keys directly.
OAuth Channels (LinkedIn, Pinterest, Reddit, Quora, Patreon)
- Store app client ID/client secret first, then complete OAuth to obtain refresh token.
- For Reddit comments, include a stable user-agent string and refresh token.
- Quora and Patreon provider schemas are available in Settings > APIs; publish routes are still planned.
Token/PWD Channels (Bluesky, Telegram, Substack, Medium, YouTube)
- Bluesky:
identifier+app_password. - Telegram: bot token from BotFather, plus chat ID for posting target.
- Substack and Medium: publication/integration tokens as primary credentials.
- YouTube key is currently used for Acquire workflows; Promote publishing is separate.
Operational Sequence
- Step 1: Save credentials in Settings > APIs.
- Step 2: Run channel-specific status/diagnostics checks.
- Step 3: Execute a one-recipient/one-post smoke test.
- Step 4: Enable campaign-level publishing flow for that channel.
Docs: Platform API Setup
Credential Form
Platform Documentation
Settings
Settings page placeholder.
Environment Configuration
One source of truth for all infrastructure credentials.
Secrets are masked. Changes update process.env immediately
and write to Vercel's environment variables for the next deployment.
Environment Variables
Set Not set| Variable | Value | ||
|---|---|---|---|
| Loading… | |||
Local dev: edit .env (gitignored) and restart the server.
Production: set VERCEL_TOKEN and VERCEL_PROJECT_ID
above to enable automatic Vercel sync, or use the
Vercel CLI:
vercel env add SUPABASE_URL
Settings: Profile
Set the core identity for this workspace, including the project name and the logo shown in the top banner.
Settings: Agents
Agents settings placeholder.
Settings: Database
Database Connection
Field Management
Use the form below to define custom fields for the selected database table.
Available Fields
| Key | Label | Type | Required | Active |
|---|
Settings: APIs
Connection
Loading Connection Ops...
| When | Status | Code | Summary |
|---|
| Code | Likely Cause | Fix | Portal |
|---|
Channel Connections
Click a channel to open its API form. Connection Ops expands for channels that support gate tracking.
| Channel | Core Fields / Saved | Gate 1 | Gate 2 | Gate 3 | Gate 4 | Gate 5 | Actions |
|---|