Connectors and Connections are not the same
A Connector is the tool a Playbook says it needs. A Connection is the authorisation that lets a run reach it. Two words, and the difference matters.
On this page
These two words look like a spelling variation and they are not. Getting them the wrong way round makes it impossible to say who is responsible for what, so it is worth five minutes once.
A Connector is a declaration
A Connector is a tool a Playbook says it needs in order to run. It belongs to the definition, so it travels with the Playbook: whoever copies that Playbook gets the same declaration, because the method genuinely does depend on that tool.
Declaring one is not the same as having access to it. A Playbook can name a Connector for years without a single run ever reaching the tool behind it.
A Connection is an authorisation
A Connection is what a person creates when they authorise one of those tools. It binds an actual account to the capability the Playbook asked for, and it belongs to whoever gave the authorisation rather than to the Playbook.
| Connector | Connection | |
|---|---|---|
| Belongs to | the Playbook | the person who authorised it |
| Travels when copied | yes | no |
| Answers | what does this method need | what may this run reach |
Why keep both words
Because collapsing them into one loses the thing that matters: a method can be shared, and an authorisation must not be.1 Publishing a Service hands somebody the declarations. It never hands them your access.
The Playbook says what it needs. You say what it may reach.One sentence version
Notes
- 1The catalogue of available Connectors is not a hand-kept list in this repository; it resolves through an external registry, which is one reason there is no page here per tool yet. ↩
Read next
What a Playbook actually is
A Playbook is the method an expert captures, written down as a document the runtime follows. What goes in it, what a Play is, and what stays yours.What one run includes
A run is one execution of a Playbook, from the trigger that started it to the artifact it returns. It is also the unit that gets metered and receipted.The method is the asset
An expert who has delivered the same outcome enough times owns a method. Doing the work again by hand for every customer is what that method costs them.From Playbook to published Service
Publishing turns a Playbook into a Service that other people can pay to run. What the public contract says, and what a customer gets when they buy.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.
Read a Playbook that does this
Every template in the library publishes its contract and a real example output.