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 |
|---|---|
| API key | In Base44, open your account settings, then API keys. A read-only key is enough unless you turn on write-back for an entity. |
| app id | The id in your app's Base44 address, after /apps/. |
| one entity name | Only if PYLO asks for it: the name of one table in your app, such as Lead. PYLO reads a record from it to prove the key works. |
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/api-reference/count-app-users