Skip to content
Platform surfaces 4 min read

FlowHub

The first-party workflow marketplace live at initial launch — catalog, downloads, supported provider imports and Account-backed billing.

Status: live at initial launch. FlowHub is FluxonLab’s first-party workflow marketplace at its own subdomain. The initial public launch includes the catalog, downloads, supported provider imports, approved provider runtime, and Account-backed purchase and billing access. The visual Canvas/Studio and full AI Assistant are later Coming Soon updates. Its dedicated home is flowhub.fluxonlab.com.

What the initial launch includes

  • Browse a large catalog of ready-made n8n workflow templates.
  • Inspect the graph, required apps, docs and trust signals before downloading.
  • Download standard n8n JSON with credentials and raw secrets removed.
  • Import the JSON into your own n8n instance and add your credentials there.
  • For Pro users, send a draft to supported platforms through the one-click import flow.
  • Buy first-party workflow products from FluxonLab through Account-backed checkout.

Importing a workflow into n8n

At initial launch, the import path works like this:

  1. On a workflow page, choose Download to get the .json file.
  2. In your n8n instance go to Workflows → Add workflow.
  3. Choose Import from File and select the downloaded JSON.
  4. Review the full node graph on the n8n canvas before activating anything.
  5. Open nodes with credential warnings, create your own credentials, and run a test execution.

FlowHub does not execute the workflow during import. The workflow becomes runnable only inside the automation platform you control.

One-click imports for Pro users

Pro users can send a draft directly to a supported platform. FlowHub asks for a one-time platform API token, uses it for that request, and does not store the token. The preflight panel shows node count, edge count, credential placeholders and platform warnings before anything is created.

Supported import platforms

n8n receives the original workflow directly. Other platforms use different graph formats, so FlowHub creates a provider-native review scaffold: a safe draft or shell that carries the FlowHub source graph and metadata for manual mapping.

PlatformImport modeWhat gets created
n8nDirect importAn inactive n8n workflow with nodes, connections, settings, tags and credential placeholders preserved.
Make.comReview scaffoldA scenario draft carrying the FlowHub source package for manual replacement with Make-native modules.
ActivepiecesReview scaffoldA disabled flow record with FlowHub source metadata for step and connection mapping.
Node-REDReview scaffoldA flow tab with comment, inject, function and debug nodes carrying the FlowHub source package.
FlowiseReview scaffoldAn undeployed chatflow shell with FlowHub graph metadata.
LangflowReview scaffoldA Langflow flow shell with FlowHub graph metadata.

Zapier, Dify, Pipedream and similar platforms are not part of the initial import matrix; they may get platform-specific adapters in a future update.

Marketplace and billing boundary

FluxonLab is the only seller in the initial marketplace. The Account layer owns sign-in, plans, checkout access, billing records and entitlements. Third-party seller onboarding, vendor accounts, commissions, split payments and payouts are outside the initial scope.

Credential model

FlowHub workflows ship with credential placeholders, never real secrets. Published files are scanned and scrubbed before they reach the marketplace. A downloaded workflow may reference a credential type such as OpenAI API, Slack API or Gmail OAuth, but it never contains the key or token. Credentials live only inside your target platform.

What comes later

  • The visual Canvas for generating and remixing workflows.
  • Export-fidelity expansion and deeper provider-native adapters.
  • A fuller AI assistant, only when it can be proven reliable — until then any hero assistant stays a deterministic guide.

Design principles

  • Honest scope — FlowHub is a marketplace, discovery, export and controlled-import surface, not a hosted workflow runner.
  • Credential-safe — templates ship with placeholders; real secrets stay in your own platform.
  • Visual first — you should understand what a workflow does before importing it.
  • Least privilege — integrations request the minimum scope required.

Not a runner

FlowHub does not run workflows, schedule jobs or connect to your accounts. Workflows run on the automation platform you control, self-hosted or cloud.

FluxonLab Sign up for free