---
title: "New guide: Integrating flyctl into automation and CI/CD pipelines"
description: "A new guide to running flyctl from CI: picking token types, GitHub Actions workflows, monorepos and parsing JSON output."
date: "2026-05-05"
author: "Kristin Martin"
url: "https://fly.io/changelog/flyctl-ci-cd-guide/"
discussion: "https://community.fly.io/t/new-guide-integrating-flyctl-into-automation-and-ci-cd-pipelines/27806"
---

# New guide: Integrating flyctl into automation and CI/CD pipelines

Running `flyctl` from a script or CI pipeline instead of your laptop? We've published a new guide for that.

Whether you're wiring up GitHub Actions, orchestrating deploys across a monorepo, or building tooling that runs `flyctl` on behalf of your team, this guide covers the patterns and gotchas we've seen come up most often in Solutions Architecture sessions and support chats.

The guide walks through picking the right token type for the job, structuring GitHub Actions workflows for single apps and monorepos, parsing `flyctl` output with `—json` and `jq`, and choosing a build strategy that fits your pipeline.

**Read it here:** https://fly.io/docs/flyctl/integrating/

Let us know if it's useful, what's unclear, and what else you'd like to see covered.