mutation

Generate GraphQL mutations for Crystallize catalog, customer, cart, and order operations.

4|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/CrystallizeAPI/ai --skill mutation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mutation
Source: https://github.com/CrystallizeAPI/ai/tree/main/use-crystallize/skills/mutation
Command: npx skills add https://github.com/CrystallizeAPI/ai --skill mutation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The mutation skill helps you create, update, and manage Crystallize catalog, customer, cart, and order data without hand-writing low-level GraphQL write flows.

Core Features & Use Cases

  • Create and manage catalogue items: build products, documents, and folders, update components/fields, manage variants/SKUs, and publish or unpublish items.
  • Handle customers and orders: create/update customers, create orders from carts or directly, record payments, and track fulfillment pipeline stages.
  • Drive the checkout lifecycle: hydrate carts, modify cart items, set customer and addresses, place carts, and convert carts to order intents for downstream processing.

Use case example: You need to add a new product with variants, update its description and gallery images, publish it, and then place an order from a customer’s cart while recording payment and fulfillment stage changes.

Quick Start

Use this skill to generate the exact GraphQL mutations (Core API for catalogue/customer writes and Shop API for cart/order writes) needed to publish an updated product and create an order from a placed cart.

Frequently Asked Questions about mutation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Crystallize orders and update product catalogs using GraphQL mutations?

Crystallize GraphQL mutations automate write operations for catalog, customer, cart, and order lifecycles. You generate mutations to create products, manage variants, hydrate carts, and place orders with payments using tenant-scoped authentication via Core API or Shop API endpoints.

What's the best way to automate Crystallize checkout flows and cart lifecycle management?

Automate Crystallize checkout by generating GraphQL mutations to hydrate carts, modify cart items, set customer addresses, and convert carts to order intents. Use Shop API endpoints for cart and order writes, including variable placeholders and expected response shapes for reliable integration.

Do I need separate API endpoints for Crystallize catalog management versus checkout and order creation?

Yes, Crystallize requires correct endpoint selection: use the Core API for catalog and customer writes like creating products or updating components, and the Shop API for cart and order writes like placing carts and recording payments. Tenant-scoped authentication is required for both endpoints.

Can I publish and unpublish Crystallize product variants with GraphQL mutations?

Yes, you can generate GraphQL mutations to manage Crystallize product variants and SKUs, including publishing and unpublishing items. The mutations cover creating products, documents, folders, updating components and fields, and managing the full catalog lifecycle with structured variable placeholders.

How does recording payments and fulfillment pipeline stages work with Crystallize GraphQL mutations?

Crystallize GraphQL mutations handle order processing by creating orders from carts or directly, recording payments, and tracking fulfillment pipeline stages. You generate structured mutations with variable placeholders and expected response shapes targeting the Shop API endpoint for reliable order management integration.

What are the limitations when using GraphQL mutations for Crystallize catalog and order management?

Crystallize GraphQL mutations require tenant-scoped authentication and strict Core API versus Shop API endpoint selection. Catalog and customer writes go through Core API while cart and order operations use Shop API, and output formatting must include mutation structure, variable placeholders, and expected response shapes for reliable integration.