# Paginated data not being passed through remainder of flow

**URL:** https://connective.celigo.com/t/paginated-data-not-being-passed-through-remainder-of-flow/532
**Category:** Integrator.io
**Tags:** pagination, graphql, debug, shopify, flow-builder
**Created:** [February 22, 2023, 6:19pm UTC](https://connective.celigo.com/t/paginated-data-not-being-passed-through-remainder-of-flow/532 "2023-02-22T18:19:12Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)
#### Post date: [March 21, 2025, 1:11am UTC](https://connective.celigo.com/t/paginated-data-not-being-passed-through-remainder-of-flow/532/11 "2025-03-21T01:11:46Z")

</div>

I want to add to this post a bit since we're all being forced into GraphQL 🙂 . I'm also curious where you all are having to escape quotes because non-escaped quotes are working fine for me.

### GraphQL connector setup

If you're using the GraphQL connector we have, you would have a setup similar to what I have below in order to paginate on your export. Our branded Shopify connector will have this better GraphQL editor baked into it in the next release as well, so this will be more relevant.

Query:

```graphql
query getProductVariants($first: Int, $after: String) {
  productVariants(first: $first, after: $after) {
    edges {
      node {
        id
        title
        sku
        price
        compareAtPrice
        inventoryQuantity
        availableForSale
        updatedAt
        product {
          id
          title
        }
        selectedOptions {
          name
          value
        }
        image {
          originalSrc
          altText
        }
      }
    }
    pageInfo {
      hasNextPage
      endCursor
    }
  }
}

```

Variables:

```graphql
{ 
  "first":200,
  "after": {{#if export.http.paging.token}}"{{export.http.paging.token}}"{{else}}null{{/if}}
}

```

 ![This image shows a configuration screen for exporting data via a GraphQL query using the HTTP POST method, retrieving product variants with pagination support. (Captioned by AI)](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/f/f5733fba8a97cb8cb0adaf0f0bf633160267738e.png)  
 ![The image shows a configuration interface for setting up API paging with the "Next page token (cursor)" method and specifies the path to the next page token as "data.productVariants.pageInfo.endCursor." (Captioned by AI)](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/f/f498f09f4a66b4ca6d7b4d28613f0506e0be9b90.png)  
 ![The image shows a settings interface for specifying a non-standard API response pattern, with a path to records in the HTTP response body set as "data.productVariants.edges." (Captioned by AI)](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/6/66464ce6239894ed2448a50aa5c1c322bed66701.png)

### GraphQL setup using HTTP connector or Shopify in HTTP form

If using the existing Shopify connector or the normal HTTP connector, your setup would be something more like this.

Post body

```json
{
  "query": "query getProductVariants($first: Int, $after: String) { productVariants(first: $first, after: $after) { edges { node { id title sku price compareAtPrice inventoryQuantity availableForSale updatedAt product { id title } selectedOptions { name value } image { originalSrc altText } } } pageInfo { hasNextPage endCursor } } }",
  "variables": { "first": 2, "after": {{#if export.http.paging.token}}"{{export.http.paging.token}}"{{else}}null{{/if}} }
}

```

 ![The image shows a configuration interface for exporting data via an HTTP POST request to a Shopify API endpoint using a GraphQL query with Handlebars templates. (Captioned by AI)](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/e/e1b1511029a31d7969a1e079bc6448abd0f2087f.png)

 ![This image is a user interface setup for API paging, where the paging method is "Next page token," with the token located in the HTTP response body under the path "data.productVariants.pageInfo.endCursor." (Captioned by AI)](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/e/e0b4d342c747fdafefdba69d1e1827cd5e257ee0.png)  
 ![The image shows a configuration screen where a user specifies a path to records in an HTTP response body as "data.productVariants.edges" for non-standard API response patterns. (Captioned by AI)](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/8/8e901b80ca18534c565457ce64f9b1bf3d2a1e4c.png)

---

_[View the full topic](https://connective.celigo.com/t/paginated-data-not-being-passed-through-remainder-of-flow/532)._