Playbook Generator Agent Reference

the playbook generator agent runs in playbook building mode on playbook and component editor pages it creates or modifies one flow at a time for procedures, see create and modify playbooks with hero ai supported capabilities the agent can create and modify a playbook (individual flow) or a component component modify user defined interfaces (input and output schemas) publish fields to the properties in the output schema playbook add a new flow to a playbook or modify an existing flow add, modify, or delete cron triggers delete record, flow, and webhook triggers modify conditions for record, flow, and webhook triggers add, configure, and delete components available in the tenant add, configure, and delete actions of connectors available in the tenant add or change the asset used by a connector action add, configure, and delete native actions condition, loop, parallel, create/update variable, search records, create record, delete records, scripts, transformations, hero ai connect actions with on success, on failure, and on complete connections not supported (playbook) add, replace, or configure schemas for flow, webhook, or record triggers (component) add or modify existing interfaces (intents) enable or disable a flow via prompt query application records or answer general turbine usage and documentation questions while in playbook building mode (planned for a future release) mark action inputs as sensitive (for example, the hero ai native action prompt) use variables from assets unless they are mapped to connector actions test or run components or playbooks from a prompt reference playbook or component runs create or edit multiple flows from a single prompt notes and considerations prompts in hero ai native actions, python scripts, and jsonata transformations are not validated and may be incorrect complex (multi level, multi group) filters in loops, conditions, search records, and trigger conditions might not be fully correct filters by attributes with predefined list values are not supported in search records for end to end validation, use the test console