We’ve added full automation management to the GraphQL API. Use the createAutomation, updateAutomation, and deleteAutomation mutations to create, modify, and remove automation configurations, with corresponding input and payload types (CreateAutomationInput/Payload, UpdateAutomationInput/Payload, DeleteAutomationInput/Payload).

New

• Mutation: createAutomation: You can now create automation configurations using this mutation.

• Mutation: deleteAutomation: A new mutation to delete existing automation configurations.

• Mutation: updateAutomation: Introduced a mutation to update existing automation configurations.

• Types:

  • CreateAutomationInput and CreateAutomationPayload: Added for creating automation configurations.
  • DeleteAutomationInput and DeleteAutomationPayload: Added for automation deletion operations.
  • UpdateAutomationInput and UpdateAutomationPayload: Added to facilitate the updating of automations.

Enjoy the new features and improvements! Make sure to update your integration to take advantage of the new mutations and types available.

New types have been introduced, including Base, Form, and various PortalInterface types to support new portal functionalities. Several types and mutations related to SMTP configurations have also been added, such as createSmtpConfiguration and SmtpConfiguration, enabling new email management features. Additionally, new fields were added to AiBehaviorMetadata and AiBehaviorParams, enhancing AI-related functionalities. A change was made to the value field in FieldMapInput, making it optional.

In summary, these changes focus on expanding capabilities for portal interfaces, AI behavior, and SMTP email configuration.

New:

• Types and Fields:

  • AiBehaviorMetadata: Added field pipeId.
  • AiBehaviorParams: Added field referencedFieldIds.
  • Base: A new type was introduced.
  • BreadcrumbBase: A new type was introduced.
  • BreadcrumbMainPortal: A new type was introduced.
  • Form: A new type was introduced.
  • PortalInterface: A new type was introduced with additional sub-types for specific content and elements:
    • PortalInterfaceSearchContent
    • PortalInterfaceSearchElementLink
    • PortalInterfaceSearchElementOtherForm
    • PortalInterfaceSearchElementPage
    • PortalInterfaceSearchElementPortalForm
  • PortalPage: A new type was introduced along with PortalPageElement.
  • SmtpConfiguration: A new type was introduced along with:
    • CreateSmtpConfigurationInput
    • CreateSmtpConfigurationPayload
    • SmtpConfigurationInput
    • SmtpCustomEmail
    • CreateSmtpCustomEmailWithConfigurationInput
    • CreateSmtpCustomEmailWithConfigurationPayload

• Mutations:

  • createSmtpConfiguration: Added to handle SMTP configuration creation.
  • createSmtpCustomEmailWithConfiguration: Added for creating custom emails with specific configurations.

• Fields in Interfaces and Object Types:

  • InternalOrganization, Organization, OrganizationInterface: Added field mainPortal.

Changed:

• Field Input Modification:
  • In FieldMapInput, the field value changed from being required String! to optional String.

These updates aim to enhance capabilities mainly around SMTP configurations, portal interfaces, and AI behavior parameters. Make sure to adjust your integrations accordingly to use the new types and mutations effectively.

This week's update is the addition of a new identification field, id, to both the AiBehaviorActionAttributes object type and the AiBehaviorActionAttributesInput input type. This change allows for the unique identification of actions, providing greater precision and control in managing AI behaviors.

New:

• Added a new field id to the object type AiBehaviorActionAttributes.
• Introduced id as an input field of type ID to the input object type AiBehaviorActionAttributesInput.

This changelog introduces a new createTag mutation, enabling users to create tags. It also adds new CreateInput and CreatePayload types to support this functionality. Additionally, the BulkTagsInput has been updated with a new visibleToMembers boolean field, allowing for more granular control over tag visibility.

New:

• Type CreateInput: A new input type has been added.
• Type CreatePayload: A new payload type has been added.
• Mutation createTag: Added a new mutation to the API. This allows users to create a new tag within the system.

Changed:

• Input Field visibleToMembers: A new field visibleToMembers of type Boolean was added to the BulkTagsInput input object type. You can now specify whether tags should be visible to members by including this field in your requests.

This update introduces robust organization reporting features, allowing you to create, manage, and export detailed reports. We've also added enhanced controls for AI behavior, giving you more precise configuration options. Finally, this release brings improved tag management capabilities, including bulk operations and visibility controls, while streamlining our API by removing some legacy embedding interfaces.

