A Practical Guide to Resources
Resources are pre-connected modules that give your AppWeb or flow advanced capabilities, such as showing interactive maps, processing payments, talking to LLMs, or generating images, without writing any code or dealing with external APIs.
1. Resources in AppWeb Studio (Canvas)
In Canvas, you request resources from Copilot as part of the chat message (when creating or iterating). There are two key moments:
In the Copilot message
Ask for resources in the Canvas chat. Example: "Create a landing page for a clinic. I need a map in the contact section, a booking form, and use AI-generated images of doctors."
While iterating
If the app already exists, send another message in Agent mode (or ask for a plan and run Build): “Add a Geoapify map on contact” or “Integrate Stripe payments in checkout.”
2. Resources in Hub Flow and Channels
Some resources are exclusive to the flow engine (Hub Flow). These resources aren't inserted into buttons or visual containers; instead, they're part of the logic of an automation on channels like WhatsApp or Telegram.
- File handling: Receive PDFs or voice notes sent by the user via WhatsApp.
- Interactive lists: Send native WhatsApp Business catalogs or menus.
- Invoice OCR: Process images sent to the bot to extract structured text.
Mind your expectations
If you see a resource marked as "Flow Only" in the catalog, it means you can't embed it in a button on your AppWeb. It will only work as a logic node in the conversational flow builder.
3. Resources and Hub AI Credit
Connecting Stripe or inserting a map on the canvas does not debit credit by itself. What uses Hub AI Credit is AI model usage: Copilot in Studio and AI calls from your visitors in production.
Generating with Copilot, or a visitor creating an image with FLUX.2 / chatting with an LLM in your published app, debits your single euro balance.
Configuring Stripe, maps, or other capabilities without model calls does not spend Hub AI Credit (they may have their own external costs).