This month's update introduces enhancements to the GraphQL API, including a new query for the Flow view, identity propagation configuration capabilities, field archiving support, and improved notification handling for automation loops.

New:

• Query Added:

  • pipeFlow: A new query responsible for returning data to be shown on the new Flow view.

• Mutation Added:

  • createIdentityPropagationConfiguration: A new mutation for creating identity propagation configurations.

• Field Added: The archived field was introduced across all pipefy fields (e.g. AssigneeField, DateField) to indicate whether the field was archived.

• Enum Value: automationLoopDetected was added to the enum NotificationEvent. You can now use this value to handle specific notification cases related to automation loops.

This release introduces Start Form visibility controls, IPaaS preferences, and archived status fields for Phases and Reports. Additionally, we have deprecated the anyone_can_create_card field across multiple objects and removed enableExternalGuests from Repo preferences.

New:

• Fields Added:
  • archived was added to the PhaseField object type.
  • archived was added to the PipeReportFilterableFields object type.
  • startFormVisibility was added to the Pipe object type.
  • startFormVisibility was added to the PipeSharedProperties interface.

Deprecated:

• The anyone_can_create_card field is now deprecated across several areas including:
  • ConnectedTable
  • InternalPipe
  • Pipe
  • PublicPipeInterface
  • Repo
  • Table
• The enableExternalGuests field is deprecated in RepoPreference.
• The anyone_can_create_card argument in the pipes field of the following is now deprecated:
  • InternalOrganization
  • Organization
  • OrganizationInterface
• The anyone_can_create_card input field in UpdatePipeInput is now deprecated.

These permissions are deprecated in favor of form permissions configuration.

This week brings enhanced access control with custom role management and improved compliance through pipeline audit log exports.

New Mutations:

• createCustomRole - Creates a custom role with specified title, description, and reference role
• deleteCustomRole - Deletes a custom role by its ID
• saveRolePermission - Updates the permissions assigned to a role
• exportPipeAuditLogsReport - Exports pipeline audit logs for compliance and reporting purposes

New Queries:

• availableRoles - Retrieves available roles for a resource (Repo, Organization, or Interface) based on user permissions

Feel free to explore these additions to enhance your use of the API!

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.