FlowHub Documentation

Everything you need to run n8n in production on FlowHub. Updated for n8n v1.85.

Introduction

FlowHub is a managed cloud platform for running n8n — the popular open-source workflow automation tool. You write and ship workflows; we run the servers, keep them patched, take backups, scale them and handle incidents around the clock.

This documentation covers FlowHub-specific concepts: deploying workflows, the REST API, environment variables, credentials, webhooks, custom domains and operational features. For node-level documentation (Trigger nodes, HTTP Request, AI Agent, etc.) please refer to the official n8n documentation.

5-minute quickstart

From zero to a deployed workflow in 5 minutes flat:

Sign up at flowhub.dev/register — 14-day Professional trial, no credit card.
Click + New workspace, pick ap-south-1 (Mumbai) and click Create.
Open your new workspace — you'll land in the n8n editor.
Click Add first workflow or import a template from templates.
Once you're happy, flip the Active switch. FlowHub deploys it to a production worker.

Pick a region

ap-south-1Mumbai, India · 8ms

ap-southeast-1Singapore · 12ms

eu-central-1Frankfurt, Germany · 18ms

Install the CLI

The FlowHub CLI lets you deploy workflows from your terminal, GitHub Actions or any CI/CD pipeline. Install via npm, brew or curl.

# Install via npm (recommended)
npm install -g flowhub-cli

# macOS / Linux via Homebrew
brew install digiably/tap/flowhub

# Or grab the binary directly
curl -fsSL https://get.flowhub.dev | sh

Then authenticate:

# Login (opens browser)
flowhub login

# Or with a token directly
flowhub auth set --token fh_live_xxxxxxxx

# Verify
flowhub whoami

Deploy a workflow

POST /v1/workflows

Deploy a workflow JSON to your workspace. The endpoint returns a workflow ID and live URL.

# Deploy from a local file
flowhub workflows push ./daily-report.json

# Deploy from a GitHub gist
flowhub workflows push https://gist.github.com/amit/abc123

# Deploy from stdin
cat flow.json | flowhub workflows push -

Webhooks

Every workflow is automatically assigned a unique production webhook URL. Find it under your workflow's Webhook URL tab:

https://hooks.flowhub.dev/wf/<workflow-id>/<path>

The webhook supports:

HMAC signing — every request includes X-FlowHub-Signature header (sha256). Verify with your workflow's secret.
Automatic retries — failed 5xx responses trigger retry with backoff (1s, 5s, 30s, 2m).
Rate limiting — default 100 req/s, configurable per workflow.
Custom path — sub-path after the workflow ID is preserved for routing inside the workflow.

Cron schedules

Open a workflow, click the Schedule trigger node and use the visual cron builder. Timezones are per-workspace (default UTC).

0 9 * * 1-5 — weekdays at 9:00 AM
*/15 * * * * — every 15 minutes
0 0 1 * * — first of every month

Missed runs are recorded as missed status and reported in the dashboard — so you never silently skip a job.

Environment variables

FlowHub supports both n8n-style environment variables (loaded at workflow execution time) and FlowHub variables (managed at the workspace level).

GET /v1/variables

POST /v1/variables

PUT /v1/variables/:key

DELETE /v1/variables/:key

Example: import a .env file via the CLI.

# Set variables from .env
flowhub variables set --file .env

# List current
flowhub variables list

Credentials & secrets

All credentials (API keys, OAuth tokens, DB passwords) are encrypted at rest using AES-256-GCM with a per-workspace master key. The master key is itself encrypted with Digiably's KMS and rotated quarterly.

Credentials are scoped to a workspace — they cannot be read from another workspace.
Each read is logged in the audit log with user, timestamp and target node.
Rotate from the dashboard, CLI or API. Old versions remain available for 7 days for rollback.

Custom domains

On Professional and Business plans, bring your own domain by adding a CNAME record:

# In your DNS provider
CNAME workflows.example.com → proxy.flowhub.dev.

