The moment it happens

Tell Slack when a Contentful entry goes live

Each time an entry is published, your channel sees its title and content type straight away.

Runs: The moment it happens
Apps: Contentful
AI: Not needed
Access: content_management_manage

Send this to your assistant

Create a ClickRuntime automation: when an entry is published in my Contentful space, post its title and content type to #content in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Publishing in a headless CMS is silent. An editor presses Publish in Contentful, the entry goes to the API, and the front end updates, but nobody else on the team knows it happened. A product manager checks the site an hour later to see whether the launch copy is live, and support does not realise a new help article exists.

As soon as Contentful reports that an entry was published, this posts its title and content type to Slack. The team sees what went live and what kind of content it was, right when it happens.

Marketing, product and support teams that rely on content going live on time use it as a shared signal. The message is created from the Contentful publish event, so it appears only when an entry really goes live, and it names the content type so the team can see what kind of change it was.

What you get out of it

Confirm launches the moment content ships
When the campaign page publishes, the channel shows it. The launch owner no longer has to refresh the site and ask who published it. The launch owner sees the campaign page go live in the channel, and no longer has to refresh the site to find out.
Let support know about new articles
A help article announced in Slack can be linked in tickets right away. Customers get answers sooner because the support team knows they exist. A help article announced in Slack can be linked in tickets at once, so customers get answers sooner than before.
Catch accidental publishes fast
If an unfinished entry goes live by mistake, the post makes it visible within moments. Unpublishing quickly limits how many people see it. An unfinished entry published by mistake is visible within moments, and unpublishing it quickly limits how many people see it.
Show the team what editors are doing
A visible feed of published content keeps everyone aware of cadence. Managers can see whether the editorial calendar is being met. A feed of published content shows editorial cadence, and managers can tell whether the planned calendar is being met.
Create a time-stamped publishing record
Slack keeps a searchable history of what went live and when. It answers questions about when a change appeared on the site. Slack keeps a searchable history of what went live and when, which settles questions about when a change reached the site.

How it works

What happens, step by step

When an entry is published in Contentful, Contentful tells ClickRuntime straight away.
A message goes to your Slack channel with the entry's title and content type.
Each publish is posted once, so your team sees what went live without anyone sharing it.

Before it runs live

Connect Contentful
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Tell Slack when a Contentful entry goes livejust nowSucceeded

Slack · #contentPublished: Autumn product update (blogPost)

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Contentful steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

published_entry_alert.pyexample

from clickruntime import on_event, notify

@on_event
def handle(event):
    if not (event.header("X-Contentful-Topic") or "").endswith("Entry.publish"):
        return {"posted": False}
    entry = event.json or {}
    title = next(iter((entry.get("fields", {}).get("title") or {}).values()), entry["sys"]["id"])
    content_type = entry["sys"]["contentType"]["sys"]["id"]
    notify.slack(f"Published: {title} ({content_type})", channel="#content")
    return {"posted": True}

FAQ

Common questions

Does the post cover all content types?

Yes, unless you ask to narrow it. The message names the content type, so a blog post and a product entry look different. You can restrict it to specific content types if only some matter. Every content type is included unless you narrow it, and limiting the post to blog posts or product entries is a reviewed change.

Does it fire when an entry is unpublished?

No, only on publish. Contentful sends separate events for unpublish and delete, and a second flow could post those to the same channel if you want the full picture. Contentful sends unpublish and delete as separate events, and a second flow could post them to the same channel for a complete picture.

How quickly does the message arrive?

It runs when Contentful sends the publish event, so the message appears within seconds. There is no schedule or polling delay involved in this flow. The flow runs when Contentful sends the publish event, so the post appears within seconds and no schedule or polling delay is involved.

What permissions does it need?

content_management_manage. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Collects as they arrive, acts daily