PYLO Settings: Integrations and automations
Tool capabilities
What PYLO can do in each of your tools and how, the step packs it runs in your browser, and whether each run was proved.
Tool capabilities shows what PYLO can do in each tool your workspace uses, and how it does each thing for this workspace today. It also lists the step packs PYLO runs in a browser and every browser run with its proof.
Who can open it
Owners and admins. It is read only: agents plan the work and you approve it under Approvals.
How PYLO does a task
For each thing PYLO can do in a tool, it tries these in order and uses the first that works:
| Method | What it means |
|---|---|
| By API | PYLO makes the change through the tool's own API, for example adding a choice to a Close field. |
| From a snapshot | PYLO copies the agency's own template, for example a blueprint's CRM setup. |
| Step pack in your browser | The agent follows PYLO's step pack in your own signed-in browser. PYLO never holds your password. |
| Explore mode in your browser | There is no pack yet. The agent works from PYLO's map of the tool's screens, and the run is recorded as a draft pack for next time. |
| A person | Only a person can do it: going live, paying, identity checks, signing in. |
Where a tool has an API but PYLO has no writer for it yet, the screen says so and PYLO uses the next method. It never offers a route nothing would carry out.
Some things are refused by decision and say why: PYLO never changes Meta campaigns or spend, never deletes anything in a client's Close, never books a test meeting, never posts in a WhatsApp group, and does not build Notion hubs.
Done means proved
A browser step is done only when a read proves it: the tool's API shows the result, the page loads with it, or the settings screen read back after the run shows every planned value. A screenshot you confirm leaves the step claimed, not done.
Step packs
Each pack lists its version and its standing. "Never verified by a run" means its steps come from the vendor's help pages and no run has proved them yet. When a tool's screens change, the run reports drift: after one drift the pack is flagged for a refresh, and after two it waits for a person to re-record it.
The hosted browser
PYLO's own hosted browser is off. No logins or sessions are stored. Steps that would show a key on screen are left to you, and you hand the key over with a key drop.
From your agent
plan_tool_task plans a small task in any tool, for example "move the 1-hour reminder to 30 minutes" or "turn on the replay chat". get_tool_capabilities lists what PYLO can do in a tool, and get_tool_map says where things live in its screens. For a browser line, the agent uses get_step_pack, start_browser_run, report_step and finish_browser_run, and record_step_pack saves an explore run as a draft pack.