This week's API updates deliver a complete pipe reporting feature set that includes three new mutations (createPipeReport, updatePipeReport, deletePipeReport) and enhanced data retrieval capabilities through three new queries (pipeReports, pipeReportColumns, pipeReportFilterableFields) with its GraphQL types, inputs and payloads.

New:

Mutations

• createPipeReport: A mutation to create new pipe reports.
• deletePipeReport: A mutation to delete existing pipe reports.
• updatePipeReport: A mutation to update existing pipe reports.

Queries

• pipeReportColumns: A query to retrieve pipe report columns.
• pipeReportFilterableFields: A query to identify which fields are filterable in pipe reports.
• pipeReports: A query to fetch a list of pipe reports.

Types

• CreatePipeReportInput: Input type for creating pipe reports.
• CreatePipeReportPayload: Payload type returned when a pipe report is created.
• DeletePipeReportInput: Input type for deleting pipe reports.
• DeletePipeReportPayload: Payload type returned when a pipe report is deleted.
• PipeReportConnection: Describes the connection for pipe reports.
• PipeReportEdge: Represents an edge in a connection of pipe reports.
• PipeReportFieldOptionsGQL: Offers field options for pipe reports.
• PipeReportFilterableFields: Contains filterable fields for pipe reports.
• PipeReportFilterableGQLType: Defines filterable GraphQL types for pipe reports.
• PipeReportFilterablePhasesGQL: Specifies filterable phases for pipe reports.
• PipeReportSortField: Describes fields available for sorting pipe reports.
• PipeReportsOrder: Defines the order of pipe reports.
• Sort: Specifies sorting options.
• UpdatePipeReportInput: Input type for updating pipe reports.
• UpdatePipeReportPayload: Payload type returned when a pipe report is updated.

This release enables advanced filtering by phases and field types, flexible sorting and pagination, and comprehensive report management—giving you everything needed to build powerful, customizable reporting interfaces with complete programmatic control over your pipe data analytics.

Enjoy the new features!

This week's updates bring enhanced querying options for cards and new fields for tracking AI credits and card submission information.

New:

• Fields and Arguments:

  • aiCreditsAddonAvailable field added to:

    • Organization
    • OrganizationInterface

  • submitterEmail argument added to the createCard mutation to capture the email of public form submitters.

  • pipeRelationId argument added to the cards query for authorization purposes when listing cards through pipe relations.

  • throughConnectors argument added to the cards query to filter cards through connected fields.

These updates expand query capabilities and provide better control over card creation workflows and organization data access.

This week's update makes it easier to manage AI-related features. We've added a new generatedByAi field on the NodeFieldValueInput to mark values created by AI, and we've added ai_credits to the SubscriptionLimits enum to give you more control over AI subscriptions.

New:

• Input field generatedByAi of type Boolean: This field is now available in the NodeFieldValueInput input object type. You can use it to indicate if a field value was generated by AI.

• Enum value ai_credits: Added to the SubscriptionLimits enum, this new value might help in managing AI-related subscription capabilities.

This update adds new fields to help you manage AI features and SMTP configurations. You can now track who disabled AI features and why, check for SMTP reauthentication, and specify reference connectors when creating cards.

New:

• Field aiDisabledBy has been added to the OrganizationPreferences type. This new field can help you know who disabled AI-related features.
• Field aiDisabledReason has also been added to the OrganizationPreferences type. It provides insights into why AI-related features might be disabled.
• Field reauthRequired is now part of the SmtpCustomEmail type. It indicates whether reauthentication is required for SMTP custom emails.
• Field hasAddon has been introduced to the UsageStatsAiCreditDetails type. This field helps to identify if there's an addon associated with AI credit usage.
• Input field throughConnectors has been added to the CreateCardInput input object type. This facilitates specifying reference connectors when creating a card.

These updates enhance information transparency and connectivity within the API, helping users better manage organizational settings and usage statistics.

This update expands the autoFillFields query with a new throughConnectors argument, and introduces the filterAuthorizedFormsToMe query to retrieve only forms specifically authorized for you.

New:

• Argument: throughConnectors was added to the query autoFillFields. This argument expects a ReferenceConnectorFieldInput type, and expands the functionality of the query.
• Query: filterAuthorizedFormsToMe was added to the query object type. You can now use this query to access forms specifically authorized for you.

This update introduces new organization usage statistics types and queries, including AI credit usage details, while removing the pages field from InterfaceType.

✨ New

Object Types

• AiResource: Represents an AI automation resource, with fields to indicate whether it is enabled and the number of times AI automation credit was used.

• UsageStats: Provides statistics related to organization usage.

  • Includes the field aiCredits (type: UsageStatsAiCreditDetails), which returns detailed information on AI credit usage.

• UsageStatsAiCreditDetails: Details about AI credits usage, including:

  • active: Whether AI credits are active.
  • aiAutomation / assistants: AI usage broken down by resource.
  • filterDate: A time filter to restrict results.
  • freeAiCredit: Free credit information.
  • limit: Credit limit.
  • usage: Number of times credits were consumed.
  • updatedAt: Last updated timestamp.

• FilterDate: Defines a period filter with from and to fields (both ISO8601DateTime).

• FreeAiCredit: Represents free AI credits with limit and usage.

Schema Additions

• Organization

  • New field usageStats: Provides aggregated organization usage statistics (including AI credits).

• Queries

  • aiCreditUsageStats: Fetch AI credit usage statistics.

🗑️ Removed

• pages field removed from the InterfaceType interface.

Hey there! We're excited to share what's new in our latest update. We've added a couple of features to make your workflow smoother and data access even easier. Here's a look at the changes:

New:

• repoName field was added to the DataSource type. This enhancement allows you to now retrieve the repository name associated with a data source.
• tableElements field was added to the InterfacePage type. This addition provides access to elements of a table within the interface.

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.