Skip to main content
Upload local OAuth connector configurations to Base44. The command reads all .json and .jsonc files in your base44/connectors/ directory and syncs them with Base44. Connectors require OAuth authorization before they can be used with the SDK. When pushing connectors that need authorization, the CLI prompts you to authorize each connector one by one. The CLI will suggest opening your browser automatically, and if you accept, it iterates through each integration’s authorization page sequentially. You can also use the displayed OAuth URLs to authorize manually. You can push connectors without completing authorization, but they won’t be usable until you authorize them. Run connectors push again later to complete authorization. If you push a connector with the same scopes it already has, you won’t need to reauthorize.
Connectors cannot be created or configured through the Base44 dashboard. You must define them in local configuration files and push them using the CLI.
This is a full sync. Remote connectors not present locally will be removed. See the Sync behavior table below for details.

Usage

base44 connectors push

Sync behavior

The command performs a full sync for connectors:
Local stateRemote stateResult
Connector existsConnector existsRemote connector scopes are updated.
Connector existsConnector doesn’t existNew connector is created and requires OAuth authorization.
Connector doesn’t existConnector existsRemote connector is removed.

See also