PYLO Connectors
Base44
Connecting Base44 to PYLO, what it brings and how to tell it is working.
Base44 connects to PYLO so that:
- Leads, calls and outcomes, EOD reports and payments kept in a Base44 app count in PYLO's figures, through the mapping you save.
- A client who runs their business in Base44 does not have to move it to use PYLO.
Connecting
Base44 connects by an API key you paste into PYLO. Open Settings, then Integrations, then Base44.
| You provide | Where to find it |
|---|---|
| Personal access token | In Base44, open workspace settings, then Secrets, and create a personal access token. Paste all of it. An older account API key works only until 15 October 2026, when Base44 stops accepting them, and PYLO marks a connection still using one. |
| app id | The long id in your app's Base44 address, after /apps/. For example 6a9197858fa7303c55f9a51f. |
| one table name | Leave this empty. PYLO finds your app's tables itself, and asks for this only when your token cannot list them: then type the name of one table (an entity in Base44), such as Lead. Not a field such as name or email. |
Before you start: Base44's App Management API is in beta. Base44 may change it without notice; when it does, PYLO stops reading and says so here rather than guessing.
What PYLO reads
- The records of every entity you map, and the names of the app's entities
It does not read:
- Entities you do not map
- Records deleted in Base44: PYLO keeps what it already imported
- Anything outside the one app this key and app id name
Base44's own documentation: https://docs.base44.com/developers/references/apps-api/get-started/authentication