The Actions resource in Copilotz allows users to define specific operations that can be performed by agents during workflows. These actions represent tasks such as making API requests, triggering a function, or interacting with external services, and they follow the OpenAPI specification for flexibility and consistency.
An Action defines what tasks or operations an agent can execute. These actions can either be natively handled by Copilotz or can point to a custom module URL for more advanced functionality.
openapi3-yaml
but can be extended for other formats.native:request
, Copilotz will handle the request natively.A typical Action would look like this:
openapi3-yaml
. This defines how the action is structured and interpreted.native:request
can be used.Native Actions: If the moduleUrl
is set to native:request
, Copilotz will handle the action internally, using the provided OpenAPI specification to make an HTTP request.
Custom Actions: If the moduleUrl
points to an external module, that URL will be invoked, and it will handle the operation. The user must provide their own implementation for this action. As Copilotz uses Deno runtime, moduleUrl
can be any url containing a .js or .ts file, and it’ll be dynamically loaded for being executed as an action when called by the agent.
The Actions resource in Copilotz allows users to define specific operations that can be performed by agents during workflows. These actions represent tasks such as making API requests, triggering a function, or interacting with external services, and they follow the OpenAPI specification for flexibility and consistency.
An Action defines what tasks or operations an agent can execute. These actions can either be natively handled by Copilotz or can point to a custom module URL for more advanced functionality.
openapi3-yaml
but can be extended for other formats.native:request
, Copilotz will handle the request natively.A typical Action would look like this:
openapi3-yaml
. This defines how the action is structured and interpreted.native:request
can be used.Native Actions: If the moduleUrl
is set to native:request
, Copilotz will handle the action internally, using the provided OpenAPI specification to make an HTTP request.
Custom Actions: If the moduleUrl
points to an external module, that URL will be invoked, and it will handle the operation. The user must provide their own implementation for this action. As Copilotz uses Deno runtime, moduleUrl
can be any url containing a .js or .ts file, and it’ll be dynamically loaded for being executed as an action when called by the agent.