Appearance
Hygraph
undefined
| Detail | Value |
|---|---|
| Category | CMS |
| Base URL | https://{region}.hygraph.com/v2/{project_id}/{environment} |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | hygraph |
Using Hygraph in a workflow
- Go to Connections and click New Connection.
- Pick Hygraph from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | List Entries (GraphQL) |
GET | Create Entry |
GET | Update Entry |
GET | Publish Entry |
GET | Upload Asset |
GET | Introspect Schema |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
List Entries (GraphQL)
| Detail | Value |
|---|---|
| Operation ID | list_entries_graphql__0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Hygraph connection from the Connection dropdown.
- In the Operation dropdown, select
list_entries_graphql__0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hygraph API reference.
GET
Create Entry
| Detail | Value |
|---|---|
| Operation ID | create_entry_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Hygraph connection from the Connection dropdown.
- In the Operation dropdown, select
create_entry_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hygraph API reference.
GET
Update Entry
| Detail | Value |
|---|---|
| Operation ID | update_entry_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Hygraph connection from the Connection dropdown.
- In the Operation dropdown, select
update_entry_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hygraph API reference.
GET
Publish Entry
| Detail | Value |
|---|---|
| Operation ID | publish_entry_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Hygraph connection from the Connection dropdown.
- In the Operation dropdown, select
publish_entry_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hygraph API reference.
GET
Upload Asset
| Detail | Value |
|---|---|
| Operation ID | upload_asset_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Hygraph connection from the Connection dropdown.
- In the Operation dropdown, select
upload_asset_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hygraph API reference.
GET
Introspect Schema
| Detail | Value |
|---|---|
| Operation ID | introspect_schema_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Hygraph connection from the Connection dropdown.
- In the Operation dropdown, select
introspect_schema_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hygraph API reference.