Skip to content

Recipes

A recipe is a named set of assets: objects, properties, pipelines, workflows, forms, lists, records, and Trading Cards apps. It is the thing you hand on. In the library a recipe is a book; an app is a trading card.

A recipe stands alone. When you add an asset from a snapshot, its definition is copied into the recipe, so the snapshot can be deleted later without touching the recipe.

New recipe in the Library or on the Recipes screen asks for a name and creates an empty recipe. Then add assets:

  • From a snapshot: open a snapshot, select items (or open one item) and click Add to recipe. Everything the items depend on comes with them.
  • From the recipe page: Add assets has two tabs, From a snapshot and Apps.

An asset already in the recipe is not added twice.

SectionWhat it shows
FactsIndustry, Hubs, Use cases, Tier/Edition, Updated
Deployed toEach portal the recipe has been deployed into. Update appears when the recipe has changed since. Watch opens the running job.
AssetsName, Type and Dependencies for every item. Items that arrived as a dependency are marked. Remove per row, or select several and Remove N.

Buttons: Export, Add assets, Deploy. The ⋯ menu: Edit details, Change cover, Copy recipe ID, Duplicate, Delete recipe.

Edit details holds the name, a description, an industry, a tier (Starter, Pro, Enterprise), the hubs it touches (Sales, Marketing, Service, Content, Data, Revenue, Agent) and free-form use cases. These are shown on the face and used by search.

Every recipe gets a generated cover from its name. Change cover lets you pick a primary colour (teal, red, blue, amber, plum, ink, or any hex), one of ten patterns and one of four themes, or Shuffle. Upload takes a PNG, JPG, WebP or SVG up to 300 KB.

Sharing is a file. There are no teams or shared workspaces; each recipe belongs to one person.

  • Export downloads <name>.recipe.json: the recipe’s details, cover, and every asset with its full definition, plus who exported it and when.
  • Import (Library or Recipes) takes that file and creates an independent copy in your library. Imported recipes appear under Shared with you, and record where they came from.

Import limits: 25 MB and 5,000 items. Items that are malformed, or apps that are no longer in the catalogue, are skipped and counted in the notice afterwards.

Duplicate makes “<name> (copy)” with the same details, cover and assets. Delete recipe removes the recipe and the definitions copied into it. Snapshots and portals are untouched.

Deploy asks for a target portal and whether assets that already exist there should be skipped or created as copies. The server queues one job for the assets and one job per app; the apps need a Personal Access Key on the target, the assets need a Private App Token. Details in Deploying assets.