Connection Help

Learn how to connect your accounts to publish content across different platforms.

Quick Navigation

BlogSpot BlogSpot WordPress WordPress (Self-Hosted) WordPress.com WordPress.com (OAuth) Medium Medium
API
Custom HTTP
BlogSpot

BlogSpot Connection

To connect your BlogSpot (Blogger) account, you'll need to obtain credentials from Google Cloud Console. Note that BlogSpot is the domain name, while Blogger is the official platform name.

Required Information:

  • Blog ID: Your Blogger blog identifier (long number)
  • OAuth 2.0 Credentials: Client ID and Client Secret for publishing

Step-by-Step Setup:

  1. Find your Blog ID:
    • Go to Blogger Dashboard
    • Select the blog you want to integrate from the left sidebar
    • Look at your browser's address bar - you'll see a URL like: https://www.blogger.com/blog/posts/1234567890123456789
    • The long number after /posts/ is your Blog ID
  2. Create Google Cloud Project:
    • Visit Google Cloud Console
    • Click "Create Project" if you don't have one, name it "Blogger Integration"
    • Select your project from the project dropdown
  3. Enable Blogger API:
    • In the search bar at the top, search for "Blogger API"
    • Select "Blogger API" from the search results
    • Click the "Enable" button
  4. Set up OAuth 2.0 (Required for Publishing):
    • Go to "Credentials" from the left navigation menu
    • Click "Create Credentials" → "OAuth client ID"
    • If prompted, configure the "OAuth consent screen" first (name it "My Blogger App")
    • For application type, select "Web application"
    • Add authorized redirect URIs (your application's callback URL):
      https://app.content-growth.cn/auth/blogspot/callback

      Copy this exact URL into your Google Cloud Console

    • Click "Create" to generate your OAuth credentials
    • Copy your credentials:
      • Client ID: Copy the "Client ID" value (looks like: 123456789-abcdef.apps.googleusercontent.com)
      • Client Secret: Copy the "Client secret" value (looks like: GOCSPX-abcdef123456)
      • Store these securely - you'll need both for the connection setup
  5. Test the connection:
    • Enter your Blog ID and OAuth credentials in the connection form
    • Click "Test Connection" to verify the setup
    • You may need to authorize the application during the first connection

Important: An API key alone only allows reading public data. To publish posts automatically, you must use OAuth 2.0 credentials which allow your application to act on your behalf after you grant permission.

Note: Keep your API key secure and never share it publicly. If compromised, revoke it immediately and generate a new one.

WordPress

WordPress (Self-Hosted) Connection

Connect your self-hosted WordPress site or WordPress.com paid plan using Application Passwords for secure authentication.

Required Information:

  • Site URL: Your WordPress site URL (e.g., https://yourblog.com)
  • Username: Your WordPress admin username
  • Application Password: Generated from WordPress admin

Step-by-Step Setup:

  1. Log into WordPress Admin:
    • Go to your WordPress admin dashboard (usually at https://yoursite.com/wp-admin)
    • Log in with your admin credentials
  2. Navigate to Your Profile:
    • Click on "Users" → "Profile" in the left sidebar
    • Or go directly to https://yoursite.com/wp-admin/profile.php
  3. Generate Application Password:
    • Scroll down to the "Application Passwords" section
    • Enter a name for the application: "Content Growth"
    • Click "Add New Application Password"
    • Copy the generated password immediately (format: xxxx xxxx xxxx xxxx xxxx xxxx)
    • Important: You won't be able to see this password again!
  4. Configure the Connection:
    • Enter your WordPress site URL (with https://)
    • Enter your WordPress username (not email)
    • Paste the Application Password (include spaces or remove them - both work)
    • Click "Test Connection" to verify

Requirements: Application Passwords require WordPress 5.6+ and HTTPS. If you don't see the "Application Passwords" section, your site may not meet these requirements.

WordPress.com Paid Plans: This method works for WordPress.com Personal, Premium, and Business plans. Free plans should use "WordPress.com (OAuth)" instead.

WordPress.com

WordPress.com (OAuth) Connection

Connect your free WordPress.com site using OAuth 2.0 authentication. This method works for all WordPress.com plans including free accounts.

Required Information:

  • OAuth Client ID: From WordPress.com developer portal
  • OAuth Client Secret: From WordPress.com developer portal

Step-by-Step Setup:

  1. Create WordPress.com Application:
    • Go to WordPress.com Developer Portal
    • Click "Create New Application"
    • Fill in the application details:
      • Name: Content Growth
      • Description: Content publishing platform
      • Website URL: Your app URL (e.g., https://app.content-growth.cn)
      • Redirect URLs: Add your callback URL:
        https://app.content-growth.cn/auth/wordpress/callback
      • Type: Web
    • Click "Create" to generate your application
  2. Copy Your Credentials:
    • After creating the app, you'll see your Client ID (a number like 127115)
    • Click "Show" to reveal your Client Secret
    • Copy both values - you'll need them for the connection
  3. Configure the Connection:
    • Enter your OAuth Client ID
    • Enter your OAuth Client Secret
    • Click "Connect & Authorize"
    • You'll be redirected to WordPress.com to authorize the app
    • After authorization, your site will be automatically selected

✅ Free Plan Compatible: This method works with WordPress.com free plans! No paid subscription required.

Multiple Sites: If you have multiple WordPress.com sites, the first site will be automatically selected. You can create separate connections for each site.

Note: Keep your Client ID and Client Secret secure. Never share them publicly or commit them to version control.

Medium

Medium Connection

Connect your Medium account using a personal access token to publish articles directly.

Required Information:

  • Access Token: Medium personal access token

Step-by-Step Setup:

  1. Generate Access Token:
    • Go to Medium Settings
    • Scroll down to "Integration tokens"
    • Enter a description for your token (e.g., "Content Publishing")
    • Click "Get integration token"
    • Copy the generated token immediately (it won't be shown again)
  2. Configure the connection:
    • Paste your access token in the connection form
    • Click "Test Connection" to verify the token works

⚠️ Important: Medium has discontinued new integration token generation. This connection only works if you already have an existing integration token. New users cannot obtain tokens for Medium integration.

Note: Keep your access token secure and never share it publicly. If compromised, revoke it immediately and generate a new one.

API

Custom HTTP Platform

Connect to any platform that supports HTTP API endpoints for content publishing.

Configuration Options:

  • Endpoint URL: The API endpoint for publishing
  • HTTP Method: POST, PUT, or PATCH
  • Headers: Authentication and content-type headers
  • Payload Mapping: How to structure the request body

Setup Guidelines:

  1. Endpoint URL:
    • Use the full URL including protocol (https://)
    • Ensure the endpoint accepts the chosen HTTP method
    • Test the endpoint manually first if possible
  2. Authentication Headers:
    • Common formats: "Authorization: Bearer TOKEN" or "X-API-Key: KEY"
    • Include Content-Type header (usually "application/json")
    • Add any custom headers required by your platform
  3. Payload Structure:
    • Map article fields to your platform's expected format
    • Common fields: title, content, tags, status
    • Use JSON format for the request body

Example Configuration:

{
  "endpoint_url": "https://api.example.com/posts",
  "http_method": "POST",
  "headers": {
    "Authorization": "Bearer YOUR_TOKEN",
    "Content-Type": "application/json"
  },
  "payload_mapping": {
    "title": "{{title}}",
    "body": "{{content}}",
    "tags": "{{tags}}",
    "status": "published"
  }
}

Note: Keep your API key or token secure and never share it publicly. If compromised, revoke it immediately and generate a new one.

Need more help? Contact support or check the documentation for additional platform integrations.