Build integrations, not infrastructure
The FlowGate One SDK handles messaging, secrets, config delivery, and lifecycle management. You write the business logic.
Go SDK
Build an integration in 50 lines
Define three callbacks — what happens when an integration is created, when a trigger is activated, and when an action fires. The SDK handles everything else.
package main
import (
"context"
"log"
"github.com/flowgateone/sdk"
)
func main() {
worker := sdk.NewWorker("slack")
worker.OnNewInstance(func(ctx context.Context, inst sdk.Instance) {
// Called when a new Slack workspace is connected
secrets := inst.Secrets() // Auto-loaded from Vault
config := inst.Config() // Delivered by the platform
log.Printf("Slack workspace connected: %s", config.Name)
})
worker.OnNewTrigger(func(ctx context.Context, inst sdk.Instance, trigger sdk.Trigger) {
// Start watching for events matching this trigger
// When an event occurs, publish it:
inst.Publish(ctx, trigger.ID, eventPayload)
})
worker.OnAction(func(ctx context.Context, inst sdk.Instance, action sdk.ActionCommand) {
// React to events routed here by FlowGate One
// Full access to secrets, config, and connections
postMessage(inst.Secrets().Get("bot_token"), action.Payload)
})
worker.Start() // Connects to platform, handles lifecycle
}What the SDK handles for you
Focus on integration logic. The platform handles the hard parts.
Automatic Secret Management
Secrets are loaded from Vault automatically. Each integration instance has its own scoped credentials. No manual secret wiring.
Config Delivery
Configuration is pulled from the platform API at startup and delivered to your handler. Schema-validated against your integration type definition.
Lifecycle Commands
The SDK manages the full integration lifecycle — creation, trigger updates, secret rotation, pause, and shutdown. You implement the callbacks you need.
Graceful Shutdown
In-flight actions drain on shutdown with configurable timeout. The SDK tracks active work and ensures clean exits.
Self-Healing
If a worker becomes unresponsive, the platform detects and recovers automatically within seconds. Zero manual intervention.
Action Dispatch
Actions run on the same process that owns the integration — with full access to secrets, config, and reusable connections. No cold starts.
REST API
API Reference
Manage integrations, triggers, and actions programmatically.
| Method | Endpoint | Description |
|---|---|---|
| POST | /integrations | Register a new integration instance |
| GET | /integrations/:id | Get integration details and status |
| POST | /triggers | Create a trigger (event source) |
| POST | /actions | Create an action (event sink) wired to triggers |
| DELETE | /integrations/:id | Remove integration and cascade cleanup |
| DELETE | /triggers/:id | Remove trigger and update routing |
| DELETE | /actions/:id | Remove action and stop event delivery |
Ship your first integration today
From zero to production-ready integration in minutes.