Getting started
From a template to your first finished run: copy a Playbook into your account, fill in what it asks you for, run it, and read what comes back.
On this page
Build a Service around the work you want done. Start with a brief or a template, finish its setup, then run it privately. Publishing is a separate choice.
The Service's underlying definition is its Playbook: the instructions, steps and Resources used to produce an Outcome.
1. Copy a template
Browse the Library, choose a template and use its copy action. Read its required inputs, Connectors and example Outcome before choosing it. The copy belongs to your account; later changes to the original template do not rewrite it.
To start without a template, open Create a Service, describe the work and choose Shape this Service. See Build from scratch.
2. Make it yours
Use the Service's document and conversation to refine the goal, Outcome, rules and Resources. Replace example Reference files with your own information and connect the tools the Service needs.
YAMO helps author the definition, then build its steps. Review what is saved and resolve the setup items. A copied template is a starting point, so check its assumptions before using its Outcome.
3. Deploy, then run the private Service
Deployment is automatic when the owner-side readiness checks pass. There is no separate Deploy button. The Service becomes private and runnable; it is not published.
Open an Instance, supply its required inputs and customer-side Connections, and confirm the Run. Runs continue in the background. The Instance keeps the conversation, Run history and finished work.
Read the Outcome, step evidence and receipt when the Run finishes. If it fails or needs approval, inspect its recorded status and explanation before continuing.
Where next
More in Docs
Related
Reference files
Your knowledge layer: account references every Playbook can read, Playbook references scoped to one method, and placeholders for what is missing.Concepts
The words YAMO uses, defined one to a page: Playbook, Play, Service, Instance, Run, Connector, Connection and Reference file, and how each relates.Run
What happens when a Playbook is carried out: what a run asks you for, what starts one, what it produces, and how the finished work reaches you.Build
Making a Playbook: starting from a template or from a description of the work, writing the steps, and getting it ready enough to deploy and run.Publish
Putting a Service on your Front Office: what the listing asks for, what has to be true before you can publish, how it is priced, and how you get paid.Connectors
The tools a Playbook calls to do its work: how one is declared, how you authorise it, whose access satisfies it, and what a run does when it is missing.Pricing
How YAMO charges: you pay for the runs you make, and nothing for the ones you do not. What a run is, what it includes, and what publishing costs.Who it's for
The six kinds of expert YAMO is built for, and what changes when the method you already follow becomes a Service that somebody else can run.
Open a Playbook that does this
Every template in the library publishes its contract and a real example output.