Tools that need no Connection

Not everything a step does needs a Connection. Some capabilities are part of the runtime, available to any Playbook, with nothing to authorise.

What a step can do out of the box

• Search the web. A step can declare that it searches while it works, and the results inform what it writes. URL SEO Audit's research step does exactly this, which is how it can audit a page it has never seen.
• Fetch a page. Retrieve a URL and read it.
• Read your reference files. Every file the step declares is resolved into its context before it starts. See Reference files.
• Send email. Deliver something to an address.

None of these is a Connector, so none appears on the setup checklist and none can block a deployment.

They are metered

Each of these is an operation, and operations are one of the two lines on a run's receipt. Searching, fetching, reading files and sending email each record what they did, and the receipt names them in plain words: web searches, pages fetched, files read, emails sent.

That is what YAMO charges for on your own runs, alongside the model cost passed through at what we paid for it. See Your YAMO balance.

Reading a large file

A reference file is read into the step that declared it, and a very large one is trimmed rather than refused. Worth knowing if a Playbook depends on the tail of a long document: the step sees the beginning of it.

Where the line falls

If it needs your permission at somebody else's service, it is a Connector and you authorise it. If it does not, it is one of these. That is the whole distinction.