Skip to main content

Onboarding and Configuration

When you first log in, Reactor walks you through a workspace setup flow. This page explains each step and all available configuration options.

Workspace setup

Step 1: Workspace name

Give your workspace a short name. This is used in the UI and in MCP tool responses.

Step 2: Product description

Write a concise description of what your product or company does. This is injected into every content generation prompt as grounding context. Be specific -- include what you make, who uses it, and what problem you solve.

Step 3: Target audiences

Define up to four audience segments (primary, secondary, tertiary, niche). Each audience has:

  • Name -- e.g. "Startup founders"
  • Description -- pain points, goals, what they care about
  • Platforms -- where this audience spends time

Audience data shapes how the AI frames content for each channel.

Step 4: Channel selection

Check the channels you plan to publish on. Available channels:

  • X (Twitter)
  • LinkedIn
  • Blog (via Webflow or Ghost)
  • Newsletter (via Beehiiv or ConvertKit)
  • Discord
  • YouTube
  • Instagram
  • Reddit

You can change this later in engine config.

Step 5: Reference documents (optional)

Upload any documents you want the AI to reference when generating content: product specs, past blog posts, brand voice guidelines, messaging frameworks, FAQ documents. Supported types: PDF, DOCX, TXT, Markdown.

Environment variables

Required

VariableDescription
DATABASE_URLPostgreSQL connection string
NEXTAUTH_SECRET32+ character random string
NEXTAUTH_URLFull base URL including protocol
OPENAI_API_KEYOpenAI API key for generation

Publishing integrations

VariableDescription
TWITTER_CLIENT_IDX (Twitter) OAuth 2.0 client ID
TWITTER_CLIENT_SECRETX (Twitter) OAuth 2.0 client secret
LINKEDIN_CLIENT_IDLinkedIn OAuth 2.0 client ID
LINKEDIN_CLIENT_SECRETLinkedIn OAuth 2.0 client secret
DISCORD_BOT_TOKENDiscord bot token
WEBFLOW_CLIENT_IDWebflow OAuth client ID
WEBFLOW_CLIENT_SECRETWebflow OAuth client secret

Analytics integrations

VariableDescription
GOOGLE_SERVICE_ACCOUNT_EMAILGoogle service account for GA4 and GSC
GOOGLE_SERVICE_ACCOUNT_KEYBase64-encoded private key

Cron security

VariableDescription
CRON_SECRETBearer token used to protect cron endpoints

Set this in Vercel's environment variables and in your vercel.json cron configuration.

MCP

VariableDescription
MCP_API_KEY_HASHSHA-256 hash of your MCP API key

See Authentication for how to generate an API key.

After onboarding

Once setup is complete you land on the Reactor dashboard. From here:

  • Go to Settings > Connections to authenticate publishing channels
  • Go to Settings > Data Sources to connect analytics platforms
  • Go to Settings > API Keys to generate an MCP API key