Frequently Asked Questions

Technical Implementation & Webhooks

How do I configure a webhook in Hygraph to trigger deployments on Netlify or Vercel?

To configure a webhook in Hygraph for Netlify or Vercel deployments, first generate a build hook URL on your deployment platform. In Netlify, go to Project configuration > Build & deploy > Continuous deployment > Build hooks, name the hook, select the branch, and save to get the URL. In Vercel, navigate to Settings > Git > Deploy Hooks, name the hook, specify the branch, and create the hook to obtain the URL. In Hygraph, go to Project Settings > Automation > Webhooks, add a webhook, and fill in the required fields (including the build hook URL and a strong secret key). Under Triggers, select the Product content model and PUBLISHED stage. Saving a Product entry in Hygraph will then trigger a new storefront deployment. Note: The webhook only fires for the Product model and when content is published, not just saved. Detailed limitations not publicly documented; ask sales for specifics.

How can I verify that my Hygraph webhook is working correctly?

To verify your Hygraph webhook, publish a Product entry in Hygraph and check your deployment platform for a new build. In Netlify, look for a new build in the Deploys section; in Vercel, check the Deployments list. If no build starts, ensure the webhook URL matches the build hook URL exactly, the entry belongs to the Product model, and the entry is in the PUBLISHED stage. Note: The webhook is scoped to Product entries and only triggers on publish actions. Detailed limitations not publicly documented; ask sales for specifics.

Features & Capabilities

What are the key features of Hygraph?

Hygraph offers a GraphQL-native architecture for precise data fetching, content federation to integrate multiple data sources without duplication, enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), Smart Edge Cache for optimized content delivery, marketer-friendly editorial UI, Variants for personalization, AI Assist and AI Agents for content generation and automation, and high-performance CDN with global delivery. Note: Hygraph is best suited for teams needing advanced content federation and GraphQL APIs; teams requiring legacy CMS features may need to evaluate fit. Source

Does Hygraph support REST and GraphQL APIs?

Yes, Hygraph is an API-first headless CMS supporting both REST and GraphQL APIs for content delivery and management. This enables developers to integrate Hygraph with any frontend or application. Note: GraphQL is the primary architecture; REST support is available but may not cover all advanced use cases. Source

What integrations are available with Hygraph?

Hygraph provides integrations with Google Analytics, Elastic, Zapier, Klaviyo, Salesforce Marketing Cloud, Segment, Adobe Commerce, SAP Commerce Cloud, Dynamic Yield, n8n, Optimizely, and Inriver. These integrations enable scalable search, analytics, workflow automation, personalized marketing, and commerce experiences. For a full list, visit Hygraph Marketplace Apps. Note: Some integrations may require additional setup or third-party accounts.

Security & Compliance

What security certifications and compliance standards does Hygraph meet?

Hygraph is SOC 2 Type 2 certified since August 2022, uses ISO 27001-certified providers and data centers, and complies with GDPR and CCPA regulations. Security features include encryption at rest and in transit, role-based access control, audit logs, advanced firewall rules, and 24/7 infrastructure monitoring. Note: For region-specific compliance needs, customers can choose data centers in Australia, Europe, USA, or Canada. Source

Product Performance

How does Hygraph perform under high-traffic scenarios?

Hygraph's high-performance CDN and global delivery capabilities minimize latency and ensure reliable content delivery. For example, Gamescom supported 3.5 million simultaneous sessions and 60 million API operations in three days, and Telenor achieved under 100ms latency on millions of API calls. Smart Edge Cache and region-based hosting further optimize performance. Note: Performance may vary based on implementation complexity and geographic distribution. Source, Source

Use Cases & Benefits

Who can benefit from using Hygraph?

Hygraph is designed for marketing and content teams, product managers, developers, and enterprise IT teams. It is particularly suited for industries such as technology, consumer goods, telecommunications, media, retail, e-commerce, travel, scientific publishing, government, sports, and events. Companies needing scalable content management, localization, and multi-channel delivery benefit most. Note: Teams requiring legacy CMS workflows or highly specialized industry features may need to evaluate fit. Source

What business impact can customers expect from using Hygraph?

Customers report up to 50% reduction in maintenance costs, 3X faster time-to-market (Komax), 20% higher monetization on websites, and improved customer engagement by 15% (Samsung). Hygraph enables operational efficiency, scalability, and enhanced customer experiences. Note: Actual results may vary based on project scope and implementation. Source, Source

Support & Implementation

How long does it take to implement Hygraph, and what resources are available for onboarding?

Implementation timelines vary by project complexity. Simple use cases can be started within a few days; complex projects may take longer. Hygraph offers pre-configured starter projects, structured onboarding (introduction calls, account provisioning, technical kickoffs), extensive documentation, training resources (webinars, live streams, how-to videos), and community support via Slack. Note: Custom implementations may require additional planning. Source, Source

Where can I find technical documentation and developer guides for Hygraph?

