Skip to content

Services & agents

Wire up anything with an API.

Shopify and BigCommerce ship ready to connect. Every other system becomes a custom service, and your coding agent can build it for you with the KonnectHub CLI.

Book a build callWatch an agent build one
  • Platform or custom
  • Built from your terminal
  • Keys never leave KonnectHub

Services · acme-workspace

platform 2 / custom 12

  • shopify
  • bigcommerce
  • woocommerce
  • square
  • zoho
  • quickbooks
  • hubspot
  • flow order-to-zoho SUCCEEDED
  • airtable
  • stripe
  • slack
  • google-sheets
  • n8n
  • your-erp
  • your-api
woocommerce.order.paid order-to-zoho zoho 412 ms

01 / CLI & skills

No MCP server. No plugin. One CLI.

Install the KonnectHub CLI and run one command. Your agent gets instruction files in the repo and every command it needs to build, test and ship a flow.

Setup · ~/acme-flows

Four commands

READY
  1. 01

    Install

    curl -fsSL https://app.konnecthub.io/install.sh | sh

    checks the download against a published checksum

  2. 02

    Sign in

    konnecthub login

    pick the workspace in the browser

  3. 03

    Start a project

    konnecthub init

    links nothing until you ask

  4. 04

    Teach the agent

    konnecthub skills

    writes agent instructions to .claude/skills/

  1. Files, not a server

    Skills are plain Markdown in your repo. Commit them, review them, diff them. Nothing runs in the background.

  2. The whole API, in reach

    konnecthub routes lists every route and konnecthub api calls any of them. The agent is never stuck behind a missing tool.

  3. Output made for machines

    Every command takes --json. Streams come back as NDJSON, one line per record.

  4. Scoped like you, or less

    A token can do what you can, minus what you did not grant. konnecthub whoami prints its scopes.

02 / Agent-built connections

Tell your agent. It does the wiring.

Describe the job in plain words. The agent defines the services, writes the flow, tests it against fixtures and deploys. You add the keys.

  • Claude Codeclaude
  • Codexcodex
  • OpenCodeopencode
  • Cursorcursor-agent

YouConnect our WooCommerce store. When an order is paid, create the invoice in Zoho Books.

AgentNeither is a platform service. I will define both as custom services.

konnecthub routes services

4 routes match "services"

konnecthub api POST /services --json

✓ woocommerce TOKEN ✓ zoho-books OAUTH2

AgentAdd the store keys and sign in to Zoho under Connections. I never see them.

konnecthub new woo-paid-to-zoho

✓ flow created, draft linked

konnecthub test

✓ fixtures/order-4412.json 3 steps SUCCEEDED

konnecthub deploy

pushed → published v1 → bundle READY → active

AgentLive. Each paid order is one event and one run you can open.

Keys stay in KonnectHub
Connections are created in the app, the only place credentials are entered. The agent names a connection. The platform resolves it when a flow runs.
Same draft as the browser
What the agent pushes, you can open in the editor. If you edit while it pushes, the CLI merges.
It reads its own runs
konnecthub inspect explains why a run did what it did, summary first. The agent fixes from the record, not from a guess.

03 / Services

The systems commerce teams plug in most.

platform
Ships with KonnectHub. Credentials refreshed for you, provider topics defined as event sources, webhooks registered on connect.
custom
Defined once in your workspace, by your agent or our team. Then every flow and every account uses it the same way.

Storefronts

Where orders start

  • Shopify

    OAUTH2

    • Orders into the ERP the moment they are created
    • Product edits pushed to every feed
    • shopify.orders.create
    • shopify.orders.paid
    • shopify.products.update
    platform

  • BigCommerce

    TOKEN

    • Catalog and stock kept in step with the warehouse
    platform

  • WooCommerce

    TOKEN

    • Paid orders sent to fulfilment
    • Stock counts written back to the store
    custom

  • Square

    OAUTH2

    • In-store sales drawn down from the same inventory
    custom

Back office

Where orders get counted

  • Zoho

    OAUTH2

    • Customers in CRM, invoices in Books, stock in Inventory
    custom

  • QuickBooks

    OAUTH2

    • Paid orders become invoices, refunds become credit notes
    custom

  • HubSpot

    OAUTH2 · TOKEN

    • Contacts and deals updated from order history
    custom

  • Airtable

    TOKEN

    • Ops tables the team edits, read by flows on a schedule
    custom

Money & messages

Where the team hears about it

  • Stripe

    TOKEN

    • Payouts reconciled against orders every night
    custom

  • Slack

    OAUTH2

    • Approval links posted to a channel when a run pauses
    custom

  • Google Sheets

    OAUTH2

    • A morning report the whole team can open
    custom

  • n8n

    TOKEN

    • Workflows you already run post to a KonnectHub webhook
    custom

Not on the list? If it has an API, it can be service number 13.

Tell us what to connect

04 / Custom services

Define it once. Every flow can use it.

A custom service behaves exactly like Shopify does: the same connection picker, the same input type, the same credential handling.

Service · custom

WooCommerce

Key
woocommercepermanent
Authentication
TOKEN
Config fields
store_url
Events
woocommerce.order.paid
inputs.json
{
  "store": { "type": "connection", "service": "woocommerce" }
}
flows/woo-paid-to-zoho/flow.ts
const { config, credentials } =
  await this.connection(this.input.store);
// resolved by the platform, the moment the flow asks

  1. The key is permanent

    Flows name a service by its key. It cannot change, so no flow is ever left pointing at nothing.

  2. One connection per account

    Two stores means two connections. Same service, same flow code, a different input.

  3. Listen to one store

    A subscription can be filtered to a single connection, so a flow hears from one store, not all of them.

05 / Build it with us

Name two systems.We wire them.

Hand it to your agent, or hand it to us. Our team defines the services, builds the flows and runs them in a workspace you can read end to end.

Book a build callInstall the CLI

Jobs we wire most

  1. Paid WooCommerce orders become Zoho Books invoices

    webhook → flow → custom service

  2. Shopify refunds become QuickBooks credit notes

    event source → flow → custom service

  3. Stripe payouts reconciled in a sheet every morning

    schedule → flow → custom service

  4. Refunds over $500 wait for a manager in Slack

    event source → flow → pause

  5. Your n8n workflows update BigCommerce stock

    webhook → flow → platform service