April 8

Release Notes 04/08/2025

Connectors

New connectors

• Mailgun API (General Availability): Integrates with Mailgun’s email delivery service and allows you to send emails with custom recipients, subjects and content, including attachments. It helps automate notifications, transactional emails and marketing messages within your pipelines. Learn more in the documentation.

• Gupy Public API (General Availability): Integrates with Gupy’s public API and provides access to data related to job openings, candidates, and applications. It helps automate HR workflows by allowing pipelines to interact with HR-related data. Learn more in the documentation.

• HubSpot - Sales and CMS (General Availability): Now available as two separate connectors: HubSpot Sales and HubSpot CMS. These connectors integrate with HubSpot’s Sales and CMS tools and allow you to create, update, and retrieve deals, contacts, pages, and other key resources. Learn more in the documentation.

• Protheus - Billing and Inventory of Cost (General Availability): Now available as two separate connectors: Protheus Billing and Protheus Inventory of Cost. These connectors integrate with the Protheus ERP system to access billing and cost inventory data to optimize financial and inventory processes. Learn more in the documentation.

Updates to existing connectors

• Caffeine Cache (General Availability): The Caffeine Cache connector has been refined to improve its usability. The documentation has also been updated to reflect these improvements. Check it out in the documentation.

• REST V2 (General Availability): You can now configure redirect behavior for 302 responses in the REST V2 connector. Enable or disable redirection as needed to validate the response before it's followed. This setting is in Advanced Settings and is set to true (enabled) by default. Learn more in the documentation.

Triggers

• OAuth2 on Email Trigger V2: Email Trigger V2 now supports the OAuth 2 account type in addition to the Basic account. Find out more in the documentation.

Help Hub (General Availability)

You can now access the Help Hub from the question mark icon in the left-side menu on Canvas. It provides quick access to key resources, including the Release Notes, Documentation Portal, Digibee Academy, and in-app tutorials and checklists.

At the top of the Help Hub, you will also find buttons to send feedback, view available keyboard shortcuts for Canvas, and start a conversation with our Support team. For more information, read the documentation.

Connector Latency (General Availability)

Connector Latency is a new chart available on the Pipeline Metrics page in Monitor. It displays the latency of each connector, highlighting the top six with the highest latency over a selected time range. This visualization helps you quickly identify performance trends and detect changes in connector behavior more efficiently.

Read the documentation to learn more.

Organization reports (General Availability)

Now you can generate organization reports to view detailed information about all pipelines — both deployed and undeployed —as well as every deployment within a realm. These reports are useful for auditing, managing organizational realms, and analyzing consumption by realm.

Read the documentation to learn more.

ZTNA Groups (General Availability)

Now you can create Edge Routers groups for your ZTNA connections, according to your company needs. This allows more flexible and organized connection management. Check out the updates in the following documentation and learn how to create your groups:

• How to add new ZTNA connections (Edge Routers)

• How to add new routes (Network mappings)

• How to edit routes (Network mappings)

• ZTNA Inverse Flow

VPN Metrics now available via Digibee API Metrics (General Availability)

Now you can monitor your VPN performance through Digibee API Metrics using Datadog or Prometheus. This enables proactive detection and faster response to VPN-related issues, improving overall visibility and reliability. Check out the documentation:

• How to set up Digibee API metrics with Datadog

• How to set up Digibee API metrics with Prometheus

Help Center sunset

Previously, all troubleshooting articles were available in the Help Center. These resources have now been moved to the Troubleshooting section of our Documentation Portal, where they are better organized and regularly updated to ensure accuracy and clarity.

Please note that the Help Center will be deactivated on May 5, 2025. We recommend updating any saved links to reflect this change.

Improvements and bug fixes

Improvements

• Data-streaming-manager (New role): We’ve created a new role for the Log Streaming feature. This role allows the user to create, edit and delete data stream configurations. See more in the Roles documentation.

Bug fixes

• Blank screen when interacting with the Choice connector: We fixed the bug that caused a blank screen when interacting with the Choice connector. This occurred when a condition name had fewer than 3 characters. A validation has now been added to prevent users from creating conditions with names shorter than 3 characters.

• Unable to save pipeline after editing API Trigger routes: We fixed the bug that prevented pipelines from being saved after changes were made to the API Trigger’s route configuration.

• Loops not visible in Inspect Mode on Capsules: We fixed the bug that prevented loops from being displayed in Inspect Mode when inspecting Capsules. They now appear as expected.

• JOLT – Math function fixes: We fixed issues in JOLT transformations that affected operations like subtraction, min/max, and absolute value when handling numbers with decimals or zeros.

• loopIndex not displayed correctly when using Parallel Execution inside Do While: We fixed a bug that caused the loopIndex value to disappear after the first iteration when the Parallel Execution connector was used inside a Do While. The value is now displayed correctly in all iterations.

• Inspect Mode showed incorrect path in Choice with For Each: We fixed an issue in Inspect Mode where the Choice connector always displayed the path containing the For Each, regardless of the actual execution flow. The path now correctly reflects the route taken during execution.