Thoughts

Umbraco Automate: Build your Agentic Intern Team

Author

Joe Kepley

Categories:

The Umbraco Automate logo on a background of lines and dialog boxes.

A practical look at Umbraco Automate: how to spot the repetitive work in your content pipeline and build automations that handle it for you.

Earlier today I walked through the airport and “agentic” was on about every other advertisement. A year ago I wouldn’t have guessed the word would land in the common zeitgeist at all — but the pace of AI automation has outrun even the high expectations most of us already had.

The pace of change has also gotten ahead of most teams' abilities to adapt and put the new tools to use. In multiple conversations this year, the question I keep hearing is, "what would we even do with it?" That’s not a sign that AI isn't useful — rather, it's a sign that people's understanding of what these tools can do hasn't caught up with what they actually do.

Umbraco Automate is one of these leaps. Released this year at Codegarden in June, Automate brings a pluggable workflow model to the Umbraco Backoffice that allows for trigger-based orchestration using a visual workflow builder. That's a complicated-sounding description, but if you've used tools like IFTTT or Nodemation (n8n), this will feel immediately familiar. Tied with Umbraco AI, you can build complicated automations that change how you publish content — and, potentially, how you approach much of your daily work.

So how do you decide where to start?

Determining what to automate in the first place.

The first step to automating a process is knowing what the process is. And while that might sound reductive, you'll be surprised how much of your daily activity isn't really defined.

One exercise that I've found helpful is imagining you've just taken on a dozen summer interns. While a naive reaction might be, "Great, I have so much help now,” those of us who have worked with interns have a much more realistic reaction: "Agh! What am I going to give these people to keep them busy?!"

This is a great way to find tasks worth automating. If I look at my calendar, I might have a block at the start of the day and after lunch when I work on my email. But I can't simply tell an intern "process my inbox;" that doesn't give them enough information to do a good job. I need to sit down and figure out, "how do I process my inbox?" This might lead me to come up with something like:

"I need you to triage my inbox. Prioritize emails from people in my company, client contacts, and people whose names match my connections on LinkedIn. Flag anything with an RFP or an invoice attached. Any sales promotions should go in a separate folder. Let me know what needs a reply immediately, and what can wait until later."

That might give an intern a good place to start. Interestingly, it's also starting to read like a decent LLM agent prompt.

If you go through your day like that, you'll find that there are certain tasks that are the best use of your time. I'll use an LLM to help triage email, but personally I'd never use it to compose or reply to messages to people I know. Those folks are expecting to hear from me, not an LLM. I'll use an LLM to gather information on a potential client and help understand a budget, but I would never use it to make a final decision. But everything that's not the most important and best use of your time is probably "grunt work", and a candidate for your virtual interns.

For example, content production has a lot of grunt work involved. Let's look at the content production pipeline we use here at Blend:

  • Our marketing team meets weekly. We talk through the campaigns we're running and what we're trying to achieve, and ideas for content arise from that — this article is in support of our talk on Automate at the Umbraco US Fest, for example.
  • Article ideas go into a project organizer and get assigned to someone to write by a certain deadline.
  • Once written, the article goes to an editor for review.
  • It also goes to the design team to produce any supporting graphics.
  • When those pieces are ready, it goes into the CMS.
  • At this point, it also gets reviewed for accessibility, SEO, and GEO. Extra metadata like summaries, schema tags, and etc get added in support of this.
  • Finally, it's ready to publish. Now share messages are added to social platforms like Instagram and LinkedIn

When I look at that list, there are only a few things I wouldn't hand off to an intern: coming up with the ideas, writing the article, and for the most part, the editing. Everything else feels like we could use some help. Let's start automating!

A set of colored lines turning into a bundled mess, signifying technical debt.

What is organizational AI readiness?

An Organizational AI Readiness Assessment helps organizations get a clear, honest picture of where they stand with AI — what's already happening, what opportunities are worth pursuing, what risks need to be managed, and what a reasonable path forward looks like.

