Togra ContentFlow

Togra ContentFlow lets you automate repetitive WordPress work with simple, readable workflows:

• When something happens (a trigger)
• If your conditions match (conditions)
• Then perform the actions you chose (actions)

Triggers, conditions and actions are built from registries, so every part of the plugin is extensible:

• Triggers : a post is published, updated, changes status or is trashed; a file is uploaded; a user registers, logs in, logs out, resets their password, updates their profile, changes a custom field, changes role or is deleted; a comment is submitted or approved.
• Conditions : post type, post status, post category, user role, post custom field, user custom field, joined with AND or OR.
• Actions : send an email, email the site admin, create a post, update the post, change the post status, move the post to the trash, update or delete a custom field, create a user, update the user, add or remove a user role, send a webhook, write a log entry.
• Webhooks : send workflow data to Zapier, Make, n8n, Slack or your own app, as JSON or form fields, with custom headers and an optional HMAC signature.
• Incoming webhooks : every workflow can have its own private URL that other services post to. Received fields become tokens and conditions. Protected by a secret key, optional HMAC signature, a per-minute limit and size limits. Incoming webhooks cannot create or update WordPress user accounts.
• Run rules : limit a workflow to a number of runs in total or per user, run it only once per post, or add a cooldown for the whole workflow, per user or per post.
• Schedule : run a workflow every hour, day, week or month at a set time, in the site timezone. Missed runs happen once as soon as the site is back.
• Wait : pause a workflow for minutes, hours, days or weeks, or until a date, then continue with the next actions. Delays are stored in the database, so they survive restarts and missed cron runs.

Text fields accept tokens such as {post.title} , {user.email} , {post_meta.price} , {date.today} and {site.name} , which are replaced when the workflow runs. Every run is recorded, step by step, on the Logs screen.