---
title: 'Deploy workflows with the Novu CLI'
sidebarTitle: 'CLI'
description: 'Use the Novu CLI sync command to push Framework workflows to Novu Cloud, connect a bridge endpoint, and understand sync output messages.'
---
The Novu CLI provides a mechanism for you to synchronize your workflows into Novu Cloud so that non-technical Novu users can control the workflow and Step-level controls and enable your workflows to be triggered via Novu API.
```bash
npx novu@latest sync \
--bridge-url \
--secret-key \
--api-url https://api.novu.co
```
```bash
npx novu@latest sync \
--bridge-url \
--secret-key \
--api-url https://eu.api.novu.co
```
- If your application api server is running at URL **https://api.domain.com** and **/api/novu** endpoint is serving Novu workflows created using Novu Framework, then ``in above command will be `https://api.domain.com/api/novu`
- If your application is running on your local machine during local development (`npx novu dev`), the tunnel URL can be used as ``. The tunnel URL follows the format of `https://.novu.sh/api/novu`, and example is `https://041e553c-0dbf-47e0-8ffa-c4536f390145.novu.sh/api/novu`. In this example `041e553c-0dbf-47e0-8ffa-c4536f390145` is the unique tunnel identifier which is generated for each Novu user when starting a tunnel via `npx novu@latest dev`. The tunnel identifier is persisted to your local machine to guarantee the same tunnel URL each time you invoke `npx novu@latest dev`.
## Understanding sync output
A successful sync prints the number of workflows and steps that were discovered from your bridge endpoint, for example:
```json
{"status":"ok","sdkVersion":"2.10.0","frameworkVersion":"2024-06-26","discovered":{"workflows":14,"steps":30}}
```
You may also see the following message printed alongside a successful sync:
```
Could not discover agents for bridge URL sync (bridge may not expose agents yet).
```
This is an informational notice, not an error. It only indicates that your bridge does not expose any [Agents](/agents/get-started/what-is-aci) at the sync endpoint. If you are only syncing workflows, you can safely ignore this message - your workflows and steps have still been synced.
## View your synced bridge URL
After a successful sync, the bridge URL is stored on the environment you synced to. In the Novu Dashboard, open that environment and click the glowing status orb in the top-right navigation bar to view or update the **Bridge Endpoint URL**.

For more detail, see [View your bridge URL](/framework/endpoint#view-your-bridge-url).
## Using vercel preview url
In free tier, vercel preview urls for non production deployments are not publicly accessible. You will need to enable [Protection Bypass for Automation](https://vercel.com/docs/security/deployment-protection/methods-to-bypass-deployment-protection/protection-bypass-automation#protection-bypass-for-automation) from settings to make the preview url publicly accessible. Use vercel generated secret key in query params with bridge url to make the bridge url accessible to novu.
Example: `https://my-app-preview-url.vercel.app/api/novu?x-vercel-protection-bypass=BYPASS_SECRET_KEY`
## Sync failed while calling the bridge
`novu sync` always returns `400`. The body is only a `message`. It does not include the `code` a step failure includes.
A URL rejected before sync connects looks like `bridgeUrl: Invalid URL format.` or `bridgeUrl: Requests to private or reserved IP addresses are not allowed (resolved: ).` A URL rejected while sync is calling the bridge keeps this message, with no reason code:
```
The provided bridge URL is blocked by the outbound SSRF policy.
```
A preview deployment that is down or not in DNS yet is one cause of that sentence. Sync retries that call once, after 1 second. [Bridge request errors](/framework/errors) has the message for each failure and what to run to tell them apart.