Grooper Help - Version 25.0
25.0.0024 2,166

Web Service

Resource Reference Grooper.GPT

Exposes a web service as a resource that an AI Assistant can use for dynamic data retrieval, integration, or automation.

Remarks

The Web Service resource enables the AI Assistant to connect with external web services, allowing it to send requests and receive responses from online APIs. This expands the assistant's capabilities beyond the Grooper environment, making it possible to interact with third-party systems, retrieve live data, or trigger remote actions as part of a conversation or workflow.

By configuring a Web Service resource, you empower the assistant to access real-time information, automate business processes, and integrate with a wide range of external platforms and services.

Usage and Configuration

To configure a Web Service resource:

  1. Provide a Resource File containing a RAML definition that describes the web service's endpoints, methods, and parameters.
  2. Set any required HTTP headers, such as authentication tokens or content types, to be included with each request.
  3. Choose the appropriate authentication method (e.g., API key, OAuth, Basic Auth) required by the web service.
  4. Specify a timeout value to control how long the assistant waits for a response.
  5. Optionally, define a CSS selector to identify the root element when importing HTML content from the service.

Once configured, the AI Assistant will use the RAML definition to understand available endpoints and how to interact with the service. The assistant can then invoke web service calls as needed to answer questions, retrieve data, or automate actions.

Example Use Cases

  • Retrieve real-time weather information by connecting to a weather API.
  • Submit data to a remote system, such as creating a support ticket or updating a CRM record.
  • Integrate with business applications to fetch inventory levels, order status, or other operational data.
  • Automate workflows by invoking endpoints on workflow or automation platforms.

Best Practices

  • Ensure the RAML definition accurately describes the web service and is kept up to date with any API changes.
  • Test the configuration with sample requests to verify connectivity, authentication, and data retrieval.
  • Use descriptive titles and documentation in the RAML file to help users and the assistant understand the service's purpose.

Diagnostics

If the RAML definition is missing or does not include a title property, a validation error will be logged.
Additional diagnostic messages may be generated if requests fail due to authentication errors, timeouts, or invalid configuration.

Properties

NameTypeDescription

See Also

Notification