A webhook in Hygraph is a feature that sends a signal or notification whenever a specific event occurs in your project, such as publishing content. This allows you to trigger automated actions, like rebuilding your frontend site, based on content changes. Learn more.
To configure a webhook in Hygraph, navigate to the Webhooks section of your project and click the Add button. Fill in the required fields such as Name, Description, Method (usually POST), URL (e.g., a Netlify build hook), and optional secret key. Select the triggers (e.g., Product model, PUBLISHED stage) and save. Step-by-step guide.
Required fields include Name, Description, Method (e.g., POST), URL, and Triggers (such as Content Model and Stage). You can also optionally include a secret key for payload signing and custom headers. Details here.
First, create a build hook in your Netlify site under Site configuration > Build & deploy > Continuous deployment > Build hooks. Copy the generated URL and paste it into the URL field of your Hygraph webhook. When you publish content, the webhook will trigger a Netlify rebuild. See instructions.
Yes, you can set up deployments to Vercel using Hygraph webhooks. Follow the step-by-step guide to configure your webhook for Vercel deployments.
The 'Include payload' option, when enabled, ensures that data is sent via the webhook. This allows the receiving service to process the content or event details sent from Hygraph. More info.
You can test your webhook by adding a new product content entry and publishing it. When you click 'Publish', the webhook will automatically trigger the connected service (e.g., Netlify) to rebuild your storefront. Testing steps.
A secret key is an optional field used to sign the payload of your webhook. It allows the receiving service to verify that the webhook request is genuine and originated from Hygraph, enhancing security. Learn more.
Yes, you can optionally configure custom headers by adding additional key-value pairs in the webhook setup. This can be useful for authentication or passing extra information to the receiving service. Details here.
The Hygraph-Netlify Integration allows you to install a button in the Hygraph sidebar of a content model for manual redeploys, along with a visual indicator of deployment status. This streamlines static deployments to Netlify. Integration guide.
Comprehensive technical documentation on Hygraph webhooks, including API reference and advanced use cases, is available at the Webhooks API Reference.
Yes, you can configure Hygraph webhooks to trigger based on specific content models (e.g., Product) and stages (e.g., PUBLISHED), allowing for granular automation tailored to your workflow. More info.
Yes, you can choose to limit webhook triggers by specifying actions and sources, or leave them blank to trigger on all actions and sources. This provides flexibility in automation. Details here.
After saving, your webhook appears on the main Webhooks screen in Hygraph. It will automatically trigger the configured action (e.g., deployment) when the specified event occurs. See example.
You can set up static deployments to Netlify by using the Hygraph-Netlify Integration, which adds a manual redeploy button and deployment status indicator to your content model sidebar. Integration guide.
Yes, by configuring your webhook to trigger on the Product model and the PUBLISHED stage, you can preview product entry drafts and automate deployments to your frontend. More info.
Webhooks automate the process of updating your frontend or other services whenever content is published, reducing manual steps and ensuring your site is always up to date. Learn more.
In Netlify, go to Site configuration > Build & deploy > Continuous deployment > Build hooks, and click 'Add a build hook'. Name your hook, select the branch, and save. Copy the URL and use it in your Hygraph webhook configuration. Step-by-step.
If you leave the Actions and Sources fields blank, the webhook will not be limited and will trigger on all actions and sources for the selected model and stage. More info.
Hygraph offers webhooks, robust GraphQL APIs, and integrations with platforms like Netlify and Vercel for automation. It also supports Digital Asset Management integrations (e.g., AWS S3, Cloudinary), custom SDKs, and a marketplace for pre-built apps. See all integrations.
Yes, Hygraph provides multiple APIs, including a Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. These APIs support querying, mutating, uploading assets, and managing project structure. API Reference.
Hygraph integrates with Digital Asset Management systems (e.g., Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), Adminix, Plasmic, and more. Developers can also build custom integrations via SDKs and APIs. Integration documentation.
Hygraph provides extensive technical documentation, including API references, guides on schema components, references, webhooks, and AI integrations. Access all resources at Hygraph Documentation.
Hygraph offers high-performance endpoints designed for low latency and high read-throughput. The platform actively measures GraphQL API performance and provides best practices for optimization. Performance details.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. It offers enterprise-grade security features like granular permissions, audit logs, SSO, encryption, and regular backups. Security details.
Hygraph provides robust localization features and integrates with leading asset management platforms, making it ideal for global teams managing content in multiple languages and formats. Localization guide.
Smart Edge Cache is a performance optimization feature that ensures faster content delivery by caching content at the edge, reducing latency for global audiences. Learn more.
Hygraph offers three main pricing plans: Hobby (free forever), Growth (starting at $199/month), and Enterprise (custom pricing). Each plan includes different features and support levels. See pricing details.
The Hobby plan is free forever and includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, 50MB per asset upload, live preview, and commenting workflow. More info.
The Growth plan starts at $199/month and includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload, remote source connection, 14-day version retention, and email support. See details.
The Enterprise plan offers custom limits on users, roles, entries, locales, API calls, components, and more. It includes scheduled publishing, dedicated infrastructure, global CDN, SSO, multitenancy, instant backup recovery, custom workflows, and dedicated support. Enterprise details.
Hygraph is designed for developers, product managers, content creators, marketing professionals, and solutions architects. It's suitable for enterprises, agencies, eCommerce, media, technology companies, and global brands. See case studies.
Industries include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agency, gaming, events, government, consumer electronics, engineering, and construction. Industry list.
Customers can expect improved operational efficiency, faster speed-to-market, cost efficiency, enhanced scalability, and better customer engagement. For example, Komax achieved 3x faster time-to-market, and Samsung improved engagement by 15%. See success stories.
Yes. Notable examples include Samsung (scalable API-first app), Dr. Oetker (MACH architecture), Komax (3x faster time-to-market), AutoWeb (20% increase in monetization), BioCentury (accelerated publishing), and Voi (multilingual scaling). Read case studies.
Hygraph addresses operational inefficiencies (developer dependency, legacy tech), financial challenges (high costs, slow launches), and technical issues (schema evolution, integration, performance, localization). See examples.
Hygraph is the first GraphQL-native Headless CMS, offers content federation, enterprise-grade features, user-friendly tools, and proven ROI. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report. See comparison.
Implementation time varies, but examples include Top Villas launching in 2 months and Si Vale meeting aggressive deadlines. Hygraph offers a free API playground, structured onboarding, and extensive documentation for quick adoption. See case study.
Customers praise Hygraph's intuitive UI, ease of setup, and ability for non-technical users to manage content independently. Some users note it can be complex for less technical users. See feedback.
Hygraph provides Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API, supporting a wide range of development and integration needs. API docs.
Hygraph offers webinars, live streams, how-to videos, extensive documentation, and a community Slack channel for support and guidance. Documentation | Slack
Hygraph provides a process for reporting security, confidentiality, integrity, and availability incidents, ensuring prompt response and resolution. Security process.
Hygraph offers shared or dedicated hosting in multiple regions, allowing compliance with local regulations and enterprise requirements. Hosting details.
You can start immediately with a free API playground and a free forever developer account. Hygraph provides structured onboarding, training resources, and community support for new users. Get started.
In this step of the tutorial you will learn how to configure a webhook.
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.
First, we're going to navigate to the Webhooks section of our project, and click on the Add button.
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. |
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.
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