See the Triggers and history guide in the Digital Worker documentation for the complete walkthrough.
Choose one YAML file and merge its invoke block into the existing refund-helper agent.yaml from the complete customer-care sample. Preserve the other agent fields. Copy prompts/ into that agent folder. application-invoke.yaml belongs in application.yaml instead.
These are fragments, not deployable application bundles. Do not upload this ZIP as an application. When combining variants, keep one invoke block, one manual list, and one chat entry with unique trigger IDs.
Manual triggers execute in the reviewed I0/I1 implementation. Schedule, interval, event, and workflow examples validate but their unattended runtime paths are unavailable. They must remain configuration examples until supported and admitted. No scheduler or recurring task was enabled to produce this documentation.
Validate the whole application with helixor agent check customer-care. Read the diagnostics and budget projections. Only deploy after reviewing the target and intended changes.