fix: add deploy agents and connect components

content/docs/agents/add-connect-components.mdx

@@ -3,3 +3,111 @@
 pageTitle: 'Novu Agents Add Connect Components'
 description: 'Add Connect UI components so users can link accounts and channels to your agent.'
 ---
+
+Novu provides pre-built UI components for chat platforms like Slack and Microsoft Teams. Add these components so users can install the Slack or Microsoft Teams app in their workspace and connect it to your agent.
+
+## Slack connect button
+
+`SlackConnectButton` is a pre-built UI component in the `@novu/react` SDK that connects an agent to a Slack workspace. Check out the example below.
+
+```tsx
+import { SlackConnectButton } from '@novu/react';
+
+const SlackConnectButtonComponent = () => {
+  const subscriberId = 'subscriber-id';
+  const integrationIdentifier = 'integration-identifier';
+  const agent = {
+    identifier: 'agent-identifier',
+    name: 'agent-name',
+  };
+
+  const handleSlackOAuthSuccess = () => {
+    // Handle success
+  };
+
+  return (
+    <SlackConnectButton
+      integrationIdentifier={integrationIdentifier}
+      connectionIdentifier={`${subscriberId}:${integrationIdentifier}:${agent.identifier}`}
+      connectionMode="subscriber"
+      connectLabel={`Install ${agent.name} ↗`}
+      connectedLabel="Connected to Slack"
+      onConnectSuccess={handleSlackOAuthSuccess}
+      onConnectError={(error: unknown) => {
+        console.error(error);
+      }}
+    />
+  );
+};
+
+export default SlackConnectButtonComponent;
+```
+
+### API reference
+
+`SlackConnectButton` accepts the following props to customize the UI and behavior:
+
+<TypeTable name="SlackConnectButtonProps" type={{
+  "integrationIdentifier": {
+    "description": "",
+    "type": "string"
+  },
+  "connectionIdentifier": {
+    "description": "",
+    "type": "string"
+  },
+  "subscriberId": {
+    "description": "",
+    "type": "string"
+  },
+  "context": {
+    "description": "",
+    "type": "Partial<Record<string, ContextValue>>"
+  },
+  "scope": {
+    "description": "",
+    "type": "string[]"
+  },
+  "connectionMode": {
+    "description": "",
+    "type": "ConnectionMode"
+  },
+  "onConnectSuccess": {
+    "description": "",
+    "type": "((connectionIdentifier: string) => void)"
+  },
+  "onConnectError": {
+    "description": "",
+    "type": "((error: unknown) => void)"
+  },
+  "onDisconnectSuccess": {
+    "description": "",
+    "type": "(() => void)"
+  },
+  "onDisconnectError": {
+    "description": "",
+    "type": "((error: unknown) => void)"
+  },
+  "connectLabel": {
+    "description": "",
+    "type": "string"
+  },
+  "connectedLabel": {
+    "description": "",
+    "type": "string"
+  },
+  "appearance": {
+    "description": "",
+    "type": "ReactInboxAppearance | ReactSubscriptionAppearance | ReactAllAppearance"
+  },
+  "container": {
+    "description": "",
+    "type": "string | Node | null"
+  }
+}} />
+
+## Microsoft Teams connect button
+
+<Callout type="info">
+  We are working on adding a Microsoft Teams connect button to the `@novu/react` SDK. Reach out to us at support@novu.co to get access to a pre-release version.
+</Callout>

content/docs/agents/add-connect-components.model.mdx

