Connectors

Connectors give the worker agent access to third-party services, such as web search, Gmail, and many others. A connector exposes a set of tools the agent can call during a run, and some also offer events that can start a job. See triggers for those.

Configured per job

Connectors are set up per job. Each automation has its own connector configuration, so a job only reaches the services you grant it. Two jobs can use entirely different sets of connectors.

You can narrow it further within a connector by allowing only specific tools, so a job that drafts replies does not also get the ability to send them. Leave the selection open and the job gets everything that connector offers.

Where your credentials live

Connecting a service runs its normal sign-in or key setup, and the resulting credential is held in a vault at Composio, our connections provider, scoped to your account. Golemry records which services you have connected. It does not store the tokens themselves.

When the agent calls a connector tool, the call is carried out on the vault side, which attaches your credential there. The token never reaches the machine your job runs on, so it cannot be read out of a run, written to a file, or included in a result.

The agent sees results, not secrets

The worker agent gets what a tool returns and nothing more. Your LLM key works the same way: it runs the job but stays out of the agent’s reach. See the data and security page for what is stored and for how long.