2. Enhancement

Enhanced V3 Inbound Mapping to Support the Inbound Copy Node Function

We have enhanced Inbound Mapping V3 to support the Copy Node function.

Previously, Inbound Mapping V3 did not support copying nodes. With this enhancement, users can now copy nodes in the inbound mapping target structure, including copying multiple nodes with the same name. This functionality is useful when working with flat data that needs to be mapped into repeated child records. For example, one Account record may contain data for two Contact records, such as Contact 1 fields and Contact 2 fields in a flat table, flat JSON, or flat XML structure. In this case, users can copy the Contact node and map each set of Contact fields separately. This makes it easier to map one parent record to multiple child records in Inbound Mapping V3.

After this enhancement:

The Copy Node function is supported in Inbound Mapping V3.
Users can copy one or multiple nodes as needed.
Users can create copied nodes with the same node name.
This provides more flexibility when configuring inbound mappings with repeated or similar node structures.

Enhanced Workday Adapter to Support Limit + Offset Pagination

We have enhanced the Workday Adapter to support Limit + Offset pagination when retrieving data from an API. Previously, the adapter did not provide pagination configuration. This made it difficult to retrieve large result sets from APIs that return data across multiple pages. With this enhancement, users can now enable Pagination in the adapter configuration and use the Limit + Offset pagination method.

For Limit + Offset pagination, users can configure where the data retrieval should start and how many records should be retrieved per request.

Offset Index defines the starting position of the records.
Limit Index defines how many records should be retrieved per request. For example, if users want to retrieve 10 records, they can set the Limit Index value to 10.
For Business Data Field Name is an optional field. Use this field when the API response is JSON and users want to check whether a specific business data node contains records. Example: MyAccount. If users want to check whether the direct response body is empty, this field can be left blank. Pagination stops automatically when the expected business data node is missing or empty in the API response.

Enhanced ServiceNow Adapter to Support Limit + Offset Pagination

We have enhanced the ServiceNow Adapter to support Limit + Offset pagination when retrieving data from the ServiceNow API. Previously, the ServiceNow Adapter did not provide pagination configuration. This made it difficult to retrieve large result sets when the ServiceNow API returned data across multiple pages. With this enhancement, users can now enable Pagination in the ServiceNow Adapter configuration and use the Limit + Offset pagination method. The supported pagination method is: Limit + Offset.

For Limit + Offset pagination, users can configure where the data retrieval should start and how many records should be retrieved per request.

Offset Index defines the starting position of the records.
Limit Index defines how many records should be retrieved per request. For example, if users want to retrieve 10 records, they can set the Limit Index value to 10.
Business Data Field Name is optional. Use this field when the API response is JSON and users want to check whether a specific business data node contains records. Example: MyAccount. If users want to check whether the direct response body is empty, this field can be left blank. Pagination stops automatically when the expected business data node is missing or empty in the API response.

Enhanced GraphQL Adapter to Support Pagination

We have enhanced the GraphQL Adapter to support pagination when retrieving data from a GraphQL API. Previously, the GraphQL Adapter did not provide pagination configuration. This could make it difficult to retrieve large result sets from GraphQL APIs that return data in multiple pages.

With this enhancement, users can now enable Pagination in the GraphQL Adapter and configure the pagination method. The GraphQL Adapter now supports the following pagination methods:

Limit + Offset
Limit + Cursor

For Index + Offset pagination, users can configure where data retrieval should start and how many records to retrieve per request.

Offset Index defines the starting position of the records.
Limit Index defines how many records should be retrieved. For example, if users want to retrieve 10 records, they can set the Limit Index value to 10.

For Limit + Cursor pagination, users can configure how many records should be retrieved per request and which response field should be used as the cursor for the next request.

Limit Index defines how many records should be retrieved. For example, if users want to retrieve 10 records, they can set the Limit Index value to 10.
End Cursor Field Name defines the response field that returns the cursor/token of the last record.

After the first callout retrieves records 1 to 10, the API response returns an endCursor value for the last record. The adapter uses this endCursor value in the next callout to retrieve the next set of records, such as records 11 to 20.

For Business Data Field Name is an optional field. Use this field when the API response is JSON and users want to check whether a specific node contains data. Example: data

This enhancement allows the GraphQL Adapter to retrieve large datasets page by page instead of only processing a single response. It improves flexibility and supports GraphQL APIs that require paginated data retrieval.

Enhanced SOAP Adapter to Support Pagination

We have enhanced the SOAP Adapter to support pagination when retrieving data from an API. Previously, the adapter did not provide pagination configuration. This made it difficult to retrieve large result sets from APIs that return data in multiple pages. With this enhancement, users can now enable Pagination in the adapter and configure the pagination method according to the API requirements.

The adapter now supports the following pagination methods:

Limit + Offset
Page Size + Cursor

For Limit + Offset pagination, users can configure where the data retrieval should start and how many records should be retrieved per request.

Offset Index defines the starting position of the records.
Limit Index defines how many records should be retrieved per request. For example, if users want to retrieve 10 records, they can set the Limit Index value to 10.

For Page Size + Cursor pagination, users can configure how many records should be retrieved per request and which response field should be used as the cursor for the next request.

Page Size defines how many records should be retrieved per request.
End Cursor Field Name defines the response field that returns the cursor/token of the last record.

For example, if users want to retrieve 10 records, they can set the Page Size value to 10. After the first callout retrieves records 1 to 10, the API response returns an endCursor value for the last record. The adapter uses this endCursor value in the next callout to retrieve the next set of records, such as records 11 to 20.

The Business Data Field Name is an optional field. Use this field when the API response is JSON and users want to check whether a specific response node contains data. Example: data. If users want to check whether the direct response body is empty or not, this field can be left blank.

Empty Response Handling

For pagination, the SOAP adapter can stop pagination when the response does not contain business data or when the business node is empty. For example, if the response does not return the expected business node or the node is empty, pagination will stop, and processing can be completed successfully instead of creating a failed response message.

Enhanced Monday.com Adapter to Support Pagination

We have enhanced the Monday.com Adapter to support pagination when retrieving data from a Monday.com API. Previously, the Monday.com Adapter did not provide pagination configuration. This could make it difficult to retrieve large result sets from Monday.com APIs that return data in multiple pages.

With this enhancement, users can now enable Pagination in the Monday.com Adapter and configure the pagination method. The Monday.com Adapter now supports the following pagination methods:

Limit + Offset
Limit + Cursor

For Index + Offset pagination, users can configure where data retrieval should start and how many records to retrieve per request.

Offset Index defines the starting position of the records.
Limit Index defines how many records should be retrieved. For example, if users want to retrieve 10 records, they can set the Limit Index value to 10.

For Limit + Cursor pagination, users can configure how many records should be retrieved per request and which response field should be used as the cursor for the next request.

Limit Index defines how many records should be retrieved. For example, if users want to retrieve 10 records, they can set the Limit Index value to 10.
End Cursor Field Name defines the response field that returns the cursor/token of the last record.

For Business Data Field Name is an optional field. Use this field when the API response is JSON and users want to check whether a specific node contains data. Example: data

This enhancement allows the Monday.com Adapter to retrieve large datasets page by page instead of only processing a single response. It improves flexibility and supports Monday.com APIs that require paginated data retrieval.