What mutations are available for managing product entries in Hygraph?
Hygraph automatically generates five mutations for each model: createProduct, updateProduct, publishProduct, unpublishProduct, and deleteProduct. These mutations allow you to create, update, publish, unpublish, and delete product entries, covering the complete content lifecycle. Note: Mutations are model-specific and must be used according to your schema configuration. Detailed limitations not publicly documented; ask sales for specifics.
How do I verify that a mutation has successfully changed a product entry?
After performing a mutation (such as create, update, publish, unpublish, or delete), you should run a verification query to confirm the change took effect. This is considered best practice for any destructive or state-changing API operation. For example, after deleting a product, querying the products list should confirm the entry no longer exists. Note: Always verify after destructive operations to avoid data inconsistencies.
Features & Capabilities
What are the key features of Hygraph?
Hygraph offers a GraphQL-native architecture, content federation, marketer-friendly editorial UI, enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), Smart Edge Cache, localization workflows, Variants for personalization, AI Assist and AI Agents, and a high-performance CDN. These features enable precise data fetching, multi-channel content delivery, and efficient workflows for both technical and non-technical users. Note: Best fit for teams needing flexible schema modeling and global content delivery; teams requiring legacy CMS features may need to evaluate compatibility.
Does Hygraph support API access for content management?
Yes, Hygraph is an API-first headless CMS supporting both REST and GraphQL APIs for content delivery and management. Developers can integrate Hygraph with any frontend or application. For more details, see Hygraph API documentation. Note: API usage requires appropriate permissions and schema configuration.
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 product data management. For a full list, visit Hygraph Marketplace Apps. Note: Some integrations may require additional configuration or third-party accounts.
Technical Requirements & Documentation
Where can I find technical documentation and developer guides for Hygraph?
Hygraph offers comprehensive technical documentation, including getting started guides, advanced tutorials, and onboarding resources. Access these at Hygraph Docs. Note: Documentation is updated regularly; refer to the latest version for current features.
How easy is it to implement Hygraph and start using it?
Implementation timelines depend on project complexity. Simple use cases can be started within a few days, while complex projects may take longer. Hygraph provides pre-configured starter projects, structured onboarding, extensive documentation, training resources, and community support (Slack at slack.hygraph.com). Note: Implementation speed may vary based on team expertise and project requirements.
Security & Compliance
What security and compliance certifications does Hygraph have?
Hygraph is SOC 2 Type 2 certified (since August 2022), uses ISO 27001-certified providers and data centers, and is GDPR and CCPA compliant. Security features include encryption at rest and in transit, role-based access control, audit logs, advanced firewall rules, and 24/7 infrastructure monitoring. For more details, visit Hygraph Security Features. Note: Compliance requirements may vary by region; verify with your legal team for specific needs.
Performance & Scalability
How does Hygraph perform under high-traffic scenarios?
Hygraph's global CDN, region-based hosting, and Smart Edge Cache ensure fast and reliable content delivery. For example, Gamescom supported 3.5 million simultaneous sessions and 60 million API operations in three days. Telenor achieved under 100ms latency on millions of API calls. Note: Performance may depend on API usage patterns and hosting region selection.
Use Cases & Benefits
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 implementation and industry.
Who is the target audience for Hygraph?
Hygraph is designed for marketing and content teams, product managers, developers, engineers, and enterprise IT teams. It is suitable for industries such as technology, consumer goods, telecommunications, media, retail, e-commerce, travel, scientific publishing, government, sports, and events. Note: Teams with highly specialized legacy CMS requirements may need to assess compatibility.
What pain points does Hygraph address for its customers?
Hygraph addresses dependency on developers, legacy tech stack modernization, content inconsistency, workflow inefficiencies, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization challenges. Note: Some edge cases may require custom solutions; consult Hygraph support for specifics.
Customer Proof & Success Stories
Can you share specific case studies or success stories of Hygraph customers?
Yes. Samsung improved customer engagement by 15% using Hygraph. 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 customer-specific and may not be representative of all users.
Industries & Customer Logos
Which industries are represented in Hygraph's customer case studies?
Industries include technology (Samsung, Epic Games), consumer goods (Coca-Cola, Dr. Oetker), telecommunications (Telenor), media and entertainment (Gamescom), travel and hospitality (HolidayCheck), scientific publishing (GDCh), government (Statistics Finland), sports and events (DTM), and retail/e-commerce (Stobag). Note: Industry-specific requirements may vary; consult Hygraph for tailored solutions.
Who are some notable customers of Hygraph?
Notable customers include Samsung, Coca-Cola, Epic Games, Telenor, Dr. Oetker, Komax, Gamescom, and Stobag. These organizations use Hygraph for global content management, high-traffic operations, and scalable digital experiences. Note: Customer use cases vary; review case studies for detailed scenarios.
In this lesson, you will use mutations to create, update, publish, unpublish, and delete a product entry. The mutations follow a complete content lifecycle: create it, change it, publish it, unpublish it, remove it. After each destructive mutation, you will run a quick query to confirm the change took effect.
Running a verification query after a mutation is not just a tutorial step. It is the correct practice for any destructive or state-changing API operation.
Hygraph automatically generates five mutations for each model when it is created. For the Product model, those are createProduct, updateProduct, publishProduct, unpublishProduct, and deleteProduct. They are used here in lifecycle order.
This mutation creates a new product entry with a name, slug, price, product variant, related product, category assignment, and a placeholder image asset.
Mutation
Response
The mutation uses nested create blocks to configure the product variant and related products inline. The products connect uses plaid-shirt, one of the five core products from lesson 6.1. The productCategories field uses connect to link to an existing category entry rather than creating a new one.
Open the Content editor and navigate to the Product model. The new entry appears there in the DRAFT stage.
createProduct mutation result in the content editor
This mutation changes the productName of the entry created above. The where clause uses productSlug as the unique identifier because it was configured to be unique in lesson 1.2.
Mutation
Response
updateProduct mutation result
The updateProduct mutation works on any entry, not only newly created ones. To demonstrate, update the Black leather shoes entry:
Run this query to confirm the entry no longer exists.
Query
Response
Response varies by content
Your response reflects only the product entries you created. If you completed the additional practice in lesson 6.1, more entries will appear. The Black leather shoes entry may show the updated name "My black leather shoes" from the updateProduct mutation above.
The deleted entry does not appear. This verify-after-mutate pattern applies to any mutation in any project. Run a query immediately after a destructive operation to confirm the result.
The project now has a queryable API, published content, and a confirmed remote source connection. The next step is connecting a frontend to display this content in a storefront.
In this lesson, you will use mutations to create, update, publish, unpublish, and delete a product entry. The mutations follow a complete content lifecycle: create it, change it, publish it, unpublish it, remove it. After each destructive mutation, you will run a quick query to confirm the change took effect.
Running a verification query after a mutation is not just a tutorial step. It is the correct practice for any destructive or state-changing API operation.
Hygraph automatically generates five mutations for each model when it is created. For the Product model, those are createProduct, updateProduct, publishProduct, unpublishProduct, and deleteProduct. They are used here in lifecycle order.
This mutation creates a new product entry with a name, slug, price, product variant, related product, category assignment, and a placeholder image asset.
Mutation
Response
The mutation uses nested create blocks to configure the product variant and related products inline. The products connect uses plaid-shirt, one of the five core products from lesson 6.1. The productCategories field uses connect to link to an existing category entry rather than creating a new one.
Open the Content editor and navigate to the Product model. The new entry appears there in the DRAFT stage.
createProduct mutation result in the content editor
This mutation changes the productName of the entry created above. The where clause uses productSlug as the unique identifier because it was configured to be unique in lesson 1.2.
Mutation
Response
updateProduct mutation result
The updateProduct mutation works on any entry, not only newly created ones. To demonstrate, update the Black leather shoes entry:
Run this query to confirm the entry no longer exists.
Query
Response
Response varies by content
Your response reflects only the product entries you created. If you completed the additional practice in lesson 6.1, more entries will appear. The Black leather shoes entry may show the updated name "My black leather shoes" from the updateProduct mutation above.
The deleted entry does not appear. This verify-after-mutate pattern applies to any mutation in any project. Run a query immediately after a destructive operation to confirm the result.
The project now has a queryable API, published content, and a confirmed remote source connection. The next step is connecting a frontend to display this content in a storefront.
