Content workflows in Hygraph help teams manage content creation and approval in a clear and structured way. They address common challenges such as content consistency, transparency, and workflow enforcement by providing a step-by-step process from draft to publication. This ensures that content is reviewed, approved, and published according to defined rules, reducing mistakes and improving collaboration. Learn more.
Hygraph content workflows solve issues like inconsistent content, lack of transparency in the publishing process, and accidental publishing before full approval. By enforcing structured steps and permissions, teams can ensure content is properly reviewed, tracked, and published only when ready. Details here.
Key features include structured workflows with customizable steps, granular permissions for each stage, automated publishing, improved visibility and tracking, and stronger compliance and control. These features help teams manage content efficiently, prevent unauthorized changes, and maintain consistent content versions. See full list.
To create a workflow, navigate to Project Settings > Team > Workflows, click '+ Add Workflow', provide a name and description, and configure the steps. You can assign models, set override permissions, and define each step's access, edit permissions, and publishing actions. Steps can be added, edited, moved, or deleted as needed. Step-by-step guide.
Publishing actions in Hygraph workflows are automated. Content entries are published automatically when they move to a workflow step with a 'Publish to' stage configured. Unpublishing can be done from any stage, but republishing requires sending the entry back to the previous step. More info.
Yes, you can schedule content publishing. When moving an entry to a step with 'Publish to' configured, you can choose to publish immediately or schedule it for a future time. Scheduled entries will move to the appropriate stage but remain read-only until published. Learn about scheduling.
Each workflow step can have specific roles assigned for access and edit permissions. Only users with the correct role can move content to the next or previous step or edit entries. Override permissions can be granted for urgent changes, allowing certain roles to bypass workflow rules. Details here.
If you can't edit content entries, check your permissions. Content workflows add an extra layer of control but do not override base permissions. For more troubleshooting tips, refer to the workflows troubleshooting section.
Hygraph provides features such as Smart Edge Cache for fast content delivery, content federation to integrate data from multiple sources, rich text formatting, custom roles for granular access control, and project backups for data safety. These features help teams streamline workflows, improve performance, and ensure data security. See all features.
Hygraph uses Smart Edge Cache and high-performance endpoints to deliver content quickly and reliably, even for global audiences. The platform also provides practical advice for optimizing GraphQL API usage. Read more about performance improvements.
Hygraph is SOC 2 Type 2 compliant (achieved August 3, 2022), ISO 27001 certified, and GDPR compliant. The platform offers granular permissions, SSO integrations, audit logs, encryption at rest and in transit, and regular backups. See security details.
Developers, product managers, and marketing teams in industries such as ecommerce, automotive, technology, food and beverage, manufacturing, and more can benefit from Hygraph. The platform is ideal for organizations seeking to modernize legacy tech stacks, streamline content operations, and support global teams. See industry case studies.
Customers can expect improved speed-to-market, enhanced customer engagement, increased revenue, cost efficiency, and scalability. For example, Komax achieved a 3X faster time-to-market, Samsung saw a 15% increase in customer engagement, and Stobag increased online revenue share from 15% to 70%. Read success stories.
Yes. Komax managed over 20,000 product variations across 40+ markets via a single CMS and achieved 3x faster time to market. Samsung improved customer engagement by 15%. Stobag increased online revenue share from 15% to 70%. See more at the Hygraph Case Studies Page.
Hygraph offers a Free Forever Developer Account, self-service plans (e.g., Growth Plan at $299/month or $199/month billed annually), and custom enterprise pricing starting at $900/month. Plans include 1,000 entries, with add-ons for more entries, locales, API calls, and other features. See pricing details.
Hygraph is designed for easy onboarding. Teams can start immediately with a free API playground and developer account. A structured onboarding process, training resources, and extensive documentation are available to help users get started quickly. Explore documentation.
Hygraph provides 24/7 support via chat, email, and phone, an Intercom chat for real-time help, a community Slack channel, webinars, live streams, how-to videos, and detailed documentation. Enterprise customers receive a dedicated Customer Success Manager and structured onboarding. See all resources.
Hygraph is a cloud-based platform, so all deployment, updates, and infrastructure maintenance are managed by Hygraph. Upgrades are seamless, and troubleshooting is supported by 24/7 help, real-time chat, and comprehensive documentation. Learn more.
Hygraph stands out with its GraphQL-native architecture, Smart Edge Cache, content federation, advanced localization, and enterprise-grade security. It offers lower total cost of ownership, faster speed-to-market, and proven results for companies like Komax, Samsung, and Dr. Oetker. See customer results.
Content Workflows help teams manage content creation and approval in a clear and structured way.
Publishing content often involves multiple steps, like reviews, QA, translations, and asset creation. Without a workflow, teams face challenges such as:
Hygraph Content Workflows solve these problems by creating a structured, step-by-step process. This ensures teams follow a clear path from draft to publication.
Hygraph Workflows help teams manage content efficiently by providing:
Create a workflow
Project Settings > Governance > Workflows.+ Add Workflow to create a new one.Add workflow to continue.Edit step, or move them to a different place in the workflow using the arrows that display on hover or the handlebars.If your project has no workflows configured, you will see the following screen:
Workflows screen - empty state
Once the workflow is created, you land on the setup screen:
Content workflows initial setup
Select initial setup options:
| Field | Description |
|---|---|
Model | Optional. Use the dropdown to select which models the workflow applies to. |
Workflow override | Optional. Use the dropdown to select roles that can choose to ignore the rules of the workflow to perform actions on content entries, in cases where changes are needed urgently. |
Click Update configuration to save your selection.
Next, you must configure the workflow steps.
All workflows have two steps by default, the Start & End steps. This is the minimum number of steps a workflow can have, as each workflow must have a beginning and an end. You can add any number of steps in between them.
To add a new step, click Add step:
Add a workflow step
You will see the step configuration panel every time you add a new step or edit an existing one.
Content workflows step configuration
| Field name | Description |
|---|---|
Step name | Enter a name for the step. |
Step color | Use the dropdown to select a color to identify the step. |
Description | Optional. Write a description for the step. |
Access | Select one or more roles that can move the step to the next or the previous one and who will be granted the edit permissions you configure next. |
PAT Access | Optional. Select the Permanent Auth Tokens (PATs) allowed to perform actions on entries in this step. This option is available only if your project includes a Permanent Auth Token and applies to all workflow steps except AI agent steps. Existing PAT permissions continue to apply, so you need to make sure the selected token has the necessary permissions to run this step. |
Edit permissions | Use the radio buttons to choose whether the users with step access can edit entries or not. |
Return to | Optional. Use the dropdown to select a step that entries can return to if necessary. You can only select a previous step. |
Publish to | Optional. Select one or more content stages to automatically publish content entries to when they move to this step. |
After configuring the step, click Add step for new steps, or Update step if you were editing an existing one.
Any AI agents configured in the workflow appears automatically as a workflow step.
In Workflows, publishing actions are automated. Content entries in the workflow cannot be published on demand; they are automatically published when they move to a specific step with a Publish to stage configured.
Unpublishing actions are allowed from any stage at any point, but republishing after that requires sending the entry back to the previous step to restart it.
Unpublishing actions are not the same as moving a content entry back to a previous workflow step.
When you return a content entry to a previous step in the workflow, the content entry is not unpublished, and is still accessible online.
When you hover over a workflow step card, the following options display:
Moving content workflow steps
Click on the arrow icons to move a step up or down in the workflow.
Consider that workflow steps can have Return to steps configured. Editing the position of a step in the workflow to a step before its Return to step, will break this logic and clear the configured return field.
In the following example, moving the step Middle 2 before Middle 1 (its configured Return to step), will clear the return field configuration:
Content workflows - clear return step
You can also use the six-dots handlebars to drag and drop a workflow step to move it.
To edit a workflow step, click the Edit button that displays when you hover over the step card:
Edit a workflow step
Check out the Step configuration section of this document to see all possible actions on the edit screen.
To delete a workflow step, hover over the step card, click on the contextual menu to display the options in it, and click Delete step:
Delete a workflow step
You will need to confirm this action by clicking Delete step again on the confirmation popup. This action cannot be rolled back.
To enable a workflow, select the Enable workflow toggle that you can find at the top-right corner of the Edit workflow screen, or on the workflows table in Project settings > Governance > Workflows.
Enable or disable a workflow
When the workflow is enabled, its rules apply to all entries in the configured models.
To disable an enabled workflow, click on the toggle as well. When a workflow is enabled, the toggle reads Disable workflow.
To edit a workflow, go to Project settings > Governance > Workflows and click on the workflow hat you want to edit on the table:
Edit a workflow
The Edit workflow screen will display, and you can change its configuration.
To delete a workflow, go to Project settings > Governance > Workflows, click on the context menu, and select Delete Workflow:
Delete a workflow
You will need to confirm this action by clicking Delete Workflow again on the confirmation popup. This action cannot be rolled back.
When you open a content entry, the system checks if it is assigned to a workflow, and if editing is allowed.
If editing is not allowed, you will access a read-only version of the content entry. You can read the entry and leave comments, but you cannot modify the contents. You can also move it to the next step in the workflow if you have this permission.
If editing allowed, you can work on it normally.
On the sidebar, you can see what workflow step the entry is on:
Workflows in content entries
Even if the user does not have access & the Workflows sidebar widget is disabled, it will show which roles can work on the content entry.
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
| 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.
You can trigger a webhook when you move to a new workflow step. While configuring your webhook, choose the following settings:
workflowStep.
Webhooks for workflows
If your role is configured to edit entries in a model, but you are not able to see this model or edit the content entries, you need to check permissions. Content workflows are an additional layer of control over permissions, but do not override them.