Working with Contentful?

Contentful space tangled or webhooks dropping? We sort it out.

Contentful is a strong CMS when the content model is deliberate and a painful one when it has been grown by five different agencies. Most of the trouble we see is in the shape of the entries, the branching between spaces, and webhooks that fire into endpoints nobody owns anymore. We fix the model first and everything else gets easier.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

contentful-webhooks.log

still broken

What it is

Contentful at a glance

Contentful is a headless CMS founded in Berlin in 2013 by Sascha Konietzke and Paolo Negri. Instead of coupling content to a theme the way WordPress or Drupal do, it stores structured entries behind a REST and GraphQL API, and leaves the presentation to whichever front end you choose.

The platform is used heavily by enterprise marketing teams, large ecommerce sites and multi-brand publishers. It supports content types, references, assets, localisations, environments for staging content changes, and roles with fine-grained permissions. Pricing is plan-based with hard ceilings on API calls, records, locales, users and environments; overages are the single most common surprise on an invoice.

Type
Headless content management system, API-first
First released
2013
License
Proprietary SaaS, tiered plans
Maintained by
Contentful GmbH
Typically used for
Enterprise marketing sites, product catalogues, multi-brand content, localised sites powered by React, Next.js or Astro

The honest version

Contentful pros and cons

No technology is all upside. This is where Contentful earns its place and where it tends to cause trouble.

Where Contentful is strong

  • A clear structured-content modelContent types, references and validations give editors a set of forms rather than a free-text blob, which is exactly what large marketing teams need.
  • Delivery and preview APIs are separatePublished content comes from the Content Delivery API, drafts from the Content Preview API, and both are cached on a CDN so front ends feel fast.
  • Environments and environment aliasesEditors can preview a content schema change on a copy of the space before it lands on production, and aliases let the switch happen without changing application code.
  • Good localisation primitivesLocale fallbacks, per-field locale controls and import-export for translation vendors save a surprising amount of custom work on multi-market sites.
  • Role and team permissionsGranular roles on content types and environments mean editors in Germany cannot accidentally publish a US-only entry, which is a common ask from any brand above a certain size.
  • A healthy SDK ecosystemFirst-party clients for JavaScript, Python, Ruby, PHP, .NET and Java, plus a Rich Text renderer and a solid CLI for migrations.

Where Contentful bites

  • Plans have hard ceilingsAPI calls, records, locales, users, environments, roles are all capped by plan tier. Teams routinely bump into one of them months after launch and face an unexpected upgrade.
  • The content model is hard to change laterField type changes, required-field flips and reference restructures need migration scripts. Teams that never built migration muscle end up afraid to touch the model.
  • Rich Text is powerful and heavyThe JSON Rich Text format is strict and renders through a per-framework library. Custom marks and embedded entries require a renderer that needs maintenance.
  • Webhooks are at-least-onceReceivers must be idempotent, and silent failures are easy to miss. Several teams discover a dropped webhook only when an editor notices a missing preview.
  • Pricing is not cheapThe entry tier is reasonable and the enterprise tiers climb fast, particularly when API-call overages or content delivery usage are involved. Budgeting needs a close read of the plan.
  • Editor UX trade-offsThe editor is good but opinionated; teams coming from WordPress expect more flexibility in authoring and the structured model asks them to change habits.

Sound familiar?

Common Contentful problems we fix

The Contentful problems that bring people to us, and what you have once each one is fixed.

webhook target returned 500

Webhooks are quietly failing

Entry publishes stop firing the Netlify build, or ISR revalidation never runs, and no one notices for a week because the editor sees the entry go green inside Contentful.

Deliveries verified and alerted on

VersionMismatch: entry updated

Editors keep clobbering each other

Two editors on the same entry with no lock, or a script using the Management API without reading the current version first, writing over each other's changes.

Optimistic concurrency respected

monthly API calls: 2.4M of 2M

The plan is over on API calls

A front end calling the Content Delivery API per page view without caching, or a GraphQL query without persisted operations fanning out across the site.

Traffic back inside the plan

content model: 118 types, 11 unused

The content model has become a junk drawer

Content types added by past agencies that nobody uses, fields renamed but never removed, and reference chains that reach five entries deep for no good reason.

Model tidy, documented and tested

Environment alias: deleted env

Environment aliases point at nothing

Someone deleted the environment master was aliased to, or the alias was never updated after a migration, and production is serving stale content with no warning.

Aliases pointed at live environments

AssetFileUpload: processing failed

Asset uploads are failing

Images over the per-asset size limit, a storage integration that lost its credentials, or an upload from a browser blocked by a corporate proxy before it reaches Contentful.

Media pipeline back to green

Rich Text renderer crashes

Rich Text breaks on an unknown node

A new embedded entry type that the renderer does not know about, or a custom mark removed from the schema while entries still reference it, crashing the build.

Renderer matches the content types

locale fallback cycles

Locales fall back in circles

en-US falls back to en-GB which falls back to en-US, and a missing translation shows an empty string instead of a fallback value. Easy to miss until someone browses in the wrong region.

Fallback chain linear and tested

What we do

Contentful help, from rescue to steady state

Call us for one broken webhook, or hand us the whole space.

Rescue
Publishing stuck, previews blank, builds not triggering. We get content flowing again and only then look at the long-term fix.
Content model review
Content types audited against the site and the editor's workflow, unused fields retired, migrations scripted and run on a test environment first.
Webhooks and ISR
Reliable delivery to Netlify, Vercel or your own build, idempotent handlers, retries that are safe, and alerts when a delivery is dropped.
Migrations
Moving content in from WordPress, Drupal or a custom CMS with history preserved where it matters, and the first editor session planned.
Localisation
Locale strategy, fallbacks and translation vendor flow laid out so editors and translators are not fighting the tool.
Managed Tech
Steady upkeep of the content model, ongoing monitoring of API call usage and plan headroom, and a person to call before the overage email arrives.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Contentful alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Contentful questions

Something else? Call+1 737 727 7327

Why are our Contentful webhooks silently failing?

Usually a receiver that returns 500 on one branch of its logic, a signing secret that drifted after a redeploy, or a firewall that started dropping Contentful's IP ranges. Contentful retries for a while and then gives up, and the editor never sees a warning. We instrument the receiver, verify signatures correctly, and alert on dropped deliveries.

Can you tidy up a Contentful content model that has grown out of control?

Yes, and it is one of the most common jobs we are handed. We inventory every content type and field against real site usage, identify the unused and the duplicate, and script migrations with the Contentful CLI so the clean-up is reversible. The front end is tested against the new model before anything is published.

Why did our Contentful bill jump this month?

Almost always API call overages, either because the front end stopped caching, a new GraphQL query is fanning out per request, or a build is hitting the Management API in a loop. We open the usage dashboard with you, name the top ten offenders, and make the obvious changes before anyone talks about upgrading the plan.

Should we pick Contentful, Sanity or Strapi?

Contentful fits large marketing teams who need roles, environments and enterprise contracts. Sanity fits developers who value the real-time editor and GROQ queries. Strapi fits teams who want to self-host and own the database. We will tell you which one matches your team before anything gets procured.

How do we migrate content from WordPress to Contentful?

We define the content model in Contentful first, map WordPress post types, taxonomies and custom fields onto it, then import through the Management API in batches with the original IDs preserved. Media is moved into Contentful's asset library, and redirects from the old permalinks are generated so nothing on the public side drops out of search.

How much does Contentful help cost?

The quote is free and comes with no obligation. Send the space name and the problem, and we return a written plan with a price before any content is touched.

Free estimate

Contentful giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.