Execute GraphQL
Infoveave Data Automation — RESTful
GraphQL query in. Structured data table out. Automatically in every workflow run.
GraphQL has become the API standard for modern SaaS platforms including Shopify, Salesforce, GitHub, Contentful, and many others. Execute GraphQL brings native GraphQL support to the Infoveave workflow canvas — write the query, define variables, configure pagination, and the activity returns a structured table from the response. Unlike REST wrappers, Execute GraphQL sends true GraphQL operations with variables, cursor-based pagination, and operation-level type control (query vs mutation), making it the right choice for any GraphQL-powered data source in your pipeline.
What Execute GraphQL does
Execute GraphQL queries and mutations from inside your Infoveave workflow. Pass variables, handle pagination, parse responses into structured tables, and integrate any GraphQL-powered API — from Shopify to Salesforce — as a native workflow data source.
When to use Execute GraphQL
- Your data source exposes a GraphQL API — such as Shopify, Salesforce, GitHub, Contentful, or any other GraphQL platform
- You need to run a GraphQL mutation to create or update records in an external system as a workflow step
- The GraphQL endpoint uses cursor-based pagination and you need all pages retrieved automatically
- You need to pass dynamic variables to the GraphQL operation from the workflow context
When to avoid it
- You are connecting to a standard REST API — use Execute API instead
- You are querying an OData endpoint — use Retrieve OData
- You are integrating specifically with Microsoft Dynamics CRM — use Microsoft Dynamics for its native entity and filter support
- You are querying a relational database with SQL — use Execute Query
Where it fits in your Infoveave automation
Execute GraphQL is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Execute GraphQL
Real scenarios where this transformation saves hours of manual work.
Shopify Order Data Extraction
A nightly e-commerce workflow uses Execute GraphQL to query the Shopify Admin API for all orders placed in the past 24 hours. The query uses cursor-based pagination to retrieve orders across all pages and passes date range variables dynamically. The extracted order table is loaded into the ERP via Insert into Database.
GitHub Repository Metrics Collection
A weekly engineering analytics workflow queries the GitHub GraphQL API to retrieve pull request counts, review times, and merge statistics per team. Variables pass the organization name and date range from the workflow context. The metrics table feeds into a team performance dashboard.
Contentful Content Export
A content operations workflow queries the Contentful GraphQL API to export all published articles in a specific content type, paginating through all results. The content data flows into a transformation pipeline that produces SEO metadata summaries for the editorial team.
See Execute GraphQL in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
shopify-graphql-apihttps://yourstore.myshopify.com/admin/api/2025-01/graphql.jsonqueryquery GetOrders($first: Int!, $after: String) {
orders(first: $first, after: $after) {
edges { node { id name totalPriceSet { shopMoney { amount } } } }
pageInfo { hasNextPage endCursor }
}
}
{"first": 50}data.orders.edgesendCursorCursorInput Data
| (GraphQL connection and query configuration — no row input required) |
Output Data
| OrderID | OrderName | TotalAmount |
|---|---|---|
| 1001 | #1001 | 1200.00 |
| 1002 | #1002 | 435.00 |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Connection
The registered GraphQL API connection in Infoveave Studio. Includes the base URL and authentication (Bearer token, API key, or OAuth). The connection handles authentication for every operation.
Operation
The GraphQL operation type: 'query' for read operations that retrieve data, or 'mutation' for write operations that create, update, or delete records in the external system.
Query
The GraphQL operation string — the full query or mutation defining which fields to request and which arguments to pass. Use named operations with variables for parameterized queries.
Variables
JSON key-value object of GraphQL variables referenced in the query using the $variableName syntax. Supports Infoveave workflow variable placeholders for dynamic values such as date ranges, IDs, or counts.
Root of Response
JSONPath to the array of records in the GraphQL response. For example, 'data.orders.edges' extracts the edges array from the Shopify orders response. Each element in the array becomes a row in the output table.
Next Page Key / Next Key Behaviour
Configures cursor-based pagination. Set Next Page Key to the field in the response containing the cursor (e.g., 'endCursor') and Next Key Behaviour to 'Cursor'. The activity automatically fetches subsequent pages until hasNextPage is false.
Frequently asked questions
Everything you need to know about Execute GraphQL in Infoveave.
Also in RESTful — and what runs before & after
Transformations in the same family as Execute GraphQL, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Execute GraphQL is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
