# Install flowpipe with Homebrew Cloud scripting engine. Version 1.2.2 via Homebrew; verified 2026-07-26. ## Install ```sh sudo av install brew:flowpipe ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install flowpipe ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:flowpipe - **Package manager:** Homebrew - **Version:** 1.2.2 - **Source summary:** Cloud scripting engine - **Homepage:** - **Repository:** - **Last updated:** 2026-07-26T11:37:57+02:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - flowpipe (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 1.2.2 ## Project history and usage Flowpipe is Turbot's open-source cloud scripting and workflow automation engine for defining DevOps pipelines as HCL code. ### Project history Flowpipe was introduced in December 2023 as a cloud scripting engine for automation and workflow, with pipelines for DevOps written in HCL. The initial release supported pipeline execution, steps such as container, email, function, HTTP, query, sleep, transform, and pipeline, schedule and HTTP triggers, credential management, and mod composition. The project reached 1.0.0 in October 2024. That release added a connection resource for credentials, formal connection and notifier variable types, enum validation, defined CLI exit codes, and deprecated earlier credential resources in favor of connection resources. ### Adoption history Flowpipe's adoption path is tied to Turbot's broader CLI and mod ecosystem. Its README points users to Flowpipe Hub library mods and samples for services such as AWS, Azure, GCP, GitHub, Jira, Okta, PagerDuty, SendGrid, Slack, Teams, and Zendesk. The README also positions Flowpipe alongside Steampipe and Powerpipe in Turbot Pipes, using Steampipe for data access, Powerpipe for visualization, and Flowpipe for workflow automation. ### How it is used Users define pipelines, triggers, variables, locals, and steps in .fp files inside a Flowpipe mod. Config resources such as workspaces and connections are HCL files ending in .fpc and are loaded from the working directory or mod location and the Flowpipe install config directory. A typical package workflow installs the flowpipe CLI, initializes a mod with flowpipe mod init, writes pipeline definitions in HCL, installs reusable mods from the hub or Git repositories, and runs pipelines from the terminal. ### Why package nerds care Flowpipe is notable for package metadata because it brings Terraform-like HCL mod conventions to command-line workflow automation. It also has a recognizable family relationship with Turbot's Steampipe, Powerpipe, hub mods, and connection configuration files. ### Timeline - 2023: Flowpipe 0.1.0 introduces the cloud scripting engine and HCL pipeline model. - 2024: Flowpipe 0.2.0 adds query triggers, expanded HTTP triggers, database query support, and more credential types. - 2024: Flowpipe 0.3.0 adds human workflow, Slack and email messaging, input steps, and Steampipe credential import. - 2024: Flowpipe 0.6.0 adds interactive workflows in the terminal via console integration. - 2024: Flowpipe 1.0.0 introduces connection resources and deprecates credential resources. - 2026: Flowpipe 1.2.x continues with security and dependency maintenance releases. ### Related projects - Official sources connect Flowpipe to Flowpipe Hub mods, Turbot Pipes, Steampipe, Powerpipe, and the shared Turbot pipe-fittings codebase. ### Sources - - - - - - ## Security Notes infrastructure mutation or orchestration signal. - **Geiger risk:** orange / medium - infrastructure mutation or orchestration signal ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: *.fp, mod.fp, $PWD/*.fpc, ~/.flowpipe/config/*.fpc, $FLOWPIPE_INSTALL_DIR/config/*.fpc ## Credential files - Unix: $PWD/*.fpc, ~/.flowpipe/config/*.fpc, $FLOWPIPE_INSTALL_DIR/config/*.fpc ## Combined YAML source View the package source record on GitHub. [combined/flowpipe.yml](https://github.com/mxcl/pkgdb/blob/main/combined/flowpipe.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph