How to Set Up Contentful Webhook Notifications with Webhookify

Published Feb 21 202610 min read
Contentful webhook setup with Webhookify

Contentful is the leading headless CMS platform used by enterprises and development teams to manage and deliver content across websites, mobile apps, and digital experiences. Every time an entry is created, published, updated, or archived, and every time an asset is uploaded or removed, Contentful can fire a webhook event. For content teams, missing these events can mean publishing outdated content, failing to trigger static site rebuilds, or losing track of editorial workflow changes. With Webhookify, you can instantly receive human-readable notifications for every Contentful webhook event on Telegram, Discord, Slack, Email, or your mobile device, keeping your editorial and development teams perfectly synchronized.

This guide walks you through connecting Contentful webhooks to Webhookify, from creating your endpoint to receiving your first real-time content management alert. Whether you are an editorial team managing a multi-site content pipeline or a developer maintaining a Jamstack site that rebuilds on content changes, this setup takes less than 15 minutes and adds real-time visibility to your content operations.

Why Monitor Contentful Webhooks with Webhookify?

  • Instant Content Awareness: Know the moment an entry is published, updated, or unpublished in your Contentful space. Webhookify delivers AI-summarized alerts within seconds, enabling editors and developers to react to content changes in real time.

  • Multi-Channel Delivery: Route Contentful alerts wherever your team works. Send publication events to a Slack editorial channel, asset upload notifications to a Discord design channel, and content archival alerts to Email -- all from a single Webhookify endpoint.

  • AI-Powered Summaries: Instead of parsing Contentful's JSON webhook payloads, Webhookify transforms content events into plain-English summaries like "Sarah published the entry 'Spring Product Launch' (Blog Post) in the production environment."

  • Editorial Workflow Visibility: Track content as it moves through your editorial pipeline -- from draft creation to review, publication, and archival. Non-technical stakeholders can stay informed through their preferred notification channel without needing Contentful access.

  • Complete Content Audit Trail: Every webhook Contentful sends is logged with full headers and payload data. This creates a searchable history of all content changes for compliance, auditing, and tracking who published what and when.

Prerequisites

  1. A Contentful account with at least one space (free Community tier available at contentful.com)
  2. A Webhookify account (sign up free at webhookify.app)
  3. At least one notification channel configured (Telegram, Discord, Slack, Email, or mobile push)
  4. Admin access to your Contentful space for managing webhooks

Step-by-Step Setup Guide

1

Create a Webhookify Endpoint

Start by logging into your Webhookify dashboard at webhookify.app. If you do not have an account yet, sign up -- the free tier is all you need to get started.

Once inside the dashboard, click the "Create Endpoint" button. Webhookify will generate a unique webhook URL that looks something like this:

https://hook.webhookify.app/wh/abc123xyz789

Copy this URL and keep it handy. This is the URL you will paste into Contentful's webhook configuration. Each endpoint has its own event log, so you can create separate endpoints for different Contentful spaces or environments.

Give your endpoint a descriptive name like "Contentful Production Content" or "Contentful Blog Pipeline" so you can easily identify it later in your dashboard.

2

Configure Your Notification Channel

Before connecting Contentful, make sure you have at least one notification channel set up in Webhookify. Navigate to the Settings or Notifications section in your Webhookify dashboard.

For Telegram: Click "Connect Telegram" and follow the bot authorization flow. This is ideal for editors and content managers who want instant publication alerts on their phone.

For Discord: Click "Connect Discord" and authorize the Webhookify bot to post in your selected server and channel. Choose a dedicated channel like #content-updates or #cms-activity to keep content notifications organized.

For Slack: Click "Connect Slack" and complete the OAuth flow. Select the workspace and channel where you want Contentful alerts to appear. A channel like #editorial or #content-pipeline works well for content teams.

For Email: Enter the email address where you want to receive content notifications. You can add multiple addresses to notify editors, reviewers, and stakeholders simultaneously.

For Mobile Push: Download the Webhookify app from the App Store or Google Play. Sign in with your account credentials. Enable push notifications when prompted so you receive instant alerts for every content change in your Contentful space.

3

Add Your Webhookify URL in Contentful

Log into the Contentful Web App and navigate to the space you want to monitor.

  1. Go to Settings in the top navigation bar.
  2. Click "Webhooks" in the settings menu.
  3. Click the "Add Webhook" button in the top right.
  4. Fill in the webhook details:
    • Name: Give it a descriptive name like "Webhookify Notifications"
    • URL: Paste your Webhookify URL:
https://hook.webhookify.app/wh/abc123xyz789

  1. Under Triggers, select the events you want to monitor. Contentful organizes triggers by entity type:

    Entry events (content entries):

    • Create, Save, Auto save, Archive, Unarchive, Publish, Unpublish, Delete

    Asset events (media files):

    • Create, Save, Archive, Unarchive, Publish, Unpublish, Delete

    Content Type events (content models):

    • Create, Save, Delete

  2. Optionally, add Filters to narrow down which content changes trigger the webhook (e.g., only entries of a specific content type or in a specific environment).

  3. Click "Save" to create the webhook.

Contentful will now send webhook events to your Webhookify URL whenever the selected content changes occur.

4

Configure Event Filters and Alert Preferences

Back in your Webhookify dashboard, click on your Contentful endpoint to fine-tune notification delivery.

The most important Contentful events to monitor include:

  • Entry.create -- A new content entry was created
  • Entry.save -- A content entry was saved (draft updated)
  • Entry.auto_save -- A content entry was auto-saved
  • Entry.archive -- A content entry was archived
  • Entry.publish -- A content entry was published (live)
  • Entry.unpublish -- A content entry was unpublished (taken offline)
  • Asset.create -- A new media asset was uploaded
  • Asset.publish -- A media asset was published

For most content teams, focus on Entry.publish and Entry.unpublish for production content monitoring. Add Entry.create if you want to track when new drafts are started.

Configure notification routing in Webhookify:

  • Route Entry.publish events to a #content-published Slack channel
  • Send Entry.unpublish events to Email for editorial review
  • Route Asset.create events to a Discord channel for the design team
  • Filter out Entry.auto_save events to reduce noise
5

Test Your Configuration

Contentful provides a built-in webhook testing tool. In the Contentful Web App, go to Settings > Webhooks, click on the webhook you just created, and you will see the Activity Log tab.

To test with a real event, create or publish a content entry in your space. Within seconds, you should receive a notification on your configured channels.

You can also check the webhook activity log in Contentful to see the delivery status of each webhook call. Green checkmarks indicate successful delivery, while red marks indicate failures.

Check your Webhookify dashboard to see the event logged with its full payload. Contentful webhooks include details like the entry title, content type, locale, environment, and the user who made the change.

If you do not receive a notification:

  • Check the Contentful webhook activity log for delivery errors
  • Verify the trigger events are correctly selected
  • Confirm your Webhookify notification channel is connected and active

Contentful Webhook Events You Can Monitor

Contentful EventDescription
Entry.createTriggered when Entry create occurs
Entry.saveTriggered when Entry save occurs
Entry.auto_saveTriggered when Entry auto save occurs
Entry.archiveTriggered when Entry archive occurs
Entry.unarchiveTriggered when Entry unarchive occurs
Entry.publishTriggered when Entry publish occurs
Entry.unpublishTriggered when Entry unpublish occurs
Entry.deleteTriggered when Entry delete occurs
Asset.createTriggered when Asset create occurs
Asset.saveTriggered when Asset save occurs
Asset.archiveTriggered when Asset archive occurs
Asset.publishTriggered when Asset publish occurs
Asset.unpublishTriggered when Asset unpublish occurs
Asset.deleteTriggered when Asset delete occurs
ContentType.createTriggered when ContentType create occurs
ContentType.saveTriggered when ContentType save occurs
ContentType.deleteTriggered when ContentType delete occurs

Real-World Use Cases

  • Editorial Pipeline Monitoring: A media company uses Contentful to manage articles across multiple publications. When an editor publishes an article, the marketing team receives a Slack notification with the article title, author, and publication. This triggers their social media promotion workflow within minutes of publication rather than relying on manual handoffs.

  • Static Site Rebuild Verification: A development team using a Jamstack architecture monitors Entry.publish events via Webhookify alongside their build webhook. While the build webhook triggers the site rebuild, the Webhookify notification confirms to the content team that the publish event was received. If they see the notification but the site does not update, they know to investigate the build pipeline.

  • Asset Management Tracking: A design team uploads images and videos to Contentful for use across web and mobile applications. They receive Discord notifications for Asset.create and Asset.publish events, giving them real-time visibility into which assets are being added to the content space and by whom.

  • Content Compliance Monitoring: A legal team at an enterprise company monitors Entry.unpublish events via Email. When content is taken offline, they are immediately alerted and can verify that the removal was intentional and compliant with content governance policies.

Example Notification

Here is what a typical Webhookify notification looks like when a Contentful entry is published:

New Webhook Event Received

Source: Contentful
Event: Entry.publish
Endpoint: Contentful Production Content

AI Summary:
Sarah published the entry "Spring 2026 Product Launch
Announcement" (content type: Blog Post) in the master
environment. The entry is in English (en-US) locale
and includes 3 linked assets. Space: Marketing Website.

Timestamp: 2026-02-21T10:55:33Z

View full payload in Webhookify Dashboard

Troubleshooting

  1. Webhook not firing after content change: Verify the webhook is active in Contentful Settings > Webhooks. Check that the correct trigger events are selected. If you added filters (e.g., specific content type or environment), ensure your content change matches those filter criteria.

  2. Too many notifications from auto_save events: Contentful fires Entry.auto_save events frequently as editors type. If this creates too much noise, remove the auto_save trigger from your Contentful webhook configuration or use Webhookify's notification rules to suppress these events.

  3. Webhook delivery failures in Contentful: Check the webhook activity log in Contentful for error details. Common causes include incorrect URL formatting, network timeouts, or the webhook being disabled. Contentful retries failed deliveries, but persistent failures will cause the webhook to be deactivated.

  4. Missing content details in notifications: Contentful webhooks include the entry metadata and sys information by default. To include the full entry fields in the payload, ensure the webhook's payload configuration includes content fields. You can customize the payload template in the Contentful webhook settings.

  5. Notifications for the wrong environment: If you use multiple Contentful environments (e.g., master and staging), make sure your webhook filters are set to the correct environment. Without filters, the webhook fires for all environments. Create separate Webhookify endpoints for each environment to keep events organized.

Use Contentful's webhook filters to limit notifications to specific content types. For example, set a filter for content type "Blog Post" so you only receive alerts when blog articles are published, not when every minor content entry is updated. This dramatically reduces noise while ensuring you never miss an important publication.

Never Miss a Content Publish Again

Set up real-time Contentful webhook notifications in under 15 minutes. Get instant alerts for content creation, publication, and updates on Telegram, Discord, Slack, or your phone.

Get Started Free

Related Articles

Frequently Asked Questions

How to Set Up Contentful Webhook Notifications with Webhookify - Webhookify | Webhookify