Limitations when calling skills from a workflow

If you intend to build a workflow that calls skills, review the following limitations.

General limitations

  • Calling skills with document outputs is not supported.
  • Calling composite skills is not supported.
  • Calling skills that have an integer type output must use values that fit into an int32.

Calling skills from a workflow (particularly custom skills) is based on OpenAPI constructs. Keep in mind the following constraints for OpenAPI constructs.

Automatically renamed OpenAPI constructs

  • Schema property names that are not valid will be modified into a valid property name. Invalid JavaScript identifiers will be prefixed with uab_ and invalid characters in the JavaScript identifier will be replaced with _. For example, break is a reserved JavaScript word, so it will be automatically changed to uab_break. For example, created-at contains the invalid JavaScript identifier character -, so it will be automatically changed to uab_created_at.
  • Schema property names that are reserved Java words or reserved workflow words will be prefixed with uab_. For example, boolean is a reserved Java word, so it will be automatically changed to uab_boolean.
  • If the OpenAPI definition contains object names longer than 64 characters, the object names are shortened.

Unsupported OpenAPI constructs

  • Properties allOf, oneOf, anyOf, and not are not supported.
  • Type integer with format int64 is not supported.
  • $ref properties that reference properties in schema objects are not supported unless the type of the referenced property is a primitive data type.
  • $ref properties that reference elements in other locations of the same OpenAPI definition are not supported, except by the following references:
    • #/components/schemas/name for schemas
    • #/components/parameters/name for parameters
    • #/components/responses/name for responses
    • #/components/requestBodies/name for request bodies
    • #/components/securitySchemes/name for security schemes
  • Paths that contain a semicolon are not supported.

OpenAPI constructs that are ignored or not honored

  • For the HTTP methods GET, HEAD, OPTIONS, and DELETE, any request body is ignored.
  • Property default is ignored for all types.
  • Properties maxLength and minLength for type string are ignored for parameters.
  • Property multipleOf for the types integer and decimal is ignored.
  • Property allowEmptyValue is ignored.
  • Schema properties maxProperties, minProperties, and additionalProperties are ignored.
  • Schema array properties maxItems and minItems are ignored.
  • Formats email, password and hostname for type string are ignored.

Parent topic:

→ Reusing automations and skills