FlowHub provisions a Let's Encrypt TLS certificate in <60 seconds and sets up automatic renewal. Up to 5 (Professional) or unlimited (Business) custom domains per workspace.

REST API

The full FlowHub REST API follows OpenAPI 3.1 — the spec is available at api.flowhub.dev/openapi.json. Authentication is via Bearer tokens:

# Authentication header
Authorization: Bearer fh_live_xxxxxxxx

Base URL

All API requests go to https://api.flowhub.dev/v1. Production tokens are prefixed with fh_live_, test tokens with fh_test_.

Common endpoints

Quick reference for the most-used endpoints:

GET /v1/workspaces — list your workspaces
POST /v1/workspaces — create a workspace
GET /v1/workflows — list workflows
POST /v1/workflows — deploy a workflow
POST /v1/workflows/:id/trigger — manually trigger a workflow
GET /v1/executions — list executions (with ?workflow_id, ?status, ?limit)
GET /v1/executions/:id — full execution details including per-node output
GET /v1/usage — usage and quota for current billing cycle

Examples

End-to-end examples using curl, Node.js and Python:

          
          
          
        
# List my last 20 executions
curl https://api.flowhub.dev/v1/executions?limit=20 \
  -H "Authorization: Bearer fh_live_..."

# Trigger a workflow from CI
curl -X POST https://api.flowhub.dev/v1/workflows/wf_92a1/trigger \
  -H "Authorization: Bearer fh_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "event": "deploy-success", "repo": "api" }'

# Reschedule a cron workflow
curl -X PUT https://api.flowhub.dev/v1/workflows/wf_92a1/schedule \
  -H "Authorization: Bearer fh_live_..." \
  -d '{ "cron": "0 6 * * *", "timezone": "Asia/Kolkata" }'
import FlowHub from "flowhub";
const fh = new FlowHub({ apiKey: process.env.FLOWHUB_TOKEN });

// List recent failures
const failures = await fh.executions.list({ status: "failed", limit: 10 });
console.log(failures);

// Trigger an on-demand workflow
const run = await fh.workflows.trigger("wf_92a1", { event: "deploy-success" });
console.log(run.id, run.status);
from flowhub import FlowHub
fh = FlowHub(api_key="fh_live_...")

# List recent failures
failures = fh.executions.list(status="failed", limit=10)
for f in failures:
    print(f.id, f.workflow_id, f.error)

# Trigger an on-demand workflow
run = fh.workflows.trigger("wf_92a1", {"event": "deploy-success"})
print(run.id, run.status)

Errors

All errors return standard HTTP status codes plus a JSON error body:

// 4xx / 5xx response
{
  "error": {
    "code": "workflow_invalid",
    "message": "Workflow references missing credential 'openai-prod'",
    "request_id": "req_4f8a93",
    "docs": "https://docs.flowhub.dev/errors/workflow_invalid"
  }
}

Backups

Every workspace is backed up hourly to encrypted, cross-AZ object storage. Restore granularity:

Starter: 1 daily snapshot · 30-day retention
Professional: Hourly snapshots · 90-day retention
Business: Hourly + WAL archive · 365-day retention

Restore from the dashboard, CLI, or API:

# Restore workspace to a snapshot
flowhub workspace restore ws_4f8a --to 2026-04-14T08:00:00Z

Monitoring

FlowHub ships with built-in monitoring: per-second metrics, p50/p95/p99 latency, error rate, queue depth and execution success ratio are streamed to your dashboard. Send to Datadog, New Relic, Sentry or a generic webhook with one click.

# Datadog integration
flowhub monitoring set --provider datadog \
  --api-key "dd_..." \
  --site datadoghq.com

Scaling

FlowHub runs each workflow in its own isolated queue. When latency spikes, FlowHub horizontally scales the worker fleet automatically (up to 100 workers per workspace on Business). Scaling events are visible in real-time on the dashboard.