Pro Tips for Turbine Automation
Introduction
These are the top tips and course insights you'll see throughout the Fundamentals of Turbine Automation
course and lab challenges. Keep this sheet handy as you build, test, and refine your Playbooks.
Planning & Playbook Design
• Always include a Playbook Description to keep your automation library organized.
• Add your Trigger at the right time: add time-based triggers last, data-based
triggers first.
• Use descriptive names that clearly reflect purpose.
• Title every action to make your Playbook logic readable.
• Reuse existing Components or Playbooks before creating new ones.
• Build single-purpose, modular Playbooks for clarity.
Applications, Fields, and Hero AI
•
•
•
•
•
•
Add field and application descriptions to help Hero AI understand data context.
Use placeholder text thoughtfully to improve usability and AI accuracy.
Add Help Text only when necessary for infrequently used or unclear fields.
Avoid unbounded lists - use reference fields or Applications instead.
Use Workflow to show only relevant fields to users.
Be mindful of data limits: 100MB per record, 30MB per field.
Building Logic & Data Transformation
• Use Transform Data for simple conversions and JSONata for complex transformations.
• Comment advanced JSONata expressions for maintainability.
• Name transformation blocks descriptively to make Playbooks easier to read.
• Include loop exit conditions and avoid unnecessary iterations.
• Group record updates into a single Upsert for efficiency.
• Use Variables strategically with clear, descriptive names.
Testing & Troubleshooting
• Test incrementally - validate small sections before running the full flow.
• Inspect schema output after key actions to confirm structure.
• Use log messages to verify variable values and data transformations.
• Validate authentication and mappings before deploying.
• Document lessons learned for future Playbook improvements.
Copyright 2025
Content & SSP Considerations
•
•
•
•
Write detailed descriptions for all Playbooks, Components, and Applications.
Name consistently to simplify maintenance and content export.
Include all dependencies before exporting Solution Support Packages (SSPs).
Build modular Playbooks to support reuse across projects.
Widgets & Visualization
•
•
•
•
•
Limit the number of widgets per dashboard to improve performance.
Combine related functionality into fewer, multi-purpose widgets.
Include configuration details in widget headers for clarity.
Avoid hardcoding values; reference Application fields where possible.
Design widgets for reuse in multiple contexts.
And finally...a few quick reminders!
• Title every Action and Transformation block.
• Duplicate actions instead of rebuilding.
• Save often.
• Think like an automation architect - solve problems, not just tasks.
• Iterate and test continuously.
Copyright 2025