Joomla
CMS & ContentRun a Joomla site from your workflows. Agents create, update, and publish articles, manage categories, tags, and user accounts, and audit menus, modules, banners, template styles, and global configuration through the Joomla Web Services API.
What This Integration Enables
Joomla powers sites that have outlived several redesigns and most of the people who built them, and since version 4 its Web Services API finally makes those sites automatable end to end. This connector covers the three jobs a long-lived CMS actually generates: moving content in and out, keeping the user roster honest, and auditing the accumulated structure of menus, modules, templates, and configuration that nobody has inventoried since launch. FlowRunner runs all three as governed flows, with staged states and review gates where the site touches the public. - Create, update, and publish articles with categories, tags, language, and SEO metadata - Stage content unpublished and flip state only after review - Provision, update, block, and remove user accounts programmatically - Audit site structure: menus, modules, template styles, banners, and installed languages - Read and cautiously update global configuration, including offline mode and mailer settings - Respect Joomla's own safety rail: articles and categories must be Trashed before permanent deletion
Without FlowRunner
With FlowRunner
Use Case Scenarios
The editorial pipeline that ends on the site
Finished drafts from the content team's workflow arrive with title, body, and target section. The flow resolves the category with List Categories, stages the piece via Create Article with alias and meta description set, and queues the preview for editorial sign-off. On approval, Update Article publishes it. Syndicated pieces from the company's [WordPress](/integrations/wordpress) property run the same line, with Create Category and Create Tag keeping taxonomies aligned across both platforms.
Accounts that track the org chart
When HR marks a departure, the flow finds the account with List Users, blocks it immediately with Update User, and files the removal for the quarterly cleanup. New hires in content roles get Create User with the right group assignments. A monthly sweep cross-references List Users against the HR roster and posts the discrepancies to [Slack](/integrations/slack): the contractor whose engagement ended in March still has an author login, and now someone knows.
The site inventory nobody had time to build
On a schedule, the flow walks List Site Menus, List Site Modules, List Template Styles, List Banners, and List Languages, and writes the full inventory to [Google Sheets](/integrations/google-sheets). Diffs against last month's snapshot get flagged: a new module in a sidebar position, a template style change, a banner whose click counts flatlined. Get Application Config rides along so SEO settings and offline mode are part of the record. The agency handoff that used to take a discovery week starts from a current spreadsheet.
Human-in-Loop Highlight
Update Application Config writes the global configuration of the entire site, and it requires a Super User token because it deserves one. This is the endpoint where one wrong key takes the site offline, breaks search-engine-friendly URLs sitewide, or silently redirects the mailer, and the blast radius is every page and every visitor at once. So FlowRunner treats it as the most gated write in the connector. Agents read config freely for audits, but any change request posts as a proposal: the setting, the current value, the new value, and why the flow wants it changed. A person approves before Update Application Config runs, and the flow logs the before and after. The same instinct applies down-stack: Delete User is immediate and irreversible, so departures are blocked instantly by the agent but removed only in a reviewed batch, and article deletion follows Joomla's own two-step, Trashed first by machine, purged later with sign-off.
Agent Capabilities
27 actionsArticles
5- List Articles Retrieves paginated articles with full-text search, category and state filters, and sorting. Each returns as a JSON:API resource with title, alias, state, category, and intro text.
- Get Article Retrieves a single article by ID with full attributes, including text, metadata, and language.
- Create Article Creates an article in a category with HTML intro text, alias, publication state, language, and SEO metadata. The staging step of the editorial pipeline.
- Update Article Updates an article by ID, changing only supplied fields: move categories, edit text, update metadata, or flip publication state. The publish switch behind the review gate.
- Delete Article Deletes an article by ID. Joomla requires the Trashed state first, so removal is always a two-step with an audit trail.
Categories
5- List Categories Retrieves content categories with title, alias, path, parent, level, and state. The taxonomy map for filing content.
- Get Category Retrieves a single category by ID with description and hierarchy detail.
- Create Category Creates a category, optionally nested under a parent, with description and state.
- Update Category Updates a category by ID: rename, move, or change state.
- Delete Category Deletes a category by ID. Requires the Trashed state first, and the category must be empty.
Users
5- List Users Retrieves paginated users with name, username, email, block status, and registration date. The roster read behind account audits.
- Get User Retrieves a single user by ID including group assignments and last-visit date.
- Create User Creates a user account with name, username, email, password, and group assignments.
- Update User Updates a user by ID: rename, change email, reset password, block or unblock, reassign groups. The instant-block step for departures.
- Delete User Permanently deletes a user account, immediately and irreversibly. Runs only in reviewed batches.
Tags and Fields
4- List Tags Retrieves content tags with title, alias, path, and state.
- Get Tag Retrieves a single tag by ID with its description and hierarchy.
- Create Tag Creates a tag with optional description, parent, and language, for taggable content across the site.
- List Fields Lists the custom fields defined for a component context, such as article or user profile fields. The schema read before mapping external data in.
Site Structure
6- List Banners Lists banners with click and impression counts, target URL, and state. The performance read for banner campaigns.
- List Site Menus Lists front-end menu types with menutype, title, and description.
- List Administrator Menus Lists back-end menu types for admin-side audits.
- List Site Modules Lists front-end modules with title, type, position, and state. The inventory of what actually renders where.
- List Template Styles Lists template styles with template name and default flag. The audit step before theme changes.
- List Languages Lists installed content languages with tags and state. The validation source for content language codes.
Configuration
2- Get Application Config Retrieves the global configuration: site name, offline mode, SEO options, mailer settings. Requires Super User privileges.
- Update Application Config Updates global configuration settings, changing only what is supplied. Super User only, and the most gated write on this page.
Frequently Asked Questions
What can FlowRunner do with Joomla?
FlowRunner agents can run List Articles, Get Article, and Create Article in Joomla, plus 24 more actions.
Does connecting Joomla to FlowRunner require OAuth?
No. Joomla connects to FlowRunner with an API key, no OAuth flow required.
Can Joomla trigger a FlowRunner workflow automatically?
Joomla doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Joomla
$100 in credits. No card required. Connect in minutes.