Skip to main content
In the message box, describe what someone needs to do with the app. Type @ to choose the Salesforce objects it should use.

​
Write a useful first prompt

Name the task and who it’s for. Add the fields, filters, and actions that matter. If you have a layout in mind, describe that too. For example, “Build a sales dashboard” leaves the scope open. This gives Wisty a clearer starting point:

Build a list of open opportunities closing this quarter for our sales managers. Show Opportunity Name, Account, Stage, Amount, and Close Date. Add a stage filter and sort by Close Date. Keep this app read-only.

You can refine the result afterward. A follow-up such as “Add a search box for Opportunity Name” is enough for a focused change.

​
Mention your Salesforce objects

  1. Check the selected org on Home before starting a project.
  2. Type @ and search for an object by name.
  3. Select a result to insert an object chip, then continue your message.
The picker includes standard and custom objects. Wisty uses the selected object’s real field names and relationships when building. If your org uses a custom field, name it in the prompt: “Use Renewal_Amount__c for the renewal value.” You don’t need to mention every related object. Wisty can look up object metadata as it works. Mentions help it start in the right place. For conventions you want to reuse across projects, add org knowledge.

​
Prompts to start from

​
Review a case backlog

Select Case from the @ picker, then add:

Build a case backlog board for support leads. Group open cases by owner, show their age and priority, and add a priority filter. Let me open a case in Salesforce from the board.

​
Use an existing report

Build a weekly sales dashboard using our existing Pipeline by Stage report. Show the report results and a chart of opportunity amount by stage.

Tell Wisty which report you mean if it needs more detail. Using report data requires Reports & analytics reads; Wisty can ask you to allow that access.

​
Update next steps

Select Opportunity from the @ picker, then add:

Build a list of my open opportunities with Name, Stage, Close Date, and Next Step. Let me edit Next Step for one opportunity at a time.

This needs Create & edit records. Follow Update Salesforce records to understand approval and test the change.

​
Build for a record page

Select Account from the @ picker, then add:

Build a panel for an Account record page. Show that account's open opportunities and recent cases. Include links to open those records in Salesforce.

For a record-specific project, set a preview record before testing. See Add an app to Salesforce when you’re ready to place it on a page.

​
Use a reference image

Click Add image in the message box, paste an image, or drag one into the composer. You can attach up to 3 PNG, JPEG, or WebP images per message. Explain what to borrow: “Use this screenshot’s layout, with our Opportunity fields” is more useful than an image alone.
Your messages and attached images are supplied to the generating model. Remove record values or other information you don’t want to include. Wisty doesn’t retrieve Salesforce records for generation; content you provide in chat is a separate input. See How Wisty uses your data.

​
Keep the task within Wisty’s scope

Wisty builds interfaces over your existing Salesforce org: lists, dashboards, record viewers, and forms. It can create, update, or delete records when those actions are enabled and approved. It doesn’t create or change Salesforce objects and fields, Apex, triggers, validation rules, or Flow definitions. Generated apps also can’t call external services directly. If the task needs those changes, complete that setup separately and use Wisty for the interface. Record changes still run through Salesforce’s existing validation and automation. See Update Salesforce records for permissions and approval.