Describe the feature you want

You can build an app around an AI assistant, add AI actions to its forms and records, or combine both. AppJuice provides shared AI capabilities and ready-made conversation interfaces that Builder can add for you. Describe what the user should be able to do, what information the feature needs, and where the result should appear.

For example: “Add a button that turns the notes in this form into a short summary. Show the result below the form so I can edit it before saving.”

Add an assistant

Ask for an assistant when people should be able to discuss a task, ask follow-up questions, or let it choose steps and tools. Tell Builder whether the conversation should be a main page, a side panel, or a small expandable chat button.

Example request: “Add an assistant beside the itinerary. It should use the selected trip, ask before changing dates, and keep a separate conversation for each trip.”

Builder connects the assistant to your app's records and controls. Test that it receives the correct information and that an approved change updates the intended record.

Use the ready-made Agent Conversation component

Agent Conversation is AppJuice's shared AI conversation interface. Ask Builder to place it in your app as a main view or beside the app's own content. It provides the conversation controls, so you can focus on what the assistant should do.

  • Conversations and input: saved sessions, attachments, and voice dictation when a speech service is configured.
  • Task controls: tool activity, approval requests, guidance during a task, and Stop.
  • Answers and choices: formatted text, tables, formulas, diagrams, sources, interactive choice cards, and drafts.
  • Generated files: artifact cards, supported file previews, and available save, copy, or share actions.

These features depend on the app's tools, connected services, and device support. Adding the interface does not automatically give the Agent access to every app record or external service.

Example request: “Use AppJuice's Agent Conversation component beside my project list. Give the assistant the selected project's details and let me ask it to prepare a progress report.”

Use a compact Chat Widget

Choose Chat Widget when the app's main screen should remain a form, list, or dashboard. It provides an expandable conversation entry point that users can open when they need help.

Example request: “Add an expandable assistant to the inventory screen. It should answer questions about the selected item without replacing the main inventory view.”

For a working example, see Nectra's book assistant beside its reading interface. One Shot shows the full conversation interface used as the main app view.

Connect the conversation to your app

Tell Builder which information to share with the assistant and which actions it may perform. For example, it might read the selected trip, propose a revised itinerary, and update dates only after confirmation.

You can also ask Builder to adapt the heading, introductory text, colors, and placement to fit your app. Describe the result you want; component attributes and API calls belong in the developer reference.

For the everyday controls used inside these conversations, see Working with agents.

Add a specific AI action

Use a defined action when the input and result are already clear: summarize a note, transcribe an uploaded recording, generate an image, or read an eligible web page. Ask Builder to add the action to the relevant form or workflow.

Example request: “Add a Transcribe button for uploaded audio. Show progress, let me edit the transcript, and save it only when I confirm.”

Builder can use AppJuice's Direct AI helpers. Check AI Capabilities for the service needed by that action. A text model alone does not provide every media capability.

Use your configured AI services

Tell Builder when the app should follow your configured model preferences, use a particular service, or work with a local model. AppJuice's APIs share the platform's supported provider connections.

Example request: “Use the AI services configured in AppJuice. If no transcription service is ready, explain how to connect one instead of leaving the button stuck.”

Provider choice still needs to match the task. If local inference is a requirement, ask Builder to check every AI feature and online tool involved.

Add files and service access

Describe the intended file operation: upload one document, choose a folder, preview a generated report, or save it to a chosen destination. AppJuice provides shared file and preview capabilities where supported by the device.

For an external service, say which records the app needs and whether it may only read them or also change them. Configure requested credentials in Platform Vault, rather than pasting secret values into the app's interface or conversation.

Add specialized Agent roles when needed

An app can use several Agent roles for different parts of a task. Describe the roles and the result you expect, such as independent reviews followed by one combined recommendation.

Ask Builder how partial failures and retries will be handled. Several Agents can use more time and model calls; a single assistant may be sufficient.

Try the complete workflow

  1. Provide an ordinary example input and check the result.
  2. Try a missing file, an unavailable service, or a cancelled task.
  3. Confirm that changes are saved to the correct record or location.
  4. Try the workflow on the devices where it will be used.
  5. Ask Builder to fix any unclear feedback or unwanted behavior.

For people working directly with code

The Agent and AI API reference contains minimal examples for embedded conversations, Agent invocation, Direct AI helpers, and file access. These interfaces are for apps running inside AppJuice.