# October 30

## New features

### **New trigger: MCP Server**

The **MCP Server Trigger** allows pipelines to receive and process requests from **Model Context Protocol (MCP) clients**, enabling advanced integrations with AI tools and external systems. It supports multiple tools and provides a clear visual representation in the pipeline, making it easier to manage complex and dynamic interactions.

Learn more in the [**MCP Server Trigger documentation**](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/triggers/web-protocols/mcp-server).

<figure><img src="https://4091659634-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE9x0KHkAmxzJGlYPs9aE%2Fuploads%2FPXJmSR8UWrntti6cr0vv%2Fvisual-representation-mcp-server.png?alt=media&#x26;token=8a3567e1-6207-4b16-9a56-db868ebc48b2" alt=""><figcaption></figcaption></figure>

## Connectors

### **New connector: Vector DB**

The **Vector DB Connector** performs the **data ingestion process** that transforms information into **vector embeddings** and stores them in a **vector database**. These embeddings capture the meaning of the content, allowing AI models to later perform semantic retrieval and contextual understanding based on similarity rather than exact matches.

Explore how it works in the [**Vector DB Connector documentation**](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/connectors/ai-tools/vector-db).

### **New connector: Magento (Beta)**

The **Magento Connector** integrates Digibee pipelines with **Adobe Magento** via REST API. It lets you query, create, update, and delete records related to products, orders, customers, and carts, streamlining e-commerce operations and keeping data synchronized across systems.

Check the [**Magento Connector documentation**](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/connectors/industry-solutions/magento) for configuration details.

### **Update: Agent Connector**

The **LLM Connector** is now the **Agent Connector**, reflecting its broader functionality. It now includes two new tabs, **Embedding Models** and **Vector Store**, which let you retrieve content from Vector Stores for Retrieval-Augmented Generation (RAG), long-term memory, semantic search, and many other use cases.

See what’s new in the [**Agent Connector documentation**](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/connectors/ai-tools/llm).

### **Update: Oracle NetSuite**

We’ve enabled query parameters for the `GET` method on the **Oracle NetSuite** connector. Previously, only `POST` methods supported this option.

Learn more about supported methods in the [**Oracle NetSuite Connector documentation**](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/connectors/industry-solutions/oracle-netsuite).

### **Update: XML to JSON and Stream XML File Reader**

The new **Escape Special Characters** parameter has been added to the **XML to JSON** and **Stream XML File Reader** connectors. When enabled, it automatically escapes reserved XML characters (such as `&`, `<`, and `>`) to prevent conversion failures and ensure correct data parsing during transformation.

Find details in the [**XML to JSON Transformer**](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/connectors/tools/xml-to-json-transformer) and [**Stream XML File Reader**](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/connectors/files/stream-xml-file-reader) documentation.

## Platform improvements

### **“Messages” tab in the Flow left-side panel**

The **Messages** tab has been moved to the **Flow** left-side panel alongside the **Test Cases** feature, making it easier to view messages and test different integration scenarios.

Learn more in the [**Execution Panel documentation**](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/development-cycle/build-overview/canvas/execution-panel).

<figure><img src="https://4091659634-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE9x0KHkAmxzJGlYPs9aE%2Fuploads%2FXUzoh99eFI77FxfyLuTJ%2Fmessages.gif?alt=media&#x26;token=94dec5da-2d81-4e81-aadf-1fadd6e74e1c" alt=""><figcaption></figcaption></figure>

### **New “Request Queue Time” chart added to Pipeline Metrics**

The new **Request Queue Time** chart provides insights into the average time requests spend in the queue (RabbitMQ) before being processed by the pipeline, allowing for better monitoring of queue latency.

Learn more about these and other metrics in the [**Pipeline Metrics documentation**](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/development-cycle/dashboards/pipeline-metrics).

<figure><img src="https://4091659634-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE9x0KHkAmxzJGlYPs9aE%2Fuploads%2F0G5YVVI7wdB8RlSUICb7%2Fimage.png?alt=media&#x26;token=d214166e-be1f-4fea-9f48-ec7c4ac185ed" alt=""><figcaption></figcaption></figure>

### **Improved management for Accounts and Globals**

You now have new options to better manage accounts and globals:

* **Project restrictions**: When creating a new account or global, you can restrict it to a specific project. Existing ones remain available to all projects by default, but you can edit their settings if needed.
* **Deprecation**: Accounts and globals can now be marked as **deprecated**, preventing their use in new pipelines. This does not affect deployed pipelines unless they are redeployed.

Learn more in the [**Accounts**](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/platform-administration/settings/accounts) and [**Globals**](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/platform-administration/settings/globals) documentation.

### **Interface design and naming updates**

We’ve refreshed several areas of the interface for improved consistency and readability:

* **Platform icons** have been updated with a modern and unified visual style.
* The **Completed Executions** tab on the Monitor page has been renamed to **Executions** to better reflect its purpose. All previous data and features remain unchanged and fully available.

### **Project management updates**

Managing projects and pipelines is now easier and safer.

* Pipelines are automatically linked to the project where they are created. Previously, you could create a pipeline in any project and associate it later. Now, you must select or create the project before creating a pipeline.
* A confirmation dialog now warns that archived pipelines in a project can’t be recovered, and the error message displayed when archiving a project with active pipelines has been improved for clarity.
* The Run and Monitor pages now apply project-level permissions, so users only see **deployments**, **metrics**, and **logs** from projects they can access. This improves access control and keeps data more secure across the Platform.

## Digibee Academy

### **New webinar available: ETL in Practice – Performance, Scalability & Efficiency**

The new **ETL in Practice** webinar is now available on Digibee Academy! Learn how to build fast, resilient, and scalable pipelines that deliver consistent results.

You’ll explore:

* How to apply **selective scalability** to optimize resources
* **Parallel processing** strategies to handle millions of records
* Techniques for **resilience** and seamlessly reprocessing failures
* **Efficiency** best practices for flexible and organized pipelines

**Level:** Intermediate

Watch now on the [**Digibee Academy**](https://digibee.academy/webinars/webinar-etl-na-pratica-performance-escalabilidade-e-eficiencia/) and take your pipelines to the next level!

## Documentation

We’ve updated the following documentation:

* [HTTP File Trigger (Upload and Download)](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/triggers/web-protocols/http-file)
* [Accounts](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/platform-administration/settings/accounts)
* [How to create a pipeline](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/development-cycle/build-overview/pipelines/how-to-create-a-pipeline)
* [Digibee Customer Support](https://app.gitbook.com/s/boT4qPJIk6PZotrxlJWL/help-and-faq/support)

## Bug fixes

* **Incorrect `null` values in Pipeline Keys:** We fixed a bug that caused the Pipeline Keys column in Pipeline Logs (Monitor) to show `null` instead of the actual key values.
* **Google BigQuery Standard SQL not working:** We fixed a bug that prevented queries using Google BigQuery Standard SQL from running correctly.