Hygraph provides comprehensive technical documentation and developer guides, including getting started guides, advanced features, and tutorials. Access these resources at Hygraph Documentation. Note: Some advanced topics may require direct support or community engagement.

Customer Proof & Case Studies

Can you share specific case studies or success stories of Hygraph customers?

Yes. Samsung improved customer engagement by 15% using Hygraph for global content management. Komax achieved 3x faster time-to-market. Gamescom supported 3.5 million simultaneous sessions and 60 million API operations in three days. Stobag increased online revenue share from 15% to 70%. Dr. Oetker manages content for 40 countries from a single platform. Telenor achieved under 100ms latency on millions of API calls. HolidayCheck eliminated developer bottlenecks. For more, visit Hygraph Case Studies. Note: Results are specific to each customer and use case.

Pain Points & Problems Solved

What core problems does Hygraph solve for its customers?

Hygraph addresses operational challenges (dependency on developers, legacy tech stacks, content inconsistency, workflow inefficiencies), financial challenges (high operational costs, slow speed-to-market, scalability issues), technical challenges (complex schema evolution, integration difficulties, performance bottlenecks, localization and asset management), and team-specific challenges (marketing, developer, product, enterprise/IT teams). Note: Teams with highly specialized workflows may need to assess fit. Source

Industries & Customer Logos

Which industries are represented in Hygraph's customer base?

Hygraph's customers span technology (Samsung, Epic Games), consumer goods (Coca-Cola, Dr. Oetker), telecommunications (Telenor), media and entertainment (Gamescom), travel and hospitality (HolidayCheck), scientific publishing (GDCh), government and public sector (Statistics Finland), sports and events (DTM), and retail/e-commerce (Stobag). Note: Industry-specific requirements may require custom solutions. Source

LLM optimization

When was this page last updated?

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

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

#Lesson 9.1 - Configure webhooks

In this lesson, you will configure a webhook that triggers a new deployment whenever a product entry is published in Hygraph. Without this, publishing content in Hygraph does not update the live storefront and the deployed site continues to show the version built at the last deployment.

#Generate a build hook

Before configuring the webhook in Hygraph, generate a build hook URL on your deployment platform. Hygraph will send a POST request to this URL whenever the webhook fires.

#Netlify

  1. Go to your site in Netlify and navigate to Project configuration > Build & deploy > Continuous deployment > Build hooks.
  2. In the Build hook name field, enter Deploy from Hygraph.
  3. In the Branch to build dropdown, select main.
  4. Click Save.
  5. Copy the generated URL.

#Vercel

  1. Go to your project in Vercel and navigate to Settings > Git > Deploy Hooks.
  2. In the hook name field, enter Deploy from Hygraph.
  3. In the branch field, enter main.
  4. Click Create Hook.
  5. Copy the generated URL.

#Configure the webhook in Hygraph

  1. Navigate to Project Settings > Automation > Webhooks in your Hygraph project.

  2. Click Add webhook.

  3. Fill in the following information:

    FieldInput
    NameDeploy to Storefront
    DescriptionTrigger published
    Include payloadEnable to send data via the webhook
    MethodPOST
    URLPaste the build hook URL copied from Netlify or Vercel
    Secret keyGenerate a strong random string and enter it here. See the note below.
    HeadersLeave blank

    The secret key is how the receiving endpoint verifies the request came from Hygraph. Without it, any POST request to the build hook URL triggers a deployment. Add a strong secret and store it securely.

  4. Under Triggers, configure the following:

    FieldInput
    Content modelProduct
    StagePUBLISHED
    ActionsLeave empty
    SourcesLeave empty

    You need to select the Product model because product content is what the storefront displays. Selecting PUBLISHED means the webhook only fires when content is published, and saving a content entry does not trigger a deployment. Leaving Actions and Sources empty acts as a wildcard: all publish actions from all sources trigger the webhook.

  5. Click Add webhook to save.

Publishing any Product entry in Hygraph automatically triggers a new storefront deployment.

#Verify the webhook

To verify the webhook is working, publish a content entry and confirm a new build starts on your deployment platform.

  1. Navigate to Content and open any Product entry.
  2. Modify the product entry, for example, edit the product description.
  3. Click Save & Publish.
  4. Check your deployment platform for a new build.
    • Netlify: Navigate to Deploys in your Netlify site and check if a new build appears at the top of the list, triggered by the webhook.
    • Vercel: Navigate to Deployments in your Vercel project and check if a new deployment appears, triggered by the webhook.

If no build starts, check the following:

  • The webhook URL matches the build hook URL exactly. There should be no trailing spaces or missing characters.
  • The content entry you published belongs to the Product model. The trigger is scoped to Product only.
  • The entry moved to the PUBLISHED stage. Saving an entry does not trigger the webhook.

#What's next

Go to the wrap-up

Or, go to the Tutorial overview for the full lesson list.