Frequently Asked Questions

Webhooks & Automation

What is a webhook in Hygraph and how does it work?

A webhook in Hygraph is a feature that sends a signal whenever a specific event occurs, such as publishing content. It acts as a notification that triggers actions, like rebuilding your storefront on Netlify or Vercel. You can configure webhooks to trigger on specific models, stages, actions, and sources. Note: Webhooks require careful configuration to ensure the correct triggers and payloads are set. Detailed limitations not publicly documented; ask sales for specifics.

How do I configure a webhook in Hygraph?

To configure a webhook in Hygraph, navigate to Project Settings > AI & Automation > Webhooks and click "Add webhook." Fill in the required fields, such as name, description, method (typically POST), URL (build hook from Netlify or Vercel), and optional secret key. Select the desired triggers (e.g., Product model, PUBLISHED stage). Optionally, add headers. Save the webhook and test by publishing a content entry. Note: Ensure the webhook URL is correctly set and triggers are properly selected to avoid missed notifications.

How can I use Hygraph webhooks to trigger deployments on Netlify or Vercel?

Hygraph webhooks can trigger deployments on Netlify or Vercel by sending a POST request to a build hook URL whenever content is published. For Netlify, create a build hook in Site configuration > Build & deploy > Continuous deployment > Build hooks, then paste the generated URL into the Hygraph webhook configuration. For Vercel, follow the step-by-step guide at deploy to Vercel using Hygraph Webhooks. Note: Manual redeploys and deployment status indicators are available via the Hygraph-Netlify Integration. Limitations may exist for complex deployment workflows; consult documentation for details.

Features & Capabilities

What are the key features of Hygraph?

Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, Smart Edge Cache, localization, granular permissions, and integrations with DAM, hosting, commerce, and translation platforms. It also provides user-friendly tools for non-technical users and structured onboarding resources. Note: Some advanced features may require enterprise plans or additional configuration; check documentation for specifics.

What integrations are available with Hygraph?

Hygraph integrates with platforms such as Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot (DAM), Netlify, Vercel (hosting), Akeneo (PIM), Adminix, Plasmic, BigCommerce (commerce), and EasyTranslate (translation). For a full list, visit Hygraph's Marketplace. Note: Integration availability may depend on your plan or technical requirements.

Does Hygraph provide APIs for content and asset management?

Yes, Hygraph offers multiple APIs: GraphQL Content API for querying and manipulating content, Management API for project structure, Asset Upload API for uploading files, and MCP Server API for secure AI assistant communication. See API Reference documentation for details. Note: API usage may be subject to rate limits or permission settings.

Technical Requirements & Documentation

Where can I find technical documentation for Hygraph?

Technical documentation is available at Hygraph Documentation, including API references, schema guides, onboarding, integration instructions, and AI feature documentation. Classic Docs are available for legacy projects. Note: Documentation may be updated periodically; check for the latest guides.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. Hosting infrastructure meets international standards, and all endpoints have SSL certificates. For more details, visit Hygraph's Secure Features page. Note: Certification scope may vary; consult sales for specifics.

What security features are available in Hygraph?

Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, and secure API policies (custom origin, IP firewalls). Data centers are ISO 27001 certified and SOC 2 Type 2 compliant. Note: Some features may require enterprise plans or additional setup.

Implementation & Onboarding

How long does it take to implement Hygraph?

Implementation timelines vary by project complexity. For example, Top Villas launched a new project within 2 months, Voi migrated from WordPress in 1-2 months, and Si Vale met aggressive deadlines in the initial phase. Structured onboarding, starter projects, and extensive documentation support quick adoption. Note: Complex integrations or custom workflows may extend timelines.

How easy is it to start using Hygraph?

Hygraph is designed for easy onboarding, with resources such as free account signup, structured onboarding calls, technical kickoffs, starter projects, documentation, Slack community, webinars, and training videos. Both developers and non-technical users can quickly begin projects. Note: Advanced features may require additional training or support.

Use Cases & Customer Success

What business impact can customers expect from using Hygraph?

Customers report faster time-to-market (Komax achieved 3X faster launches), improved engagement (Samsung saw a 15% increase), cost reduction, enhanced content consistency, and scalability. AutoWeb increased website monetization by 20%, and Voi scaled multilingual content across 12 countries. Note: Results may vary based on implementation and use case.

Can you share specific case studies or customer success stories?

Yes. Samsung improved customer engagement by 15% with Hygraph. Komax managed 20,000+ product variations across 40+ markets, achieving 3X faster launches. AutoWeb saw a 20% increase in monetization. Voi scaled content across 12 countries and 10 languages. For more, visit Hygraph's case studies page. Note: Success metrics depend on project scope and execution.

