Introducing Prepr Automations

In this months product update we have an exciting feature which is unique for headless CMS. Today we introduce the brand new Prepr Automations feature. Let's see what this means for you and your team.

Automate repetitive actions with Prepr Automations

Over the last few months, our development team worked on the Prepr Automations feature. With Automations you can automate repetitive actions, which saves you a lot of time.

Cool examples:

  • Automatically create and send a tweet when publishing a publication
  • Automatically assign a user when a publication status changes to "Review"
  • Automatically copy demo content to a development environment
You can set up an automation by selecting a trigger and linking a specific action to it. Let's dive in and see how it works with a couple of use cases.

This is how it works

To set up an automation you have to walk through 3 simple steps:

1. Select trigger event
Select the right publication event. Select the model and the status of the event you want to automate. Triggering events can be "Created", "Changed", and "Published".

2. Set additional filters
Filter on the right properties and conditions to proceed, and to create the right trigger. For example you can filter publications for a specific language or status.

3. Set the action
With this step, there are three different types of actions that can be performed. You can either create, update or delete a publication. We have set up a chronological automation use case that includes all three types. In this use case we show you how simple steps in a workflow are automated with the same publication.

Example use cases

A. Update publication

A cool use case for the update function is when you're editing a publication and you set the publication on review and you want (for example) your chief editor to review this publication. Trigger: Publication is set to review Action: Assign publication to chief editor

B. Create publication

An example for the create function is when your developers need demo content in their development environment. If the article is reviewed by the chief editor and is ready to be published in the live environment, the publication can be automatically copied to another - in this case - development environment. The developers can use the demo content in their environment to test the website. Trigger: Article is published. Action: Copy publication to another environment

Another example is when you've published a publication, a tweet with the same heading automatically gets created. Trigger: Publication is published. Action: Make a tweet.

C. Delete publication

The last option is to make an automation to  delete a publication. For example, when the  article (as mentioned above) gets automatically deleted in the development environment when it gets archived. Trigger: Publication gets archived. Action: Delete publication.

And lastly, you can test your automation, and click 'go to publication' to see the result.

What's next?

We're proud to offer you these first automations and invite you to try them out. We will be adding more triggers, filters, and actions in the future, but first we'd like to hear from you. How do you like this feature and what use cases do you want supported as well? Please send feedback to your Prepr contact, or contact sales to learn more.

Like this article? Spread the word.

Twitter LinkedIn

Want Prepr news and updates?

Sign up for our newsletter to stay up to date.

We care about the protection of your data. Read our Privacy Policy.

Subscribe to our newsletter

The latest updates and articles to learn more about content management.


Jaarbeurs Innovation Mile (JIM)

Jaarbeursplein 6

3521 AL Utrecht, The Netherlands

Phone +31 (0)30 227 17 10

KvK 54506034 • BTW NL851332390B01

© 2021 Prepr. All rights reserved.