Craft CMS integration
No native Craft CMS connector, here is what does work.
We save entries into your Craft sections through GraphQL mutations, with post dates for scheduling.
How it works
Craft CMS exposes write access through GraphQL save mutations, one per entry type, authenticated with a schema bearer token. We create entries with the enabled flag controlling draft versus live state, and we set postDate to schedule when an entry goes live. Section and entry-type mapping happens at setup, because every Craft site structures its content differently.
Two requirements come from Craft itself: mutations need the Pro edition, and mutation scopes must be enabled on your GraphQL schema by the site owner, since they are off by default. We check both at connection time and give you a plain message and a short setup guide if either is missing, rather than failing with a cryptic GraphQL error.
Best forCraft Pro sites whose developers want structured entries delivered into existing sections without manual entry work.
Setup, step by step
- Confirm your site runs Craft Pro, since GraphQL mutations require the Pro edition.
- In Craft's GraphQL settings, create or choose a schema and enable the save mutation scopes for your target sections.
- Generate a token for that schema and add it to SearchHandled's Craft connector along with your GraphQL endpoint URL.
- Map your sections, entry types, and fields to our content structure during setup.
- Run the connection test, which saves and deletes a disabled test entry to verify the scopes work.
Best practices
Scope the schema to what we need
Enable mutation scopes only for the sections we publish into. Craft's per-schema scoping is a good security model, and a narrow token limits what any integration can touch.
Use postDate for real scheduling
Craft treats a future postDate as a scheduled entry, so we set it rather than holding content back ourselves. Your entries appear in Craft's own queue where editors expect them.
Keep entries disabled until approved
The enabled flag is Craft's draft switch. Our default is to save entries disabled so your team reviews them in the control panel, then we flip them on at approval.
Tell us when sections change
Our mapping is bound to your sections and entry types. If a developer renames a section handle or restructures fields, reconnect the mapping so saves keep landing in the right place.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
GraphQL mutations require Craft Pro
Sites on the Solo edition cannot use GraphQL mutations at all, so programmatic publishing is unavailable.
How we handle itWe detect the edition at connect time and show a plain message explaining the Pro requirement instead of a failing mutation, so you know the constraint before setup effort is spent.
craftcms.com
Mutation scopes are off by default
Even on Pro, a schema token cannot save entries until the site owner enables mutation scopes on that schema, and the default is everything off.
How we handle itOur connection test detects missing scopes and walks you through enabling exactly the save mutations we need, section by section.
craftcms.com
Section and entry-type structure varies per site
Every Craft site defines its own sections, entry types, and fields, so there is no universal payload that fits all installs.
How we handle itWe map your sections and fields at setup and validate a test entry against them, so mismatches surface during onboarding rather than on publish day.
craftcms.com
Questions teams ask
- Does this work on Craft Solo?
No. GraphQL mutations require the Pro edition, and we detect this at connect time. On Solo, the fallback is our HTML export, which your team pastes into the control panel.
- Can SearchHandled schedule entries in Craft?
Yes. We set postDate on the entry, and Craft treats a future date as scheduled. The entry shows in Craft the same way as one scheduled by an editor.
- What access does the token actually have?
Only what the schema's scopes grant. We ask you to enable save mutations for the target sections and nothing else, so the token cannot touch users, settings, or unrelated content.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Craft CMS matters moves it up the rollout.