Playbook inputs and resources

A Playbook can receive text, files, images, links, and other multimodal input. Choose how users supply work, then add the reusable material that every run needs.

Choose an input

Every Playbook has a chat or form input configuration.

• Chat is the default. Use it when each request varies. You can allow file uploads when the process needs them.
• Form collects a known set of fields. A form can use text, number, single-select, file, and description fields.

Schedules and app events are launch mechanisms. They start a Playbook, but they do not replace its chat or form input configuration. Email-triggered Playbooks are planned for a future release.

Use forms to set boundaries

Use a form when the process requires named fields or files. Forms reduce ambiguity and give every run a predictable starting point. They are useful for review requests, recurring reports, and document packages.

Add resources

Resources are reusable material available to every run. They can include file templates, spreadsheets, lookup tables, reference documents, knowledge bases, and scripts.

Add a resource when every run needs it. For example, add a report template when every run must use the same layout. Add a policy document when every run must follow the same rules.

Do not use resources for one-off input. Submit one-off files with the individual run.

Technical notes

V7 Go must mount every required resource before a run starts. If a required resource is missing or unreadable, the run does not start. This prevents a result that appears to follow instructions but lacks the required source material.

Use a resource for a reusable template or reference. Use an input attachment for material that belongs to one run only.

Next steps

• Create a Playbook
• Schedule Playbook runs
• Review Playbook runs