Apps/Recipes/All recipes
Recipes
13 complete apps to start from. Each recipe is a working example: create an app from it with one command, then follow its tutorial to connect it, set its keys and try it end to end.
Three ways to start
From the CLI
Create the app and download its files in one go.
ib-apps create my-reviews \
--platform shopify --recipe reviewsFrom the dashboard
New app → Start from → pick a recipe. Shopify scopes are filled in on the connect step. Pull it when you want it locally:
ib-apps pull --app my-reviewsFrom the API
Pass recipe to POST /v1/apps, with a key that has Apps Permissions.
curl https://api.inferencebureau.com/v1/apps \
-H "Authorization: Bearer $IB_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"my-reviews","platform":"shopify","recipe":"reviews"}'All recipes
What every tutorial walks through
- 01Create the appThe CLI command and the New app route, side by side.
- 02Tour the filesEvery model, action, page and test the recipe loads, and where it lives.
- 03Finish setupScopes, webhooks, keys and integrations, in order.
- 04Run and try it
ib-apps dev, then a checklist of what Logs should show. - 05Make it yoursThe files to change first, the tests, and the deploy.
CLI reference for recipes
Install once with npm i -g @inferencebureau/apps, then ib-apps login.
| Flag | What it does |
|---|---|
--recipe <id> | Start from an example instead of the starter alone. Ids: reviews, wishlist, quiz, tagger, notion-sync, bundler, parcel-globe, waitlist, slack-bot, discord-bot, class-booking, claude-connector, chatgpt-app |
--platform shopify | Required for the six Shopify recipes. Web is the default, so web recipes need nothing. |
--dir <path> | Where the files land (default ./<slug>). The folder must be empty. |
--json | Print the created app and its folder as JSON, for scripts. |
Mixing them up fails before anything is created: The Product reviews recipe is a Shopify app. Add --platform shopify and run it again.