Ease of Use & Feedback

What feedback have customers given about Hygraph's ease of use?

Customers praise Hygraph's intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. Sigurður G., CTO, noted the UI is intuitive for "normal people." Anastasija S. enjoys instant front-end updates. Charissa K. highlighted fast comprehension and localization. Note: Some advanced workflows may require technical expertise.

Pain Points & Problems Solved

What core problems does Hygraph solve?

Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Note: Some problems may require custom solutions or advanced configuration.

Industries & Target Audience

Which industries are represented in Hygraph's case studies?

Hygraph's case studies cover SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel and hospitality, food and beverage, eCommerce, agency, online gaming, events & conferences, government, consumer electronics, engineering, and construction. Note: Industry-specific requirements may vary; consult sales for tailored solutions.

Who is the target audience for Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies across SaaS, eCommerce, media, healthcare, automotive, and more. Note: Smaller teams or organizations with limited technical resources may need additional onboarding support.

Product Performance

How does Hygraph perform in terms of content delivery and API speed?

Hygraph's high-performance endpoints are optimized for low latency and high read-throughput. The read-only cache endpoint delivers 3-5x latency improvement. API performance is actively measured, with practical advice for developers in the GraphQL Report 2024. Note: Performance may vary based on project scale and API usage patterns.

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Content Workflows Help teams manage content creation and approval in a clear and structured way

Docs

Docs updateYou are currently reading the Studio Docs. If you were looking for the Classic Docs check here

Classic Docs

#8.1 Webhooks

Lesson 7.3 - Frontend connection: Preview URL

In this step of the tutorial you will learn how to configure a webhook.

Check out the complete lessons list for this tutorial here

#Overview

A webhook is a feature that sends a signal whenever a specific event occurs. Think of it as a notification that triggers actions. We are going to configure a webhook that will trigger published content displaying in our frontend.

#Configure a webhook

First, navigate to Project Settings > AI & Automation > Webhooks in our project, and click Add webhook.

A screen will pop up, let's complete it using the following information:

Field	Input
Name	This is the name of our webhook, we'll call it “Deploy to Storefront”.
Description	This is the description for our webhook. We'll write “Trigger published”.
Include payload	This enabled switch means that data will be sent via the webhook. We'll leave it as it is.
Method	We'll use the dropdown to select the `POST` method.
URL	This is our webhook URL or build hook. Right below this table, you'll find an explanation of how to generate this in your Netlify account right under this table.
Secret key	Add an optional secret key to sign the payload of our webhook, to allow the other end to check that the source is genuine.
Triggers	This is where we select which Models, Stages, Actions and Sources should trigger your webhook. Since we want to be able to preview our product entry drafts, we'll use the `Content model` dropdown to select the `Product` model, and the `Stage` dropdown to select `PUBLISHED`. We won't select anything under `Actions` and `Sources`, because we don't want to limit them.
Headers	Optionally configure headers by adding additional Key and Value data, we will leave this blank.

Add a build hook in Netlify

Go to your site in Netlify, navigate to Site configuration > Build & deploy > Continuous deployment > Build hooks and click Add a build hook.

Build-hooks

Give your hook the name by typing “Deploy from Hygraph” in the Build hook name field, and use the Branch to build dropdown to select main - if not already chosen.

Clicking Save generated the build hook. Copy the URL and paste it into the Hygraph Webhook modal in the URL field.

Click Add at the top of the screen to save your webhook. Your saved webhook should look something like this:

Webhook details

Once saved, you should see your webhook on the main screen.

Webhook on the main screen

You can test your new webhook by adding a new product content entry and publishing. When you click Publish, the webhook will automatically trigger Netlify rebuild your storefront!

To setup a deployment to Vercel, follow our step-by-step guide on how to deploy to Vercel using Hygraph Webhooks.

Quick Tip

You can also setup static deployments to Netlify using our Hygraph-Netlify Integration: This integration allows you to install a button in the Hygraph sidebar of a content model for manual redeploys, alongside a visual indicator of deployment status.

You've reached the end of the tutorial! Let's look into our wrap-up lesson:

Getting Started project wrap-up

Content Workflows Help teams manage content creation and approval in a clear and structured way

Docs

Docs updateYou are currently reading the Studio Docs. If you were looking for the Classic Docs check here

Classic Docs

#8.1 Webhooks

Lesson 7.3 - Frontend connection: Preview URL

In this step of the tutorial you will learn how to configure a webhook.

