Settings: Integrations and automations

Keys

The keys this workspace has given PYLO, whether each still works, and how to hand PYLO a key from your terminal or a link without it passing through a chat.

Read as Markdown

Keys lists every key this workspace has given PYLO for a tool that connects with a key rather than a sign-in button: Close, GoHighLevel's private integration, Calendly's personal token, WebinarJam, iClosed, Base44, Brevo and the rest. For each one you see whether its last test passed, which account it belongs to, when it was last used, when it expires and when to replace it. PYLO never shows a key once it is saved, here or anywhere else.

Who can open it

Owners and admins.

Key drops: a key without a chat

A key pasted into a chat stays in that chat's history, and a key kept in a plain file on a server is one copy too many. A key drop hands PYLO one tool's key for one workspace directly, and nothing else sees it.

There are two ways in:

From your terminal. Your agent calls create_key_drop and gives you a command such as pylo keys put close --drop pykd_.... Run it in your own terminal. It asks for the key in a hidden prompt, or reads it from an environment variable (--from-env CLOSE_API_KEY), a file you name (--file ./close.key) or stdin, and prints only "received" and the test result. A drop works once, for 15 minutes, for the one tool and workspace it was made for.
From a link. The same drop has a link with a hidden field for the key. create_connect_link can also make one key-drop link that collects every key the workspace is missing, to send to a client. It only ever asks for keys, never a username or password.

PYLO stores the key exactly where saving that tool's key has always stored it, encrypted, and tests it at once. Your agent then calls get_key_drop_status and hears, for example, "Received, tested ok, account: Close org Partner, scopes: read, write". The Key drops section of this page lists every drop and its result.

A key that fails its test is not kept. Ask for a new drop once you have the right key.

The PYLO CLI

The pylo command is a small program with no dependencies, for Node 20 or later.

Run pylo login. It prints a short code and a PYLO address.
Open the address, check the code matches your terminal, and choose Approve. Only an agency operator can approve, and the agency must be on the Pro plan.
The terminal keeps a token that can make key drops and test keys for your agency's workspaces, and nothing else. It is saved in ~/.config/pylo/credentials, readable by you only, and listed under Agency settings, Agent tokens, where you can revoke it.

Then:

pylo keys put <tool> --drop <id> sends one key to a drop.
pylo keys import .env --workspace <id> sends every key PYLO recognises in the file, one drop each, then offers to delete the file.
pylo keys list --workspace <id> and pylo keys test <tool> --workspace <id> show key names and test results, never values.

The CLI refuses a key typed on the command line, because your shell history would keep it.

A key pasted where it should not be

No PYLO tool takes a key, password or code as an argument. If an agent passes one anyway, PYLO refuses the call with refused.secret_in_argument, does not log the value, and records which tool it probably belongs to so you can replace it. Treat that key as exposed: create a new one in the tool, drop it into PYLO, then delete the old one.