Prompt engineering tips for designing and building solutions
note
Orchestrate is an Early Access release. Refer to the Early Access disclaimer for details.
The following guidelines will help you write effective prompts for Orchestrate. Solution design is a conversation, interactive chat. You can provide additional prompts to Orchestrate, make refinements to your requests, and ask Orchestrate clarifying questions.
What to include in your prompts
- Source and destination systems
- Data volumes
- Frequency of execution
- Constraints, such as compliance requirements or authentication
- Downstream consumers
- Relevant Meta Hub business glossaries
tip
When building Data Hub models, include details about the fields and data types required for the model.
Recommended Practices
- Clearly describe the desired business outcome
- Identify the systems involved (for example, CRM, ERP, HR platforms), or reference Business Glossaries defined in Meta Hub
- Focus each prompt on a single business problem or process
- Use follow-up interactions to iteratively refine the solution, leveraging Orchestrate's conversational design
- Request an explanation of design decisions before proceeding with asset creation
- Develop the solution incrementally, expanding scope in subsequent prompts. For example, you can tell Orchestrate to add or remove components in the solution.
Practices to Avoid
- Providing full requirements documents or large, unstructured text inputs
- Combining multiple objectives into a single, overly complex prompt
- Prescribing specific Boomi products instead of allowing Orchestrate to determine the appropriate components
- Expecting production-ready assets from an initial prompt
- Using internal or domain-specific terminology without sufficient context
Prompt examples
| Category | Example Prompt |
|---|---|
| Customer & Order Operations | "When a customer places an order, update our ERP, notify the warehouse team, and send the customer a confirmation automatically." |
| Customer & Order Operations | "We need to keep customer records in sync across our CRM, billing system, and support portal in real time." |
| Employee & HR | "When a new employee joins, automatically provision their accounts across IT, HR, and payroll systems and notify their manager." |
| Employee & HR | "I want our employees to ask HR questions in plain language and get answers drawn from our company policies and data." |
| Supply Chain & Partners | "Onboard new suppliers by validating their data, setting up secure access to our systems, and alerting the procurement team." |
| Supply Chain & Partners | "Monitor stock levels across our warehouses and automatically trigger reorder requests when inventory falls below threshold." |
| Data & Reporting | "Consolidate sales data from multiple regional systems into a single view so leadership can track pipeline and forecast in one place." |
| Data & Reporting | "When a support ticket is resolved, update the customer record in our CRM and log the outcome in our data warehouse." |