Base44: `connectors pull` Command for Local OAuth Config Sync
Base44Base44 added a connectors pull CLI command that downloads OAuth connector configurations from the cloud to local .jsonc files in the project's connectors directory. The command performs a full bidirectional sync: remote connectors are written locally, and local connectors with no remote counterpart are deleted.
Sources & Mentions
2 external resources covering this update
Pulling OAuth Connector Configs Locally
Base44 extended its CLI connector management with a connectors pull command, completing the two-way sync model for OAuth integrations. The command downloads all connector configurations from Base44's cloud to local .jsonc files stored in the project's base44/connectors/ directory.
How the Sync Works
The pull operation follows a clear merge strategy:
- Connectors that exist both remotely and locally are overwritten with the remote version — the cloud is treated as the source of truth.
- Remote connectors that do not yet exist locally are created as new
.jsoncfiles. - Local connectors with no corresponding remote counterpart are deleted from the local directory.
This makes connectors pull a destructive operation for any locally-crafted connector files that haven't been pushed first.
Completing the Round-Trip Workflow
connectors pull pairs with the existing connectors push command to enable a complete round-trip workflow for OAuth connector configuration. Developers can now pull the current state of connectors into their local repository, commit the .jsonc files to source control, and push changes back to Base44 after editing.