Connectors are the tools a Playbook calls: your calendar, your email, the systems your work already lives in. They're how a run uses your data instead of guessing.

Declared, not discovered

A Playbook states the Connectors it needs in its own document. That declaration shows up everywhere you'd want it:

on the template's gallery card and library page, before you copy anything,
in the builder, where the header counts Connectors still to connect and the Resources tab marks each one until the connection exists,
at run time, where a missing connection stops the run honestly instead of producing output that pretends.

The seed templates need none: every template in the gallery runs on a fresh account. When a Playbook does declare a Connector, say your calendar, the connection is the point: the output is built from the data actually in your account, not a guess at it.

Connecting one

Connections are made once, at account level: browse the connector library from the Resources tab (or Settings → Connected Tools), sign in to the tool, grant access, done. Every Playbook that declares that Connector then finds it. Disconnecting a tool marks it not connected again for every Playbook that relies on it.

What a run can do with it

Plays call Connectors to read and act: read the week's events, fetch a document, send the digest. Calls a run makes are operation charges on the run's receipt, itemised like everything else. Where an action deserves a check before it happens, give the Play a human gate. See Run.