Engineering Teams

Where engineering processes run
without becoming engineering tickets.

Business teams handle their own repetitive processes. Engineers extend the platform with custom modules for anything proprietary. AI agents invoke your flows as tools. Everything executes with a full audit trail — on your infrastructure.

What engineering teams deal with today

Automation requests pile up in the ticket queue

Business teams can't self-serve, so every process request becomes an engineering ticket. Engineers spend time writing glue code instead of shipping product.

Scripts scattered everywhere with no visibility

Crons, Lambdas, and glue scripts sprawl across repos with no audit trail and no central view. When something breaks, nobody knows where to look.

Every proprietary integration is a custom project

Internal APIs and proprietary tools need custom code for every connection. The solutions pile up. The maintenance burden compounds.

Processes running at engineering teams on flow8

Business teams self-serve. Engineers extend. Processes execute reliably.

🚀
Build Events Route and Notify Automatically
Build event fires → Metadata extracts → Team channel notified → Approvals triggered → Downstream actions run
Real-time visibility
🚨
Incidents Escalate Without Anyone Coordinating
Alert fires → On-call paged → Ticket opened → Stakeholders notified → Resolution tracked → Post-mortem scheduled
Faster MTTR
🔗
Internal Services Talk to Each Other Without Glue Code
REST call → Chain requests → Transform responses → Enrich with external data → Return results
No custom code
📊
Data Moves, Transforms, and Lands Without a Pipeline Engineer
Extract → Transform → Validate → Load → Notify → Archive for audit trail
Fully auditable
🛠️
Your Proprietary Logic Becomes a First-Class Module
Write Go module → Register via reflection → Auto-discovered → Callable from flows → Versioned
Extensible
🤖
AI Agents Execute Your Business Logic as Tools
MCP server exposes flows → Claude or ChatGPT invokes them → Agent orchestrates multi-step tasks using your actual processes
AI-native
Plugin Architecture

Engineers extend flow8
without touching core.

One Go file. Your proprietary APIs, internal services, or custom logic drop in like any built-in module — auto-discovered, no registration, no rebuild required. Write it once and every flow in the platform can use it immediately.

  • Picked up automatically — no wiring needed
  • Version-controlled alongside your codebase
  • Full access to execution context & shared KV store
  • Available in the visual builder the moment it's compiled
module_slack_alert.go
package v2

type ModuleSlackAlert struct {
    *PluginModule
}

// NewModuleSlackAlert is auto-discovered
// by flow8's reflection-based registry.
func (m *PluginModule) NewModuleSlackAlert() *ModuleSlackAlert {
    return &ModuleSlackAlert{PluginModule: m}
}

func (m *ModuleSlackAlert) Execute(params Params) Response {
    channel := params.GetString("channel")
    message := params.GetString("message")

    if err := postSlack(channel, message); err != nil {
        return m.Fail(err.Error())
    }

    return m.Done(map[string]any{
        "sent":    true,
        "channel": channel,
    })
}

How engineers integrate with the execution layer.

Every surface your team needs to build on, extend, and observe.

🔌
Your Code Becomes a Module
One Go file. Auto-discovered via reflection. No registration, no rebuild. Your proprietary logic available everywhere immediately.
📡
Trigger Anything via REST
Pure HTTP. No SDK. Create flows, trigger runs, stream logs — every operation is a standard REST call from any system.
🤖
AI Agents Run Your Processes as Tools
Claude, ChatGPT, Cursor invoke your flows directly. AI orchestrates multi-step business processes using your actual logic.
Execution State Streams Live
WebSocket updates reach clients the moment steps complete. Watch processes run. Surface state changes without polling.
🧪
Tests Run Without External Calls
Record external API calls once. Replay deterministically. No live dependencies, no flakiness, no surprises in CI.
📝
Business Teams Own Their Processes
Non-engineers define and update flows without filing tickets. Engineering ships the modules. Everyone else runs the processes.

Developer Integration Stack

Connect any system via REST, webhooks, or custom modules

Flows as API
Every flow is a REST endpoint — trigger from any system
🤖
MCP Server
Claude, ChatGPT, Cursor invoke flows as AI tools
🪝
Webhooks
Inbound & outbound — GitHub, CI/CD, alerts
🔌
Custom Modules
One Go file, auto-discovered, no core changes
🗄️
MongoDB / PostgreSQL
Native query & write support
📡
WebSocket
Stream live execution state to any client
💬
Slack / Teams
Push alerts, approvals, incident pings
☁️
S3 / Object Storage
AWS S3, MinIO, self-hosted

See your engineering processes running.

Book 30 minutes and we'll show you your highest-toil process executing on flow8 — with your modules, your APIs, on your infrastructure.

Book a demo →