Learn more with our organizational AI readiness explainer.

 

What is an Organizational AI Readiness Assessment?

How to automate your task ideas.

When coming up with automation tasks, it's helpful to think along the lines of, "when X occurs, these things should happen." That 'X' is our trigger — something that will start the automation.

Let's take a look at how we might automate some of the grunt work around publishing an article so I can focus on writing. I'd explain it to my intern like this:

"When an article is published, look at its contents, and evaluate it for SEO and GEO. Add any missing metadata. Also, draft a LinkedIn post to promote it. Let me know via Slack what you changed."

That seems like a reasonable set of instructions — we'll just need to elaborate a bit with some details (like “How do we like our social posts to sound?” or “How long do we want summaries?”). This is ready to set up in Umbraco Automate.

The first thing you need to do in Automate is to create a Workspace. The Workspace can hold multiple automations, and it decides what permissions and capabilities are available. You need to select an Umbraco user to act as the Service Account, which will decide who the workflow runs as. You can also select a role to restrict the workflow to a subset of that user's permissions. It's tempting to not worry about permissions — just point this at an admin user and call it a day — but for real-world use it's important to take a moment and set up an account that has only the permissions needed to do the work.

Screenshot of Umbraco Automate showing Joe Kepley's name as the Service Account Key.

We can also limit certain workspaces to certain Connections. Connections are your external services that will interact with the automation. In our case, we'll need Slack for what we have planned.

Once that's set up, let's start wiring things together.

We start by adding a trigger, in this case when the article is published. We then can chain together a series of actions. While it might be nice in the future to simply add an AI agent action and have it handle the whole process, right now agents in Automate are limited in their interactions with the CMS directly, so we're only able to use them to generate text here.

Instead, we'll set up actions to grab the content, generate each of the properties we want to update, each with an agent prompted to create the right text for that field if it's empty. We then update those properties in parallel, and when they're all done, we publish the new changes and send a Slack to let editors know what's been done. They can review the added fields right in Slack and change them if they want.

A screenshot of Automate's triggers and workflow, starting with "Content Published" at the top and ending with various endpoints, including "Send Slack Message."

That's a simple but pretty powerful example of what Automate can do. Again, it's about taking a process that should be getting done now but probably isn't always — like forgetting to set meta information on a newly published article — and making it automatic. There are plenty of ways this can help, but here are a few more ideas to put your agentic interns to work:

  • Regularly summarize the site's publishing activity and post it to your editor Slack channel to keep everyone on the same page.
  • Automatically transcribe uploaded audio so your podcast episodes will be searchable and accessible.
  • Use AI to evaluate a user's Umbraco Form input and assign them a persona score in Umbraco Engage. Trigger a notice to a salesperson if the score is high enough.
  • Use Automate's webhook actions and triggers to connect with your other systems — for example, marking a task as complete in your project system when an editor publishes something to the website.

Focus on what matters.

A lot of us in the technology space have looked at the developments of the past couple of years as a threat: "If the computer can do that, what am I going to do?"

While that's a natural first reaction, it's the wrong attitude. A better approach is, "Now that the computer can do that, I can spend my time on this important stuff." Regardless of your role, there are a lot of things you do every day that need to be done, but not all of those are things you'd really do if you had unlimited help. Now that you do, it's time to open up the potential of what you can really get done.

Related articles.

We’ve been writing and creating things for — and about! — the web for over 20 years, including our thoughts about Umbraco. Check out more articles similar to this one.

Related services.

AI Icon - Lightbulb with Gear

AI Strategy

Practical AI guidance for content teams — from editorial workflows to search optimization — without chasing hype.

Strategy Icon - Castle Chess Piece

Web Strategy

Content strategy, information architecture, governance, and CMS planning — the strategic decisions that make complex web projects succeed.

Operations Icon - Connected Circles

Web Operations

Who owns your content after launch? Web operations and governance planning for editorial teams managing complex sites.