Content workflows in Hygraph help teams manage content creation and approval through a clear, structured process. They guide content from draft to publication, ensuring steps like reviews, QA, translations, and asset creation are followed. This reduces inconsistent content, increases transparency, and minimizes publishing errors. Learn more in the official guide.
When you open a content entry in Hygraph, the system checks if it is assigned to a workflow and whether editing is allowed. If editing is not allowed, you access a read-only version but can leave comments and move the entry to the next workflow step if permitted. If editing is allowed, you can work on the entry normally. The sidebar displays the current workflow step and which roles can work on the entry. See details in the documentation.
Depending on your role and permissions, you may see workflow actions such as Return to (returns the entry to a previous step), Move forward to (moves the entry to the next step), and Override workflow for this entry (allows you to bypass the workflow if you have override permission). Read more about workflow actions.
When a content entry moves into a step with Publish to configured, it is automatically published to the designated stage (e.g., QA or PUBLISHED). You can choose to publish immediately or schedule publishing for a future date. If scheduling, the entry becomes read-only until published, unless you return it to a previous step. See scheduled publishing documentation.
Yes, if a workflow step is assigned to an AI agent, the agent automatically starts processing as soon as an entry moves into that step. This enables seamless automation of tasks within the workflow.
Hygraph is a GraphQL-native Headless CMS that empowers businesses to build, manage, and deliver digital experiences at scale. Key capabilities include operational efficiency (eliminating developer dependency, streamlining workflows), financial benefits (reducing costs, accelerating speed-to-market), technical advantages (GraphQL-native architecture, content federation), and unique features like Smart Edge Cache, custom roles, rich text management, and project backups. Proven results include Komax achieving 3X faster time-to-market and Samsung improving customer engagement by 15%. See customer stories.
Hygraph solves operational inefficiencies by providing a user-friendly interface, reducing developer dependency, and supporting modern workflows. It addresses financial challenges by lowering operational costs and accelerating speed-to-market. Technical issues are resolved through simplified schema evolution, robust GraphQL APIs, Smart Edge Cache for performance, and enhanced localization and asset management. See related KPIs.
Hygraph delivers exceptional performance through Smart Edge Cache for faster content delivery, high-performance endpoints for reliability and speed, and practical advice for optimizing GraphQL API usage. These features support high-traffic, global audiences. Read more about endpoint improvements.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications ensure enhanced security and adherence to international standards. See security features.
Hygraph offers granular permissions, SSO integrations, audit logs, encryption at rest and in transit, regular backups, and enterprise-grade compliance features like dedicated hosting and custom SLAs. Security issues can be reported, and a public security and compliance report is available. View the security report.
Hygraph is ideal for developers, product managers, and marketing teams in industries such as ecommerce, automotive, technology, food and beverage, and manufacturing. It suits organizations modernizing legacy tech stacks, global enterprises needing localization, asset management, and content federation, and any business aiming to deliver exceptional digital experiences. See customer stories.
Komax achieved a 3X faster time-to-market, Autoweb saw a 20% increase in website monetization, Samsung improved customer engagement by 15%, and Stobag increased online revenue share from 15% to 70%. Explore more customer stories.
Hygraph offers a free API playground and a free forever developer account for immediate exploration. For larger projects, you can request a demo. The structured onboarding process includes introduction calls, account provisioning, business and technical kickoffs, and content schema setup. Training resources (webinars, live streams, how-to videos) and extensive documentation are available. Access documentation.
Implementation time varies by project scope. For example, Top Villas launched a new project within 2 months from initial contact, and Si Vale met aggressive deadlines during their initial phase. The onboarding process is designed for efficiency, with resources for both self-paced and guided adoption. See Top Villas case study.
Hygraph provides a structured onboarding process, training resources (webinars, live streams, how-to videos), extensive documentation, 24/7 support via chat, email, and phone, Intercom chat for real-time troubleshooting, a community Slack channel, and dedicated Customer Success Managers for enterprise customers. Access documentation.
Hygraph is a cloud-based platform, so all deployment, updates, security, and infrastructure maintenance are managed by Hygraph. Upgrades are seamless, with new features and improvements integrated automatically. Troubleshooting is supported by 24/7 support, real-time chat, extensive documentation, and a community Slack channel. Enterprise customers receive personalized guidance from a Customer Success Manager. Learn more.
Key metrics include time saved on content updates, number of updates made without developer intervention, system uptime, speed of deployment, content consistency across regions, user satisfaction scores, reduction in operational costs, ROI on CMS investment, time to market for new products, maintenance costs, scalability metrics, and performance during peak usage. Read more about CMS KPIs.
As an Editor you are not likely to configure Content Workflows, but you may have to work con content that follows a specific workflow. This document teaches you how to work with this feature.
Content workflows in Hygraph help teams manage content creation and approval through a clear, structured process.
Publishing often involves steps like reviews, QA, translations, and asset creation. Without a workflow, teams can face issues such as inconsistent content, lack of transparency, and publishing errors. Content Workflows address these challenges by guiding content through an organized, step-by-step path from draft to publication.
When you open a content entry, the system checks if it is assigned to a workflow, and if editing is allowed:
On the sidebar, you can see what workflow step the entry is on. The sidebar always shows which roles can work on the content entry.
Workflows in content entries
If a workflow step is assigned to an AI agent, the agent automatically starts processing as soon as an entry moves into that step. This ensures tasks run seamlessly within the defined workflow.
If you have permission to move the entry to the next step in the workflow, the Move to button at the top-right of the screen will be enabled.
You can click Move to, to move the entry to the next step in the workflow, or click the arrow icon to display the workflow actions.
Content workflows - entry actions
You may see some or all of these workflow actions depending on your role & permissions:
| Workflow action | Description |
|---|---|
Return to | Select this option to return the content entry to its configured return step. This option is enabled only if the workflow step has a Return to step configured. |
Move forward to | Select this option to move the content entry to the next step in the workflow. |
Override workflow for this entry | Select this option to override the workflow for the entry. When you override the workflow, you can perform any actions, just as if there wasn't a workflow configured. This option is enabled only if you have override permission. |
If you move a content entry into a step with Publish to configured, the entry will automatically be published to the configured stage. You can publish entries to intermediate content stages such as QA, or to PUBLISHED.
When publishing an entry to the PUBLISHED stage, you will have the option to publish it right away or to schedule publishing.
This action publishes your content to the PUBLISHED stage, meaning it will be available online for others to consume. If your content entry contains unpublished assets or references, you will be prompted to publish those too.
Moving an entry to the next step & publishing at the same time is an atomic operation. This means both events will succeed or fail.
If you select scheduled publishing, the side sheet will open for you to schedule publication of the content entry.
When you schedule an entry to publish to a stage, the workflow will move it to that stage but since publishing is scheduled in the future, it will not be published right away. If you open the content entry at this time, it will display as read-only.
In order to avoid workflow inconsistencies, the only way to edit this entry is to return it to the previous step, if you have the permission.
Check out our scheduled publishing docs to learn how to schedule single entries or add them to a release.