This page is part of an AI coding agent skill and is written for agents, not humans. For the human-readable Base44 docs, see the developer documentation.

base44 connectors push

Push local connector configurations to Base44, synchronizing scopes and handling OAuth authorization.

Usage

npx base44 connectors push [--dir <path>] [-y]

Options

Option	Description	Required
`--dir <path>`	Directory to read connector files from. Only used with `--app-id` (no local project); defaults to `./connectors`	No
`-y, --yes`	Skip confirmation prompt	No

Confirmation Prompt

This push overwrites your app’s connectors with your local copy and removes any not present locally. Before pushing, the CLI warns you and asks for confirmation:

$ npx base44 connectors push

Found 2 connectors to push: googlecalendar, slack
⚠ This will overwrite your app's connectors with your local copy and remove any not present locally.
? Are you sure you want to continue? › Yes

In non-interactive mode (--json, CI/CD, no TTY), you must pass -y/--yes or the command throws.

Projectless Mode

connectors push can run without a local project by passing --app-id (or setting BASE44_APP_ID). In that mode there’s no config.jsonc to read connectors from, so files are read from ./connectors by default — override with --dir.

JSON Output

Pass the global --json flag to get a machine-readable result instead of human-oriented log lines and prompts (OAuth authorization is skipped automatically in --json mode, same as any non-interactive run):

npx base44 connectors push --json

What It Does

Reads local connectors from your base44/connectors/ directory
Syncs with Base44 - updates scopes for existing connectors
Adds new connectors - new OAuth connector types trigger authorization; Stripe is provisioned automatically
Removes unlisted connectors - connectors not in your local files are removed from Base44

OAuth Authorization Flow

When you add a new connector, it needs to be authorized:

The CLI detects which connectors need authorization
You’re prompted: “Open browser to authorize now?”
If you accept, the browser opens to the OAuth provider (Google, Slack, etc.)
You log into your account and approve the requested permissions
The browser closes and the CLI confirms authorization

Important: You choose which account to connect by logging into it during the OAuth flow. For example, if you have multiple Google accounts, you select which one to use in the Google login screen.

Example Output

Pushing connectors (no new authorization needed)

Found 2 connectors to push: googlecalendar, slack
✓ Connectors pushed

Summary:
  Synced: googlecalendar, slack

Pushing new connectors (authorization required)

Found 3 connectors to push: googlecalendar, slack, notion
✓ Connectors pushed

2 connector(s) require authorization in your browser:
  slack: https://auth.base44.io/oauth/...
  notion: https://auth.base44.io/oauth/...

? Open browser to authorize now? › Yes

Opening browser for slack...
✓ slack authorization complete

Opening browser for notion...
✓ notion authorization complete

Summary:
  Synced: googlecalendar
  Added: slack, notion

Pushing Stripe (no OAuth required)

Stripe is provisioned automatically — no browser flow is needed:

Found 2 connectors to push: googlecalendar, stripe
✓ Connectors pushed

Summary:
  ✓ Stripe sandbox provisioned
    Claim your Stripe sandbox: https://dashboard.stripe.com/...
    Connectors dashboard: https://app.base44.com/...
  Synced: googlecalendar

Removing connectors

If you delete a connector file locally and push, it will be removed:

Found 1 connectors to push: googlecalendar
✓ Connectors pushed

Summary:
  Synced: googlecalendar
  Removed: slack

CI/CD Environments

In non-interactive environments (no TTY, such as CI/CD pipelines), the OAuth flow is skipped automatically:

Skipped OAuth in non-interactive mode. Run 'base44 connectors push' locally or open the links above to authorize.

You must run npx base44 connectors push locally to complete authorization for new connectors.

Skipping Authorization

If you choose not to authorize immediately, the connectors remain in a pending state:

? Open browser to authorize now? › No

Authorization skipped. Pending: slack, notion. Run 'base44 connectors push' again to complete.

Run the command again when you’re ready to authorize.

Summary Status Meanings

Status	Meaning
Provisioned	Stripe sandbox was created automatically (no OAuth needed)
Synced	Connector already existed, scopes updated if needed
Added	New connector successfully authorized via OAuth
Removed	Connector was deleted from Base44 (not in local files)
Failed	Authorization timed out, failed, or was skipped

Troubleshooting

Problem	Solution
Authorization timed out	Re-run `npx base44 connectors push` and complete OAuth faster
Authorization failed	Check that you approved all requested permissions
Wrong account connected	Remove the connector file, push to delete it, then add it back and authorize with the correct account
Browser didn’t open	Copy the URL shown in the terminal and open it manually

connectors-create.md - How to create connector configuration files
connectors-pull.md - Pull connectors from Base44 to local files

​base44 connectors push

​Usage

​Options

​Confirmation Prompt

​Projectless Mode

​JSON Output

​What It Does

​OAuth Authorization Flow

​Example Output

​Pushing connectors (no new authorization needed)

​Pushing new connectors (authorization required)

​Pushing Stripe (no OAuth required)

​Removing connectors

​CI/CD Environments

​Skipping Authorization

​Summary Status Meanings

​Troubleshooting

​Related Commands

base44 connectors push

Usage

Options

Confirmation Prompt

Projectless Mode

JSON Output

What It Does

OAuth Authorization Flow

Example Output

Pushing connectors (no new authorization needed)

Pushing new connectors (authorization required)

Pushing Stripe (no OAuth required)

Removing connectors

CI/CD Environments

Skipping Authorization

Summary Status Meanings

Troubleshooting

Related Commands