@@ -0,0 +1,58 @@
+---
+title: "Add Connect Components"
+pageTitle: 'Novu Agents Add Connect Components'
+description: 'Add Connect UI components so users can link accounts and channels to your agent.'
+---
+
+Novu provides pre-built UI components for chat platforms like Slack and Microsoft Teams. Add these components so users can install the Slack or Microsoft Teams app in their workspace and connect it to your agent.
+
+## Slack connect button
+
+`SlackConnectButton` is a pre-built UI component in the `@novu/react` SDK that connects an agent to a Slack workspace. Check out the example below.
+
+```tsx
+import { SlackConnectButton } from '@novu/react';
+
+const SlackConnectButtonComponent = () => {
+  const subscriberId = 'subscriber-id';
+  const integrationIdentifier = 'integration-identifier';
+  const agent = {
+    identifier: 'agent-identifier',
+    name: 'agent-name',
+  };
+
+  const handleSlackOAuthSuccess = () => {
+    // Handle success
+  };
+
+  return (
+    <SlackConnectButton
+      integrationIdentifier={integrationIdentifier}
+      connectionIdentifier={`${subscriberId}:${integrationIdentifier}:${agent.identifier}`}
+      connectionMode="subscriber"
+      connectLabel={`Install ${agent.name} ↗`}
+      connectedLabel="Connected to Slack"
+      onConnectSuccess={handleSlackOAuthSuccess}
+      onConnectError={(error: unknown) => {
+        console.error(error);
+      }}
+    />
+  );
+};
+
+export default SlackConnectButtonComponent;
+```
+
+### API reference
+
+`SlackConnectButton` accepts the following props to customize the UI and behavior:
+
+---type-table---
+../platform/sdks/types/react-types.ts#SlackConnectButtonProps
+---end---
+
+## Microsoft Teams connect button
+
+<Callout type="info">
+  We are working on adding a Microsoft Teams connect button to the `@novu/react` SDK. Reach out to us at support@novu.co to get access to a pre-release version.
+</Callout>

content/docs/agents/deploy-your-agent.mdx

@@ -1,5 +1,110 @@
 ---
-title: "Deploy Your Agent"
-pageTitle: 'Novu Agents Deployment'
-description: 'Deploy your Novu Agent to production environments.'
+title: "Agent Deployment"
+pageTitle: 'Agent Deployment'
+description: 'Learn how to run a conversational agent on your local machine, test it in a development environment, and deploy it to production.'
 ---
