Declaring the tools a Playbook needs
How a Playbook states which tools it requires, why the requirement is written down before anything is authorised, and where that declaration shows up.
On this page
A Playbook states the tools it needs in its own document, by name, before anyone has authorised anything. That statement is a Connector: a requirement, not an account.
Where it is written
Two places, and they stay in step with each other automatically.
- The Playbook's own list. Its document names every tool the method needs.
- Each step's list. A step names the tools it may call, which is narrower: a Playbook can need a calendar without every step being allowed to reach it.
Attaching a tool to a step also adds it to the Playbook's list, so the Playbook can never declare less than its steps reach for. The registry cannot fall behind the work.
Why it is declared up front
Because a requirement written down can be checked before it matters.
- Before you copy anything. A template's page in the Playbook Library names the Connectors it needs, so you can judge whether it fits your setup before it is in your account.
- While you are building. The setup checklist lists each one and marks the ones with no Connection yet. A Playbook cannot be deployed until they are satisfied.
- Before a run does any work. A required tool with no Connection stops the run at the start, by name. See When access is missing.
The templates declare none
Every template currently visible in the library runs on a brand new account with nothing authorised, which is deliberate: the first thing you try should not require a setup session. URL SEO Audit declares no Connectors at all.
When a Playbook does declare one, the connection is the point. The output is built from the data actually in your account rather than from a guess at it.
More in Connectors
Related
Authorising a tool
Making a Connection: where it happens, what YAMO stores and what it does not, and the question you are asked every time about whose account it is.Playbook scope and Runtime scope
Whose authorised access satisfies a requirement: the operator who wrote the method, or the customer running it. What each scope means and what is built.When access is missing
What happens when a required tool has no Connection: the setup checklist before you deploy, and an honest stop before a run does any work at all.Tools that need no Connection
What a step can do out of the box: search the web, fetch a page, read your reference files and send email, and how each one appears on the receipt.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.