Skip to main content

Getting Started with Amplicast

Amplicast turns one piece of source content into platform-ready posts across all your social channels, using AI tuned to your brand voice. This guide walks through what you'll see right after signing up.

Quick setup overview​

When you sign up, Amplicast walks you through a 5-step onboarding flow:

  1. Create your first project (new) — the brand or initiative you're publishing for
  2. Sources — where the raw content comes from (CDN, Notion, Supabase, RSS, …)
  3. Channels — connect the social accounts you'll publish to
  4. Style — set your brand voice + writing samples
  5. Automation — pick how often Amplicast should run

Each step has Skip for now if you want to come back. Skipped steps appear as crossed-out items on the dashboard's Getting Started checklist so you don't lose track.

Below — what to do at each step and why.

1. Sign up​

Go to app.amplicast.io. Enter your email → check your inbox → click the magic link. Every new account gets a 7-day free trial with full access to all features.

2. Create your first project​

When you land in the onboarding, the first step is Project.

A project is one brand or initiative you publish for. Each project has its own channels, sources, content, and brand voice. You can create more later from the sidebar.

  • Project name — required. Use the brand or initiative name (Acme Main, My Personal Brand).
  • Logo — optional. PNG / JPG / GIF / WebP up to 10 MB. The logo replaces the violet initial square in the sidebar so you can spot the active project at a glance.

Click Create project. The project is now active — every step that follows will be scoped to it. (Switch back to add more later via Project Settings, or skip and come back to it.)

See Projects for the full picture, including renaming, settings, and deletion.

3. Sources​

A source is where raw content comes from before Amplicast transforms it for each platform. Add one or skip — you can always add more later.

Available source types:

  • Supabase / Postgres — connect a database; map the columns containing your content
  • CDN / public bucket (b2_manifest) — a structured folder of JSON + assets on any HTTPS-reachable host
  • Notion — a Notion database
  • GitHub — Markdown files in a repo
  • Web scraper / RSS — pull from URLs or RSS feeds

You can configure per-source:

  • Target platforms — which channels content from this source should go to
  • Publish mode — Autopilot (auto-publish), Review (manual approval), or Draft (save only)

See Content Sources for details, and Manifest + Bible Source for the structured CDN format.

Don't have a content source yet? Skip this step. You can still create posts manually from the Create tab.

4. Channels​

Connect at least one social platform so you have somewhere to publish.

PlatformHow
LinkedInConnect personal profile or company page
InstagramRequires a Business or Creator account connected to a Facebook Page
X (Twitter)Connect your X account
YouTubeConnect your channel for video uploads
TikTokConnect your TikTok account
BlueskyConnect with handle + app password
FacebookConnect a Facebook Page you manage

OAuth handles the authentication for everything except Bluesky. Each connection automatically lands in your active project — so connect channels while the right project is selected in the sidebar.

See Platforms & Channels for per-platform setup notes.

5. Style — brand voice + writing references​

Set the voice the AI should use for this project. Three ways:

  1. Sync from a brand hub — fastest if your brand identity already lives in an external system
  2. Paste a brief, let AI extract — paste 1–2 paragraphs describing your brand; the AI fills the 9 structured fields
  3. Fill the form by hand — full control when you want it

This is per-project, so each brand can sound different even in the same workspace. Read Brand Voice for the deep dive.

You can also optionally add:

  • Writing samples (per user) — concrete examples of writing you want the AI to match. Sits alongside brand voice and gets included as examples in every prompt.
  • Reference images (per user) — logos and visual references for AI image generation

6. Automation​

Pick how often Amplicast should run autopilot — daily, 3x per week, weekly, biweekly. You can change this per topic later.

If you're not ready, Skip for now is fine. Autopilot only runs on topics you explicitly create.

7. Done — you're in the dashboard​

After onboarding, you land in the dashboard. The Getting Started checklist on the Overview tab shows the same 5 items so you can finish anything you skipped — items get crossed out as you complete them.

From here, the next thing most people do is:

  • Create your first autopilot topic (Autopilot tab) — Amplicast will generate content matching your project voice on a schedule
  • Compose a manual post (Create tab) — quick way to test the publish pipeline

What's next​

Stuck on something not covered here? Email hi@amplicast.io and we'll help.