No items found.
No items found.
  1. Help
  2. Integrations
  3. iPaaS
  4. connector-documentation
  5. GraphQL Connector

purple icon for coordination.
We’ve moved!
Our Help Center has a new home and our URLs have changed. Please update your bookmark to this page before April 30, 2026

GraphQL Connector

Generic connector for integrating with any GraphQL API using dynamic schema introspection to automatically generate fields.

🔌 GraphQL Connector

This connector is designed to work with any GraphQL API by reading its schema and generating the necessary input and output fields dynamically.

⚡ Actions

GraphQL Query

Dynamically retrieves records from a GraphQL API with auto-generated fields and built-in pagination support.

GraphQL Mutation

Executes creation, update, or deletion operations via any GraphQL API with schema-driven input and output structures.

📥 Input Parameters

  • object (String, required for Query): The GraphQL query field name populated from the schema.
  • mutation (String, required for Mutation): The GraphQL mutation name populated from the schema.
  • include_fields (Object, optional): Selection of nested or related objects to include in the results.
  • refresh_schema (Boolean, optional): Forces a re-fetch of the cached GraphQL schema.
  • page_size (Integer, optional): Number of records to retrieve per page (1-100).

📤 Output

  • nodes (Array[Object]): An array of result objects for connection or list-type queries.
  • request_id (String): A unique identifier for the API request.
  • (dynamic fields): Fields automatically generated based on the selected object's return type.

📌 Use Cases

  • Integrating with GraphQL APIs that do not have a dedicated prebuilt connector.
  • Automating data mutations such as creating, updating, or deleting records.
  • Synchronizing paginated data from various GraphQL connection-type queries.

⚠️ Notes

  • Schema Caching: The GraphQL schema is cached after the first introspection; use "Refresh schema" to clear it after API changes.
  • Automatic Pagination: Pagination arguments like first, last, before, and after are handled automatically for connection-type queries.
  • Authentication: Supports multiple methods including Bearer Token, API Key Header, OAuth2, or No Authentication.