GraphQL Changelog – March

The March changelog introduces significant enhancements to LLM provider management through new specialized queries and mutations, alongside the addition of web scraping capabilities to AI behaviors. Key structural updates include the implementation of deletedAt fields for better deletion tracking across various objects and a critical type change from Int to Float for AI usage and credit fields. These updates expand metadata tracking while requiring minor adjustments to existing integrations to ensure data type precision.

New:

• A new query activeLlmProvider was added to fetch details of the currently active LLM provider for a given resource.
• A new query llmProvidersByOrganization was added to retrieve LLM providers by organization.
• A new query providerDependencies was added to get information about provider dependencies.
• The AiBehaviorCapabilityType enum received a new value web_scraping.
• Fields phase, pipe, table, and tableId were added to AiBehaviorMetadata for expanded metadata tracking.
• A field dependentInterfaces was added to FieldDependency.
• Newly added fields id to both FlowAiAgent and FlowAutomation for unique identification.
• Several object types received a new field deletedAt for tracking deletions:
  • ConnectedTable
  • InternalPipe
  • Phase
  • PhaseFlow
  • Pipe
  • Table
  • Repo interface
• New mutations for managing LLM providers:
  • createLlmProvider
  • deleteLlmProvider
  • resetLlmProviderOwner
  • setActiveLlmProvider
  • updateLlmProvider
• A new mutation duplicateCondition was added to duplicate field conditions.

Breaking Changes:

• The fields AgentsDetails.usage, AiResource.usage, StatsDetails.usage, and UsageStatsAiCreditDetails.usage changed type from Int! to Float!. If you're using these fields, ensure to handle float values instead of integers.
• The field FieldDependency.dependentAiAgents has been updated to use DependentAiAgentConnection instead of AutomationConnection.
• The field FieldDependency.dependentAutomations now expects a non-null return with AutomationConnection!.

These updates introduce several new capabilities, particularly around LLM provider management, while also making sure your current interactions with fields are precise in their data types. If you have any integrations using the updated or changed fields, ensure they are properly adapted to accommodate these updates.