Connectors
Connectors are the tools a Playbook calls: your calendar, your inbox, the systems your work already lives in. They are how a run uses your data instead of guessing at it.
Two words do the work here and they are not the same thing. A Connector is what a Playbook says it needs. A Connection is the access you authorised that satisfies it.
- Declaring the tools a Playbook needsHow a Playbook states which tools it requires, why the requirement is written down before anything is authorised, and where that declaration shows up.
- Authorising a toolMaking 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.
- Operator, customer and built-in scopeWhose 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 missingWhat 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 ConnectionYAMO-provided capabilities need no personal Connection, but still require declared access and limits. See how their use appears on a Run receipt.