Marketplace and integrations

`jelou marketplace`

Browse, search, and install OAuth marketplace apps (Shopify, HubSpot, Slack…) for your organization.

Subcommand	Description
`list`	Browse the available apps (search or filter to installed)
`install <slug>`	Install an app by slug (opens the browser to authorize OAuth)

jelou marketplace list
jelou marketplace list --search "shopify" --json
jelou marketplace list --installed-only
jelou marketplace install hubspot
jelou marketplace install slack --print-url           # headless/SSH flows
jelou marketplace install shopify --metadata '{"shopify":{"shop":"mystore.myshopify.com"}}'

Flag	Description
`--search <q>`	Filters by name or description
`--installed-only`	Only already-installed apps
`--print-url`	Prints the OAuth URL instead of opening the browser
`--metadata <json>`	Metadata required by some apps (e.g. the Shopify store)
`--timeout <sec>`	OAuth polling timeout (default 120)
`--limit <n>`	Max results (default 20)
`--wait`	In `--json` mode, poll until the app is installed (or `--timeout`) and report `installed`

Installing grants long-lived OAuth scopes over your organization’s data; revoking is a multi-step process in the dashboard (not via CLI). If a slug matches multiple apps, the CLI asks you to choose. Some apps (Shopify, etc.) require app-specific --metadata.

`jelou payments`

Checks that a workflow’s payment nodes take charges as configured, before you publish or hand it over. It checks each payment node on its own and stops at the first check that fails.

Check	What it checks
Contract	The node’s inputs and payment tool version against the gateway catalog, same as `jelou workflow validate` and `jelou push`
Outputs	That the outputs the node uses exist in that version
Installation	That the node’s gateway is installed and connected in the marketplace
Company	That JelouPay is activated and the company has its workflows app
Credentials	That the gateway’s secrets exist (skipped in test mode)
Environment	That the node and the installation are in the same environment (test or production)
Payment link	That the gateway creates a real payment link with fake buyer data

jelou payments verify 1234                    # every payment node of workflow 1234
jelou payments verify workflows/cobro.json    # a local workflow
jelou payments verify 1234 --node cobro-stripe
jelou payments verify 1234 --json             # per-node result: checks, warnings and failure

Flag	Description
`--node <id>`	Check only this payment node
`--installation <id>`	Installation to use when the node doesn’t name its own and the gateway has several
`--live`	Also create the payment link on production nodes
`--amount <amount>`	Amount of the test charge (default 1)
`--currency <code>`	Currency of the charge when the node takes it from the conversation; a fixed currency on the node is kept

The command exits with 0 when every node passes, 2 on a configuration error, 4 when authentication fails, and 6 when a service didn’t respond (try again).

The payment link charges nothing: it creates a pending order marked as a verification, and the result shows only the link’s domain, never the full link or secret values. In test mode it doesn’t use up your tests, since only completed payments count.

In production, the payment link is skipped unless you pass --live. With --live, the test order shows as pending in the business’s Payment Hub.

`jelou connect`

Lists operators and teams of the Connect product (human-handoff flows).

jelou connect operators list                       # active operators
jelou connect operators list --include-inactive    # includes deleted/inactive
jelou connect teams list --json
jelou connect operators list --json --out operators.json

Operators are individual users with the operator role.
Teams are groups of operators for team-based routing.
The operator’s id is the one referenced in a workflow’s CONNECT node (configuration.operatorId).

`jelou shop`

Manage Jelou Shop: per-company activation, configuration, branches, categories, products, and catalog imports.

Group	Subcommands
Setup	`info`, `activate`, `settings`
Branches	`branches list/show/create/update/delete`
Categories	`categories list/create/update/delete`
Products	`products list/show/upsert/update/status/delete`
External catalog	`accounts`, `syncs <accountId>`, `imports template/upload/show`

jelou shop activate --name "My Store" --contact-mail "[email protected]"
jelou shop settings --currency USD --tax-value 15
jelou shop products list --stock in_stock --search "shoe" --json
jelou shop products upsert --file products.json --sync
jelou shop imports template --lang es --output template.xlsx
jelou shop imports upload --file products.xlsx --uploaded-by "alex"

shop activate uses your jelou login credential (your Jelou API key) — it doesn’t require a separate bootstrap key. Only one activation per company is allowed, and it refuses to overwrite an existing activation under --no-input. products upsert creates or updates products by SKU; use --sync to wait for the result.

Getting Started

Developer

Jelou CLI

Outbound Messaging

Inbox

Marketplace

Channels

Configuration

Billing

Marketplace and integrations

`jelou marketplace`

`jelou payments`

`jelou connect`

`jelou shop`

​jelou marketplace

​jelou payments

​jelou connect

​jelou shop

`jelou marketplace`

`jelou payments`

`jelou connect`

`jelou shop`