# Generic GraphQL request action
## What is GraphQL?
{% hint style="info" %}
Learn more about GraphQL in its official documentation [here](https://graphql.org/learn/introduction/).
{% endhint %}
GraphQL is an open-source query language for APIs and a server-side runtime for fulfilling those queries. It enables clients to interact with a single endpoint to get the exact data they need, without chaining requests together. Unlike traditional REST APIs that return fixed datasets, GraphQL allows clients to request specific data, eliminating over-fetching or under-fetching of data and offering improved efficiency. The [GraphQL Schema](https://graphql.org/learn/schema/) defines the structure of the data and available operations, serving as a clear contract between the frontend and backend. Like REST APIs, GraphQL is composed of a basic request and response for each call. While REST APIs rely on multiple endpoints for this process, GraphQL shifts the responsibility of defining what should be called back to the user.
GraphQL in Rewst works off of two *operation types*:
1. Query: Used for reading or fetching data
2. Mutation: Used for writing, updating, or deleting data
{% hint style="info" %}
GraphQL has a third operation type called subscription. Rewst's generic GraphQL action currently only supports queries and mutations. If there is a subscription you are looking to use in Rewst, please submit a request to our product team for a dedicated action.
{% endhint %}
## What is the Rewst GraphQL generic request action?
{% hint style="warning" %}
Before using the Generic GraphQL request action, we recommend that you have:
* An understanding of GraphQL query structure and syntax
* Familiarity with Rewst's data model and the below available schema documentation
{% endhint %}
\
The Rewst GraphQL generic request action is used for making authenticated requests against Rewst's GraphQL API. This action is available in the Rewst actions section of the Workflow Builder's actions library, but is open-ended in its capabilities. It enables:
* Direct API access: Execute custom GraphQL queries and mutations against Rewst's backend
* Advanced data retrieval: Access data structures not available through standard actions
* Custom automation: Build sophisticated workflows with precise data control
* Administrative operations: Perform bulk operations and administrative tasks programmatically
Make your choices in the **Parameters** tab of the action's settings to set it up in your workflow:
* **Operation type**: Choose the type of GraphQL operation, **query** or **mutation**
* **Graph operation**: The name of the specific GraphQL operation to execute
* Uses the Graph Operations reference
* Options in the drop-down list will dynamically populate based on your selected operation type
* **Variable values**: Variables to pass to the GraphQL operation
* JSON object type, but can be passed via Jinja
* Contains the input parameters for the selected operation
* **Response fields**: Enter text into this field to specify the fields to include in the GraphQL response
* Only provide the inner content, as it will be wrapped in curly braces
* Example, `id orgName email { name }`
* **Raw query**: The complete raw GraphQL query string to execute
* An advanced alternative to using the other fields and selectors in the Parameters tab
* Allows for full control over query structure
## Filtering arguments: Where versus search
Every plural list query in the Generic GraphQL Request action accepts up to two filtering arguments: *where* and *search*. They are not interchangeable.
#### Where: Equality only - `field: value` → `WHERE field = value`
`where` accepts a flat object of `field: value` pairs. Each pair is rendered as `WHERE field = value`. There's no way to express greater than, in this list, contains substring, etc. through `where`.
The set of fields exposed in each `