+
+Agents built with Novu can run on your local machine. Deploy them to development and production environments when you are ready.
+
+## Agent on your local machine
+
+By default, the agent runs on your local machine. To run the agent locally:
+
+* Scaffold your agent with `npx novu init -t agent`.
+* Add valid `NOVU_SECRET_KEY` and `NOVU_API_URL` values to your `.env` file.
+* Run the scaffolded project on your local machine.
+* Set the bridge option to `Local` in the agent overview section.
+
+When you complete these steps, run the agent using the Novu CLI command below.
+
+```bash
+npx novu@latest dev --port <bridge_application_port> --no-studio
+```
+
+* **bridge_application_port** - Port where your scaffolded project runs. Defaults to 4000.
+* **no-studio** - Disables Studio.
+
+After you run the command, a tunnel starts on your machine. It forwards requests to your scaffolded project on `bridge_application_port`.
+
+Novu sets the bridge URL automatically to `tunnel-url/api/novu`.
+
+The agent listens for new messages and responds while running locally.
+
+## Agent in development
+
+After you test the agent locally, deploy it to a development environment. A scaffolded app from `npx novu init -t agent` uses Next.js and exposes a `/api/novu` endpoint for communicating with Novu. Deploy the app to your preferred hosting provider, then copy the deployed URL.
+
+* Add valid `NOVU_SECRET_KEY` and `NOVU_API_URL` values in the environment variables section of your hosting provider.
+* Toggle the bridge option to `Development` in the agent overview section.
+* For a deployed app at `https://dev.my-agent-app.com`, use `https://dev.my-agent-app.com/api/novu` as the bridge URL in the agent overview section.
+
+## Agent in production
+
+Before you use an agent in production, publish the agent from the development environment to the production environment. Use the *Publish changes* option on the dashboard.
+
+After you publish:
+
+* Publishing sends the agent to production with the same name, identifier, and description.
+* The agent stays inactive until you activate it from the agent overview section.
+* Configure and connect every provider again in the production environment.
+* Deploy the agent bridge application to the production environment.
+* Add valid `NOVU_SECRET_KEY` and `NOVU_API_URL` values in the environment variables section of your hosting provider.
+
+### Deploying to production
+
+After you publish the agent and complete the above steps, deploy the agent bridge application to the production environment.
+
+#### Using Novu CLI
+
+```bash
+npx novu@latest sync --bridge-url <bridge_url> --secret-key <NOVU_SECRET_KEY> --api-url <NOVU_API_URL>
+```
+
+For example, with `https://prod.my-agent-app.com` as the bridge app URL, use `https://prod.my-agent-app.com/api/novu` as the bridge URL.
+
+In the command above:
+
+* `<bridge_url>`: URL of your deployed agent bridge application.
+* `<NOVU_SECRET_KEY>`: secret key for your Novu account.
+* `<NOVU_API_URL>`: API URL for your Novu account.
+
+After you run the command, the agent overview section shows the updated production bridge URL.
+
+#### Using GitHub Actions
+
+You can use our built-in GitHub Action to deploy your agent to the production environment.-->
+
+```yaml
+name: Deploy agent to Novu Cloud
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - main
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      # https://github.com/novuhq/actions-novu-sync
+      - name: Deploy agent to Novu Cloud
+        uses: novuhq/actions-novu-sync@v2
+        with:
+          # The secret key used to authenticate with Novu Cloud
+          # To get the secret key, go to https://web.novu.co/api-keys.
+          # Required.
+          secret-key: ${{ secrets.NOVU_SECRET_KEY }}
+
+          # The publicly available endpoint hosting the bridge application
+          # where notification entities (e.g. workflows, topics) are defined.
+          # Required.
+          bridge-url: ${{ secrets.NOVU_BRIDGE_URL }}
+
+          # The Novu Cloud API URL to sync with.
+          # Optional.
+          # Defaults to https://api.novu.co
+          api-url: https://api.novu.co
+```
+
+<Callout type="warn">Local tunnel bridge URLs cannot be activated on production environments (returns 403 Forbidden) to prevent accidental routing of production traffic to a local machine.</Callout>

content/docs/platform/sdks/javascript/index.mdx

@@ -137,7 +137,7 @@ Fetches a list of notifications based on provided filters.
 <TypeTable name="NotificationFilter" type={{
   "tags": {
     "description": "",
-    "type": "string[]"
+    "type": "TagsFilter"
   },
   "read": {
     "description": "",
@@ -225,7 +225,7 @@ Fetches the count of notifications based on filters.
 <TypeTable name="NotificationFilter" type={{
   "tags": {
     "description": "",
-    "type": "string[]"
+    "type": "TagsFilter"
   },
   "read": {
     "description": "",

content/docs/platform/sdks/react/hooks/use-notifications.mdx

@@ -13,7 +13,7 @@
 <TypeTable name="UseNotificationsProps" type={{
   "tags": {
     "description": "",
-    "type": "string[]"
+    "type": "TagsFilter"
   },
   "data": {
     "description": "",
@@ -51,6 +51,10 @@
     "description": "",
     "type": "number"
   },
+  "realtime": {
+    "description": "When `false`, disables the WebSocket subscription that auto-injects\nnewly received notifications into the list. Built-in mutations like\n`readAll`, `seenAll`, `archiveAll`, and `archiveAllRead` continue to\nupdate local state. Use this when you want to drive new-notification updates yourself (e.g.\nvia your own `novu.on('notifications.notification_received', ...)`\nhandler combined with `refetch()`).\n\nWhen set, this prop takes precedence over the `realtime` config on\n`<NovuProvider />`. When omitted, the provider value (default `true`) is used.",
+    "type": "boolean"
+  },
   "onSuccess": {
     "description": "",
     "type": "((data: Notification[]) => void)"