Check out the complete lessons list for this tutorial here

#Overview

#Configure a webhook

First, navigate to Project Settings > AI & Automation > Webhooks in our project, and click Add webhook.

A screen will pop up, let's complete it using the following information:

Field	Input
Name	This is the name of our webhook, we'll call it “Deploy to Storefront”.
Description	This is the description for our webhook. We'll write “Trigger published”.
Include payload	This enabled switch means that data will be sent via the webhook. We'll leave it as it is.
Method	We'll use the dropdown to select the `POST` method.
URL	This is our webhook URL or build hook. Right below this table, you'll find an explanation of how to generate this in your Netlify account right under this table.
Secret key	Add an optional secret key to sign the payload of our webhook, to allow the other end to check that the source is genuine.
Triggers	This is where we select which Models, Stages, Actions and Sources should trigger your webhook. Since we want to be able to preview our product entry drafts, we'll use the `Content model` dropdown to select the `Product` model, and the `Stage` dropdown to select `PUBLISHED`. We won't select anything under `Actions` and `Sources`, because we don't want to limit them.
Headers	Optionally configure headers by adding additional Key and Value data, we will leave this blank.

Add a build hook in Netlify

Go to your site in Netlify, navigate to Site configuration > Build & deploy > Continuous deployment > Build hooks and click Add a build hook.

Build-hooks

Give your hook the name by typing “Deploy from Hygraph” in the Build hook name field, and use the Branch to build dropdown to select main - if not already chosen.

Clicking Save generated the build hook. Copy the URL and paste it into the Hygraph Webhook modal in the URL field.

Click Add at the top of the screen to save your webhook. Your saved webhook should look something like this:

Webhook details

Once saved, you should see your webhook on the main screen.

Webhook on the main screen

You can test your new webhook by adding a new product content entry and publishing. When you click Publish, the webhook will automatically trigger Netlify rebuild your storefront!

To setup a deployment to Vercel, follow our step-by-step guide on how to deploy to Vercel using Hygraph Webhooks.

Quick Tip

You've reached the end of the tutorial! Let's look into our wrap-up lesson:

Getting Started project wrap-up

Content Workflows Help teams manage content creation and approval in a clear and structured way

Docs

Docs updateYou are currently reading the Studio Docs. If you were looking for the Classic Docs check here

Classic Docs

#8.1 Webhooks

Lesson 7.3 - Frontend connection: Preview URL

In this step of the tutorial you will learn how to configure a webhook.

Check out the complete lessons list for this tutorial here

#Overview

#Configure a webhook

First, navigate to Project Settings > AI & Automation > Webhooks in our project, and click Add webhook.

A screen will pop up, let's complete it using the following information:

Field	Input
Name	This is the name of our webhook, we'll call it “Deploy to Storefront”.
Description	This is the description for our webhook. We'll write “Trigger published”.
Include payload	This enabled switch means that data will be sent via the webhook. We'll leave it as it is.
Method	We'll use the dropdown to select the `POST` method.
URL	This is our webhook URL or build hook. Right below this table, you'll find an explanation of how to generate this in your Netlify account right under this table.
Secret key	Add an optional secret key to sign the payload of our webhook, to allow the other end to check that the source is genuine.
Triggers	This is where we select which Models, Stages, Actions and Sources should trigger your webhook. Since we want to be able to preview our product entry drafts, we'll use the `Content model` dropdown to select the `Product` model, and the `Stage` dropdown to select `PUBLISHED`. We won't select anything under `Actions` and `Sources`, because we don't want to limit them.
Headers	Optionally configure headers by adding additional Key and Value data, we will leave this blank.

Add a build hook in Netlify

Go to your site in Netlify, navigate to Site configuration > Build & deploy > Continuous deployment > Build hooks and click Add a build hook.

Build-hooks

Give your hook the name by typing “Deploy from Hygraph” in the Build hook name field, and use the Branch to build dropdown to select main - if not already chosen.

Clicking Save generated the build hook. Copy the URL and paste it into the Hygraph Webhook modal in the URL field.

Click Add at the top of the screen to save your webhook. Your saved webhook should look something like this:

Webhook details

Once saved, you should see your webhook on the main screen.

Webhook on the main screen

You can test your new webhook by adding a new product content entry and publishing. When you click Publish, the webhook will automatically trigger Netlify rebuild your storefront!

To setup a deployment to Vercel, follow our step-by-step guide on how to deploy to Vercel using Hygraph Webhooks.

Quick Tip

You've reached the end of the tutorial! Let's look into our wrap-up lesson:

Getting Started project wrap-up