Build Process Models with Composer

This page explains how to use Composer to create and configure process models using natural language.

Where to use Composer for process models

You can ask Composer to create and update process models from the Build view or from AI mode in an interface object.

Composer uses your permissions. If you cannot create or edit an object, Composer cannot do it for you. Composer follows the same object-level security as manual edits.

What Composer can do with process models

Composer can perform the following operations on process models:

• Create new process models: Build a new model from scratch based on the workflow you describe.
• Configure process workflows: Add nodes and configure smart services to create fully working process models with proper flows.
• Set up timer events: Configure scheduled execution, delays, and recurrence patterns with proper time zone handling.
• Add integration calls: Insert Call Integration nodes that include input and output mapping, as well as error handling.
• Add email nodes: Create Send Email nodes with email templates that use dynamic content and HTML formatting.
• Create user input tasks: Build interfaces with task assignments and form wiring.
• Configure record operations: Set up data operations such as Write Records, Sync Records, and Delete Records with proper batch handling.
• Add script tasks: Incorporate and configure script tasks within the workflow for custom logic.

Example prompts for process models

The following prompts show requests that work well when asking Composer to build process models. For general prompting guidance, see Composer Best Practices.

Goal	Example prompt
Approval workflow	Create a process model that routes a purchase request to a manager for approval. If the amount exceeds $10,000, add a second approval from the finance team.
Timer-based scheduling	Add a timer event that runs this process every weekday at 8:00 AM Eastern Time.
Integration call	Add a Call Integration node that calls the Salesforce connected system, maps the account ID as input, and stores the response in a process variable.
Email notification	Add a Send Email node that notifies the submitter when their request is approved. Include the request title and approval date in the email body.
User input task	Create a review task assigned to the HR group with an interface that shows employee details and lets the reviewer approve or reject.
Record operations	Add a Write Records node that saves the updated case record after the approval step. Include error handling for write failures.
Script task	Add a script task that calculates the total cost by summing all line item amounts and stores the result in pv!totalCost.

How Composer uses process model context

When you ask Composer to build a process model, it reads the following context from your app:

• Process models: Existing process models, their nodes, and flow connections.
• Process variables: Process variables and their data types.
• Record types: Record types and their fields, used for data operations and mappings.
• Integrations: Integration objects available in the app that can be used with the Call Integration smart service.
• Interfaces: Interfaces that can be used as user input tasks or process start forms.
• Groups: Groups used for task assignment or as recipients for the Send Email smart service.

Composer uses this context to generate valid node configurations that reference the correct variables, record types, and integrations to fulfill your request.

Review and apply process model changes

After Composer builds or modifies a process model, open the process model and verify that the flow is correct and uses the appropriate nodes and smart services. You can run the process in debug mode to verify its behavior.

If the generated process model does not match your intent, ask Composer to adjust it. You don't need to repeat your original request—Composer retains the conversation context.

All Composer changes go through Appian's versioning system. You can undo them with the same version history tools you use for manual edits. Each update creates a new object version, so you can compare diffs and roll back.

Review changes in detail

If you want to see exactly what changed between two versions of your process mode, open the diff view:

1. In the process modeler, select File > Versions.
2. In the Versions grid, find the version you want to compare to and click Compare with Latest Version.

Feedback