Skip to main content
The recipes library is App Builder’s starter template catalogue, drawn from the legacy V1 Agent Hub recipes that shipped in the first generation of Vortex IQ. Each recipe is a pre-built prompt and plan combination that gives a merchant a fast head-start on a common workflow. Pick a recipe, run it as is, or open it in the App Builder editor and customise it to fit your specific case. The recipes are not the only way to build an app. They are starting points. The full strength of App Builder is that you can describe anything in plain English and the agent will assemble it. The recipes are useful when you do not know where to start, or when you want a known-good baseline for a common task.

​
How to use a recipe

  1. Browse the recipes by platform tab below.
  2. Click a recipe name to open its template page.
  3. The template shows the pre-built prompt, the generated plan, and the toolkit it uses.
  4. Click Use this recipe to fork it into a new app in your workspace.
  5. Edit any part of the prompt or plan to fit your specific store, schedule, or output channel.
  6. Deploy to sandbox, test, promote to production. Same flow as any other App Builder app, see Building an app.

​
Shopify recipes

Shopify recipes were among the most popular V1 Agent Hub agents and remain strong starters in App Builder.

​
BigCommerce recipes

BigCommerce recipes mirror the Shopify set with some platform-specific additions for image compression and StagingPro migrations.

​
Adobe Commerce and Magento recipes

Adobe Commerce recipes focus on the SEO and image surface, with deeper hooks into the Magento extension and audit ecosystem via DryRunPro.

​
Cross-platform recipes

These recipes are not bound to a single storefront and run across whichever connectors the merchant has authenticated.

​
Building your own from a recipe

Most merchants start from a recipe and tweak. Common edits:
  • Change the schedule. “Run weekly instead of daily.”
  • Change the destination. “Post to a different Slack channel.”
  • Change the platform. Take a Shopify recipe and reuse it for BigCommerce, the agent reassembles the read tools.
  • Add a step. “Before posting, ask Ask Viq for the trend explanation and include it in the message.”
  • Add an approval gate. “Send to me first for review before posting publicly.”
After your edits, deploy to sandbox, test, promote. The recipe history is preserved so you can compare your customised version with the original.

​
Frequently asked questions

Are these recipes free to use, or do they cost extra? Recipes are part of App Builder. Whatever your plan covers for App Builder runs covers running a forked recipe. There is no per-recipe charge. Will Vortex IQ add new recipes over time? Yes. The recipes library is a living catalogue. New recipes are added as common workflow patterns emerge from merchant builds. If you build something useful, you can submit it as a candidate recipe. Can I share my own custom apps as recipes inside my workspace? Yes. Any app you build can be marked as a workspace recipe, making it visible to other users in your workspace as a starter template they can fork. Do recipes work the same across plans? The recipe definitions are universal. The tools each recipe uses depend on which connectors are authenticated and which features your plan includes. A recipe that depends on a connector you have not authenticated will prompt you to connect it before deployment. Can a recipe call another recipe? Yes, via sub-agent composition. A parent recipe can delegate work to a child recipe (for example, the Brand DNA recipe is used as a context provider by content-generating recipes). The merchant does not need to wire this manually; the recipe declares its sub-agent dependencies. What if a recipe stops working because a platform changed its API? Vortex IQ maintains the underlying connector library. When a platform changes its API, the connector is updated and any recipe that uses it continues to work without merchant intervention. If a deeper change is required, the recipe is versioned and a migration prompt is shown the next time the merchant opens the app. Can I see which recipes other merchants use most? Aggregate usage data is not exposed individually for privacy reasons. The recipes most popular across the V1 Agent Hub were KPI Agent, Image Optimisation Agent, Pages SEO Agent, Product SEO Agent, and Google Ads Performance Agent, in roughly that order. App Builder will surface usage trends inside your own workspace as the catalogue grows.