Platform Updates - July 12, 2026
π What we've shipped
- Development: all tools are now enabled by default in
DEVELOPMENTenvironments (you can still disable specific ones), removing the manual step of enabling each one.
DEVELOPMENT environments (you can still disable specific ones), removing the manual step of enabling each one.Your dashboard home now shows your active production connections against your plan's allowance, so your usage matches what you're invoiced for. A tooltip breaks the number down per environment.
The interaction logs viewer in your dashboard now has a "Related" tab that groups repeated sends of the same action, such as retries, making it easier to trace and debug related API calls.
You can now request new integrations and add-ons directly from the Tools page in your Kombo dashboard, so you can tell us what you need next without leaving the dashboard.
The Connect SDK (@kombo-api/connect 1.3.0) now accepts a container option, so you can mount the connection modal inside a specific element on your page instead of the document body. This helps when you launch Connect from inside one of your own modals.
We've overhauled the Audit Logs page in the dashboard. It now uses server-side pagination and adds filters for event type, actor, and date range, making it far easier to track activity.
The BambooHR integration now uses OAuth 2.0 for a more secure, modern authentication method, across both the HRIS and ATS APIs. Existing connections continue to work, with a migration path from the old API-key auth.
Updating partner credentials in the developer dashboard now requires a confirmation checkbox, preventing accidents.
The developer dashboard now supports a full dark mode. Pick Light, Dark, or System from the user menu.
You can now edit automatic mapping rules, scope them to specific connectors, and set explicit matching criteria like key vs. label and case sensitivity. The result is finer-grained control over how data lands in your custom fields.
Enable Static IPs for new integrations directly from the dashboard. No support ticket needed when an upstream system requires IP allowlisting. [Read the guide]
From May 19, 2026, integration setup errors like INTEGRATION.SETUP_INCOMPLETE will return HTTP 409 Conflict instead of 503 Service Unavailable. The error.code in the response body is unchanged, so any logic that branches on it will keep working. If you branch on HTTP status, update that logic before the cutover. [Updated error handling docs]
create-employee form, the dropdown for selecting employees (like a manager) has been improved, showing full names and hiding redundant IDs for a cleaner experience.create-employee action, which has been superseded by the more powerful form-based version, is now hidden in the dashboard's coverage grid to reduce confusion.POST /integrations/{integration_id}/setup-link, allowing you to programmatically generate links to the Setup Flow for your customers' existing integrations. This is useful for guiding users to configure settings like custom fields after the initial connection.end_user_* fields in the embedded connection flow to address common questions.