Skip to main content

Documentation Index

Fetch the complete documentation index at: https://documentation.outpost.pub/llms.txt

Use this file to discover all available pages before exploring further.

Your Ghost site handles Stripe billing natively — members subscribe and pay through Ghost’s built-in Stripe integration. Outpost connects to that same Stripe account to read subscription data and power its retention, segmentation, and automation tools.

​
Prerequisites

  • A Stripe account already connected to your Ghost site
  • Owner or admin access to the Stripe account

​
Setup

The easiest way to connect is during the Outpost signup flow — the connection wizard walks you through it after Ghost is connected. If you’re connecting after initial setup, go to Integrations and Core Connections → Core Connections in Outpost.
1

Start the Stripe connection

Click Connect To Stripe. You’ll be redirected to Stripe’s authorization page.
You can also skip the Stripe connection during signup and connect later from Core Connections. Stripe is required for subscription automation and retention features, but not for basic member management.
2

Authorize Outpost in Stripe

On the Stripe authorization page, select the Stripe account your Ghost site uses and approve the connection. You never need to copy API keys manually.
3

Outpost finishes setup

After authorization, Outpost configures itself to receive subscription and payment updates from Stripe. You don’t need to set anything up manually in your Stripe dashboard.
You don’t need to configure anything manually in Stripe. Outpost handles it when you authorize the connection.
The Failed Payment Flow requires Stripe’s billing self-serve customer portal. Most current Stripe accounts have this enabled by default; some legacy accounts don’t. If the Failed Payment Flow shows an error about Stripe Billing, enable the customer portal in your Stripe dashboard under Settings → Billing → Customer portal.

​
How billing works

Billing flows between Stripe and Ghost directly — Outpost reads that data to power its tools:
  1. A member subscribes via your Ghost site’s Stripe checkout
  2. Stripe creates the subscription and notifies Ghost
  3. Ghost activates the member’s tier access
  4. Outpost receives the same update from Stripe and refreshes the member’s data
  5. Outpost uses this data to trigger email flows, update segments, and drive retention automation

​
What Outpost uses Stripe data for

Stripe UpdateWhat Outpost does
New subscriptionTriggers welcome flow, updates member status
Subscription changedUpdates tier and renewal date for segmentation
Subscription cancelledTriggers cancellation/win-back flow
Payment succeededConfirms renewal, extends retention window
Payment failedStarts the Failed Payment Flow sequence
Checkout completedTracks conversion from offers and CTAs
Refund issuedUpdates member subscription state to reflect the refund
Chargeback / disputeLogs the dispute and updates the member’s subscription record
Customer payment method updatedStops in-progress dunning and triggers the Failed Payment Flow thank-you action

​
Troubleshooting

Try again from Integrations and Core Connections → Core Connections. Make sure you’re authorizing with the same Stripe account your Ghost site uses. If you have multiple Stripe accounts, select the correct one when approving the connection.
The connection may have been interrupted. Go to Core Connections and disconnect then reconnect Stripe — Outpost will restore the sync automatically.
No. Outpost must be connected to the same Stripe account your Ghost site uses. This is how Outpost matches Stripe subscription events to Ghost members.

Stripe Integration

Full details on the Stripe integration, webhook events, and settings.

Failed Payment Flow

Automatic dunning sequence for failed subscription renewals.

Offers & Discounts

Create promotional pricing powered by Stripe coupons.