New:

• Types Added:

  • AiBehaviorActionAttributes
  • AiBehaviorMetadata
  • AiBehaviorParams
  • BulkTagsInput
  • BulkTagsPayload
  • CreateOrganizationReportInput
  • CreateOrganizationReportPayload
  • DeleteOrganizationReportInput
  • DeleteOrganizationReportPayload
  • ExportOrganizationReportInput
  • ExportOrganizationReportPayload
  • OrganizationReport
  • OrganizationReportConnection
  • OrganizationReportEdge
  • OrganizationReportExport
  • UpdateOrganizationReportInput
  • UpdateOrganizationReportPayload
  • UpdateTagInput
  • UpdateTagPayload
  • UpdateTagsVisibilityByCategoryInput
  • UpdateTagsVisibilityByCategoryPayload

• Fields Added:

  • aiBehaviorParams to AutomationActionParams
  • createOrganizationReport, createTagsInBulk, deleteOrganizationReport, exportOrganizationReport, updateOrganizationReport, updateTag, and updateTagsVisibilityByCategory to mutations in Mutation type.
  • organizationReport, organizationReportExport, and organizationReports to queries in Query type.
  • teamMembers to Phase
  • visibleToMembers to both Tag and TagsByCategory

Removed:

• Types Removed:

  • InterfaceEmbedCreateMutationInput
  • InterfaceEmbedCreateMutationPayload

• Fields Removed:

  • interfaceEmbedCreate from Mutation
  • type and actionAttributes from AiBehaviorActionAttributesInput and AiBehaviorParamsInput, respectively.

Changed:

• Field Updates:
  • actionType was added as a required input field to AiBehaviorActionAttributesInput.
  • actionsAttributes was added as a required input field to AiBehaviorParamsInput.

This API update focuses on improving assistant and dependency management. For assistants, the assistantId fields were removed from AppInterface and InterfaceType, replaced by a new, standardized assistant field in those same types, alongside the introduction of the InterfaceAssistant type. Regarding dependencies, the DependentConnection, DependentConnectionConnection, and DependentConnectionEdge types were added, and the dependentConnections field was included in the FieldDependency type for more robust dependency connection management.

👉 You can explore these updates in more detail directly in our GraphQL Page

New:

• Field assistant was added to the object type AppInterface. This field is a new way to reference assistants.
• Field assistant was added to the interface InterfaceType. This enables a standardized way to work with assistants across different implementations.
• Type DependentConnection was introduced. This type likely pertains to handling dependencies.
• Type DependentConnectionConnection was added. It's part of the new types dealing with dependencies.
• Type DependentConnectionEdge was added to support the DependentConnection type.
• Field dependentConnections was added to the object type FieldDependency. This field helps in managing dependency connections.
• Type InterfaceAssistant was introduced to facilitate operations pertaining to assistants.

Removed:

• Field assistantId was removed from the object type AppInterface. Use the new assistant field instead.
• Field assistantId was removed from the interface InterfaceType. The new assistant field should be used as its replacement.

This changelog introduces new queries and mutations for managing field dependencies and AI settings. Key additions include the dependentEmailTemplates query and the updateAiSettings mutation, along with their associated types. Additionally, the dependentConditionals query has been updated to enforce a non-null return type.

New:

• Query dependentEmailTemplates was added to the FieldDependency type. This allows you to retrieve email templates that have dependencies on certain fields.
• Mutation updateAiSettings was added. This mutation can be used to update settings related to AI.
• DependentEmailTemplate, DependentEmailTemplateConnection, and DependentEmailTemplateEdge types were added. These are used to manage email templates that have specific dependencies.
• UpdateAiSettingsInput and UpdateAiSettingsPayload types were added to support the updateAiSettings mutation.

Changed:

• The query dependentConditionals in the FieldDependency type now always requires a non-null return type, changing from FieldConditionConnection to FieldConditionConnection!. This means a valid result will always be expected.

This update introduces new queries, mutations, and types focused on three key areas: automation, AI integration, and notification management. It includes features for exporting automation jobs, running automation simulations, controlling AI preferences, and handling notifications with advanced filtering options.

👉 You can explore these updates in more detail directly in our GraphQL Page

New:

• Queries:

  • automationJobsExport: A new query to export automation jobs.
  • notifications: A new query to retrieve notifications.
  • templateAgents: A new query to get template agents.

• Mutations:

  • createAutomationJobsExport: A new mutation for creating automation jobs exports.
  • createAutomationSimulation: A new mutation for creating automation simulation.

• Fields:

  • assistantId was added to AppInterface and InterfaceType, enhancing the interface with assistant identification capabilities.
  • skillId was added to ElementInterface and InterfacePageElement, allowing integration of specific skills.
  • aiAgentsEnabled and aiCopilotEnabled were added to RepoPreference for better AI functionality control.

• Types:

  • AiBehaviorActionAttributesInput, AiBehaviorMetadataInput, AiBehaviorParamsInput: New input types supporting AI behavior settings.
  • AutomationActionParamsInput, AutomationAiParamsInput, AutomationEventParamsInput, AutomationJobsExport, AutomationSimulationActions, AutomationSlaRulesHolidayInput, AutomationSlaRulesHoursInput, AutomationSlaRulesParamsInput, AutomationTaskParamsInput, CreateAutomationJobsExportInput, CreateAutomationJobsExportPayload, CreateAutomationSimulationInput, CreateAutomationSimulationPayload: New types related to automation configurations and processes.
  • CronInput, ExportStatus: New types for cron jobs and export status tracking.
  • InternalError: A new type for handling internal errors.
  • Notification, NotificationConnection, NotificationEdge, NotificationEvent, Notifications: New types focusing on notification handling.
  • PeriodFilter, SearchConditionInput, TemplateAgent: New types for advanced filtering, search conditions, and templated agents.

These updates bring significant improvements in automation, AI integration, and notification management across the API.

This week, we introduced new features to the GraphQL API, including support for tag categories with the addition of the tagCategories query and updateTagCategory mutation, as well as new related types. We also enhanced file upload capabilities by adding new fields to the CreatePresignedUrlInput input object.

👉 You can explore these updates in more detail directly in our GraphQL Page

New:

• Query: tagCategories field was added. This allows you to query the new TagCategory type.

• Mutation: updateTagCategory field was added. Use this to update existing tag categories using the new UpdateTagCategoryInput and receive results in the UpdateTagCategoryPayload type.

• Types: The following new types were introduced:

  • TagCategory: A new type representing categories of tags.
  • UpdateTagCategoryInput: This type allows you to provide input data for updating a tag category.
  • UpdateTagCategoryPayload: This type provides the payload results from the updateTagCategory mutation.

• Input Object Fields:

  • contentChecksum, contentLength, and customFilePath fields were added to the CreatePresignedUrlInput input object type. These fields offer more control and specification when creating a presigned URL.

This changelog introduces new queries and types primarily focused on automation features, including logs, simulations, and event handling. Additionally, it adds new capabilities for retrieving user suggestions.

👉 You can explore these updates in more detail directly in our GraphQL Page

New:

• Queries:

  • automatedFormulaOperations: Added a new query to assist in retrieving automated formula operations.
  • automationEventAttributes: Added a new query to get details about automation event attributes.
  • automationInitialValues: Introduced a query for fetching initial values required for automation processes.
  • automationLogs: New query added for accessing automation logs by automation.
  • automationLogsByRepo: Allows querying of automation logs by repo ID.
  • automationSimulation: Added a query to retrive the automation simulation result by ID.
  • usersSuggestions: This new query provides the users suggestion by organization UUID.

• Types:

  • AutomatedFormulaOperation: Added as a new type to define operations on automated formulas.
  • AutomationEventAttribute: Introduced as a new type for attributes related to automation events.
  • AutomationEventAttributes: Added to store a collection of automation event attributes.
  • AutomationLog: A new type that records the details of automation logs.
  • AutomationLogConnection: Helps in connecting various automation logs.
  • AutomationLogDetails: Provides detailed insights within an automation log.
  • AutomationLogEdge: Added to define edges between automation logs.
  • AutomationLogStatus: Represents the status of an automation log.
  • AutomationSimulation: A type for running simulations of automation workflows.
  • UsersSuggestions: A new type to represent user suggestions.
  • UsersSuggestionsConnection: Connects user suggestions data.
  • UsersSuggestionsEdge: Defines edges within user suggestions.