Integrator Workspace News (07/2025)

| Integrator Workspace | July

Connector upload: OpenAPI schema validation

You can now upload your connector with OpenAPI schema-based validation to help you improve reliability and ensure your API aligns with OpenAPI standards.

Key features:

  • • OpenAPI schema selection: Select the OpenAPI schema version (default is 3.0) to validate your connector file. This ensures compatibility with the version your API definition is based on.
  • • Automatic validation: When you upload a connector file, it is automatically validated against the selected OpenAPI schema version. Validation runs immediately and provides clear, detailed error messages if any issues are found.
  • • Non-blocking validation: Validation errors do not prevent the upload. Instead, they serve as important guidance to help ensure your connector integrates smoothly into flows. We recommend addressing validation issues to avoid potential runtime problems.

This new validation feature helps you ensure that your connector aligns with OpenAPI standards. It enables you to identify issues early on and supports smoother integration into flows.

Integrator Workspace > Assets > Upload asset
Integrator Workspace > Assets > Edit connector

SFTP: Upload, download, list and delete files

You can now use our new SEEBURGER SFTP connector to upload, download, list and delete files. 

Integrator Workspace > Projects > Flow > Assets > SEEBURGER SFTP connector

New connectors

The asset catalog now includes several new connectors:

    1. 1. ADP
    2. 2. Coupa
    3. 3. Adobe Commerce
    4. 4. Telegram
    5. 5. DeepL
    6. 6. Workday
    7. 7. Slack
    8. 8. Zendesk
    9. 9. Channel Engine
    10. 10. OpenProject
    11. 11. Mailchimp
    12. 12. SEEBURGER Demo API

Integrator Workspace > Assets

Authentication types independent from OpenAPI specification 

Previously, we showed only those authentication types which were listed in the OpenAPI specification. We recognized that this behavior might block you from configuring a flow because of incorrect specifications. Therefore, we have enabled all authentication types that are available in IWS, not only those defined in the OpenAPI specification.

This way, you are no longer blocked by an incorrect OpenAPI specification, and the interface now clearly indicates whether an authentication type is defined by the specification or not.