What You Can Do
Discovery
List and describe Drupal resource types — nodes, blocks, paragraphs, media, taxonomy — with field shapes and worked examples so the agent never guesses field names.
Search and read
Find entities by title, path alias, UUID, or page-only filters. Read a full entity with relationship resolution, body field shapes, and stored snapshots.
Authoring
Create new entities, update fields (including formatted text with value/format preservation), and delete entities. Multi-value, relationship, and reference fields stay JSON:API-shaped.
Media
List and read media entities. Upload new media (images, documents) and reference them in content payloads.
Bulk content push
Push a staged directory of payloads for relationship-heavy migrations where dependent entities must be created in order.
Migration mode
A dedicated content-migration workflow enforcing 1:1 source preservation, source-inventory files, asset upload before referencing, and rendered-page QA before completion.
Prerequisites
- Admin access to your Drupal site to enable modules and create credentials
- Drupal’s JSON:API module enabled (ships as core in Drupal 10/11)
- A Gradial organization Administrator role to complete setup
How to Connect
Prepare your Drupal site
Make sure JSON:API is enabled in Drupal (Extend → JSON:API). Drupal 10/11 ships it as a core module.Then choose the auth method that fits your site:Basic (simplest)
- Enable Drupal core’s Basic Auth module.
- Create a dedicated editor/admin user for Gradial with JSON:API access permissions for the bundles you want to author.
- Note the username and password.
- If your site uses a custom auth module (e.g.,
key_auth, JWT, an SSO header, or a CDN-issued token), generate a token scoped to the Gradial editor account. - Note the token, header name, and prefix.
Add the integration in Gradial
- In Gradial, go to Settings → Integrations.
- Find Drupal and click + Add.
- Fill in the connection details:
| Field | Value |
|---|---|
| Integration Name | A display name (e.g., United Rentals NL) |
| Drupal Base URL | Your site’s origin — the JSON:API root (e.g., https://drupal-united-rentals.ddev.site) |
| Authentication Method | Basic, API Key Header, or Custom Headers |
| Preview Base URL (optional) | If rendered pages are served from a different host than the JSON:API root |
- Click Connect to validate. Gradial probes JSON:API, lists available resource types, and surfaces them so you can confirm which types should be treated as pages.
- Click Save.
How It Fits Into Broader Workflows
| Use case | How to use it |
|---|---|
| Content authoring | Author Drupal pages and components from the same Gradial thread that produced the brief, copy, or designs |
| Design-system migrations | Remap source pages onto a customer’s Drupal component model while preserving copy, imagery, hierarchy, links, and CTAs 1:1 |
| Asset upload | Upload source assets into Drupal media before referencing them in pages so the destination site stays self-contained |
| Rendered-page QA | Use Gradial preview to QA the actual rendered Drupal page (not just JSON), gating completion on rendered-page checks |
- Capture the source page (live HTML, screenshots, or export) into a source inventory listing sections, copy, CTAs, images, and downloads.
- Discover the target model by listing and describing the target content types.
- Upload source images, capturing the returned media UUIDs.
- Stage the new entity payload and create the page.
- Re-read the entity and inspect the snapshot and preview; iterate on field mappings until rendered-page QA passes.
- Publish (or keep in draft) and hand the preview URL back to the requester.