OpenAPI Import

Instead of transcribing an endpoint's URL, parameters, and authentication by hand, you can import an OpenAPI specification and have the engine pre-fill an API action from a chosen operation.

What it does

When you add an API action to a rule, the OpenAPI import dialog lets you paste or load an API description and pick the operation you want to call. The engine reads the document, lists its operations, and maps the one you select onto the API action form — filling in the method, URL, query and header parameters, request content type and body shape, and the authentication style. You then review and adjust the prefilled values before saving.

Supported documents

The importer accepts both JSON and YAML, and understands Swagger 2.0 as well as OpenAPI 3.x. It reads the document's server and base path to derive the request URL, and it surfaces any parse warnings so you know when part of a document could not be interpreted. Authentication declared in the spec is recognized too: the form's authentication mode is set to none, API key, or OAuth2 to match the operation, with OAuth2 details prefilled where present.

The import flow

1. Add an API action to a rule and open the OpenAPI import dialog.
2. Provide the OpenAPI or Swagger document (JSON or YAML).
3. Pick the operation you want this action to call.
4. The dialog hands back a prefilled API action — method, URL, parameters, content type, and authentication.
5. Fine-tune any values, wire inputs to context, and save the action.

After import

An imported action is an ordinary API action — nothing about it is locked to the source document. You can edit every field, bind request values to context variables, map the response into outputs, and choose how failures are handled, exactly as you would for an action you built from scratch.