How to Use ReelsFarm CLI with GitHub Actions for CI/CD Social Media

GitHub Actions runs your tests and deploys your code.

With ReelsFarm CLI, it can also generate and publish your social media content.

Why CI/CD for Social Media

Your product releases on a schedule. Your social content should follow the same cadence.

Every release can trigger a post. A new feature gets a TikTok slideshow. A product update gets an announcement across platforms. The CLI runs in CI the same way your build scripts do.

The human still reviews. CI prepares the draft. You approve in the pipeline or through the ReelsFarm review interface. Content goes live.

Step 1: Install the CLI in Your Workflow

Add a step to your GitHub Actions workflow that installs the ReelsFarm CLI.

```yaml

• name: Install ReelsFarm CLI

run: npm install -g @reelsfarm/mcp-client ```

The CLI is open source under MIT. The binary is `reelsfarm`.

Step 2: Authenticate

Add your ReelsFarm API key as a GitHub secret. Never commit it to the repository.

```yaml

• name: Authenticate

run: reelsfarm login --api-key ${{ secrets.REELSFARM_API_KEY }} ```

Create the API key in your ReelsFarm account settings under the MCP tab. Store it in GitHub Secrets as `REELSFARM_API_KEY`.

Step 3: Generate Content in CI

The CLI can generate content from your workflow. Product scenes, slideshows, hooks.

```yaml

• name: Generate release slideshow

run: reelsfarm slideshows prepare --product "${{ github.event.release.name }}" --format tiktok --slides 6 ```

The prepare command creates a draft. It does not publish. Credits are not spent until you confirm. The draft waits for review.

Step 4: Review and Confirm

Every destructive action requires confirmation. In CI, you can handle this two ways.

Review drafts through the ReelsFarm web app after the workflow runs. Or build a confirmation step into your pipeline that a human approves before the next stage proceeds.

The confirmation gate means CI never publishes without a human seeing the output first.

Step 5: Schedule Recurring Content

Use a scheduled workflow trigger for recurring content.

```yaml on: schedule:

• cron: '0 9 * * 1' # Every Monday at 9 AM

```

The workflow runs on schedule. The CLI prepares content. You review. It publishes.

What This Unlocks

Release-triggered posts. Every deploy publishes an announcement. Scheduled content cadences. Product updates become social posts automatically.

CI/CD for social media means your content pipeline runs on the same infrastructure as your code pipeline. No separate tool. No manual posting step. No forgetting to announce the release.