Prompting guide

Guide to writing effective prompts for Autopilot actions, including expressions, workflow generation, and app generation.

Autopilot actions are fixed, pre-defined operations that you trigger in the UI. Each action accepts a single input and returns a single result — there is no ongoing conversation.

For general prompting tips, refer to Writing effective prompts.

Ausdrücke

When generating or fixing expressions, provide enough context for Autopilot to determine the correct data types and operations:

• Specify the data format when working with dates and times (for example, "dd/MM/yyyy").
• Name the data types involved (string, integer, DataTable) so Autopilot selects the right methods.
• For fix requests, include the error message or describe the expected vs. actual behavior.

Sequence generation

When generating sequences through the single-prompt actions in Studio:

• Describe the end-to-end task in a single, self-contained prompt — there is no follow-up conversation.
• Name the specific integrations, activities, or services involved (for example, "using Outlook", "via Salesforce API").
• Specify input and output expectations (file paths, variable names, data formats).

App generation

When generating apps from text, images, PDFs, or Data Service entities:

• For text-based generation, describe the app's purpose and the key screens or interactions.
• For image or PDF-based generation, ensure the source material clearly shows the layout and fields.
• For Data Service entity-based generation, verify that entities and their relationships are defined before prompting.