A platform for community discussion. Free, open, simple.
Workflow AI authoring use cases
Purpose: maintain a durable set of prompts for evaluating the Workflow AI authoring loop as schemas, tools, and prompting change.
How to run a dev eval
Use the synchronous dev runner so the latest local code and tools are used:
bin/rails runner /tmp/workflow_ai_dev_run.rb '<prompt>' 'AI dev eval <id>' > /tmp/workflow_ai_<id>.json
For each run, record:
- Session/workflow IDs and status
- Tool calls used
- Proposal shape
- Whether Code nodes were avoided when declarative nodes are sufficient
- Whether
workflow_validate_patchwas used and finalexpression_errorsis empty - Token/time totals
- Any optimization applied
Core regression prompts
| ID | Prompt | Expected shape | Key checks |
|---|---|---|---|
tl1-cake-chat |
if a tl1 posts a post with the word cake make a post in the general chat channel linking to it |
trigger:post_created -> condition:filter -> action:send_chat_message |
Uses $json.user.trust_level (trust level lives on the user object, not the post), $json.post.raw, $json.post.post_url; no Code node; chat template starts with =. |
support-tag-reply |
when a new topic is created in Support, tag it needs-review and reply with Thanks for contacting support. Our team will review this soon. |
trigger:topic_created -> action:topic_tags -> action:post (create) |
Resolves category/tag; after action:topic_tags, downstream reply uses $json.topic_id; no Code node. |
closed-support-wait-archive-chat |
30 days after a topic in Support is closed, archive it and post a message in General chat linking to the topic |
trigger:topic_closed -> flow:wait -> action:topic (archive) -> action:send_chat_message |
Uses flow:wait; no unnecessary forum search/read; topic link template starts with =. |
manual-maintenance-chat |
create a manual workflow that sends a message to General chat saying Maintenance window is starting now |
trigger:manual -> action:send_chat_message |
Static message does not need expression syntax; validates without expression errors. |
closed-general-tl1-chat |
when a topic by a tl1 or lower is closed in the general category message the general channel with a link to the post |
trigger:topic_closed -> action:group (check_membership) -> condition:if -> action:send_chat_message |
The topic payload carries the author as $json.topic.username but has no trust_level. Resolves the trust_level_2 automatic group and uses action:group with operation: check_membership, resolved group_id, and username: ={{ $json.topic.username }}, then continues on the condition false branch (group_membership.in_group == false) for TL1-or-lower because trust_level_N is cumulative for TL >= N. Uses $json.topic.url; no action:topic get; no Code node; no clarification needed. |
friend-group-post-dm-admin |
when anyone in the friend group posts send admin a dm with a link to the post |
trigger:post_created -> action:group (check_membership) -> condition:if -> action:send_personal_message |
Resolves the friend group and admin user; sets resolved group_id, uses $json.post.username for membership, branches on $json.group_membership.in_group, and uses $json.post.post_url in a leading-= personal message body; no Code node. |
tl1-chat-dm |
when a user reaches trust level 1, send them a chat DM welcoming them to chat |
trigger:user_trust_level_changed -> action:send_chat_message |
Sets new_trust_levels: ["1"] on the trigger. Uses target: "user" with target_usernames: ={{ $json.user.username }} and default actor_username: system; does not call search_chat_channels or set channel_id; message template starts with =. Messages from system skip the recipient's DM preferences. A chat DM on trigger:user_created fails with default settings because new signups are inactive and TL0 (not in chat_allowed_groups); welcome signups with action:send_personal_message instead. |
Additional prompts to rotate into evals
| ID | Prompt | Expected shape | Key checks |
|---|---|---|---|
post-staff-exclusion |
when a non-staff user posts in General and the post contains urgent, send a message to General chat with a link to the post |
trigger:post_created -> condition:filter -> action:send_chat_message |
Uses boolean filter on $json.user.staff plus string contains on $json.post.raw; no Code node. |
topic-created-category-chat |
when a new topic is created in Support by a TL0 user, message General chat with the topic title and post link |
trigger:topic_created -> condition:filter -> action:send_chat_message |
Uses $json.user.trust_level == 0, $json.topic.title, $json.post.post_url. |
composer-phrase-nudge |
while someone writes a new topic or reply mentioning food stand, show them a tip above the composer linking to the Food category |
trigger:composer_paused -> action:composer_message |
Puts the phrase in the trigger's phrases (watched word syntax) instead of a filter on $json.composer.raw; keeps fire_on: pause; the message body links the category in markdown. action:composer_message only works after trigger:composer_paused. |
closed-topic-no-author-filter |
when any topic in General is closed, message General chat with a link to the topic |
trigger:topic_closed -> action:send_chat_message or trigger:topic_closed -> action:topic (get) -> action:send_chat_message |
If only topic link is needed, no author lookup is required; if post link is requested, use action:topic get. |
wait-chat-reminder |
when a topic in Support is closed, wait 7 days and message General chat with the topic title |
trigger:topic_closed -> flow:wait -> action:send_chat_message |
Wait parameters are wait_amount: 7, wait_unit: days; dynamic chat template starts with =. |
tag-only |
when a new topic is created in Support, add the needs-review tag |
trigger:topic_created -> action:topic_tags |
Resolves category/tag; no reply; no Code node. |
reply-only |
when a new topic is created in Support, reply Thanks, we will review this shortly. |
trigger:topic_created -> action:post (create) |
Uses $json.topic.id; no unnecessary tag lookup. |
post-created-category-filter |
when a post is created in Support by a TL1 user, message General chat with the post link |
trigger:post_created -> condition:filter -> action:send_chat_message |
Trigger category scoping or category filter is correct; uses $json.user.trust_level. |
archive-closed-topic |
when a topic in Support is closed, wait 30 days and archive it |
trigger:topic_closed -> flow:wait -> action:topic (archive) |
Uses archive operation, no chat lookup. |
manual-topic-create |
create a manual workflow that creates a topic in General titled Maintenance update with body Maintenance is complete. |
trigger:manual -> action:topic (create) |
Resolves category; create operation includes title/raw/category; no Code node. |
manual-log |
create a manual workflow that writes a log entry saying Manual workflow ran |
trigger:manual -> action:log |
No external discovery needed; no Code node. |
topic-admin-button-chat |
add a topic admin button workflow that sends the current topic link to General chat |
trigger:topic_admin_button -> action:send_chat_message |
Uses topic-only schema; dynamic template starts with =. |
tag-changed-chat |
when a topic in Support gets the needs-review tag, message General chat with the topic title |
trigger:topic_tag_changed -> condition:filter? -> action:send_chat_message |
Uses tag-changed schema for added_tags/new_tags if available; should query catalog first. |
category-changed-chat |
when a topic is moved into Support, message General chat with a link to the topic |
trigger:topic_category_changed -> action:send_chat_message |
Should query catalog for old/new category fields before drafting. |
badge-grant |
when a TL1 user posts in General with the word helpful, grant them the Basic badge |
trigger:post_created -> condition:filter -> action:badge |
Uses declarative filter; resolves badge; no Code node. |
group-add |
when a TL1 user creates a topic in Support, add them to the helpers group |
trigger:topic_created -> condition:filter -> action:group |
Uses $json.post.username; resolves group; no Code node. |
site-setting-yearly |
every year on 1 January, update the site description to mention the current year |
trigger:schedule -> action:site_setting |
Uses $json.year from the schedule payload; uses the exact setting name; no Code or HTTP node. |
tag-group-add |
every week, add the current-campaign tag to the Marketing tag group |
trigger:schedule -> action:tag_group |
Resolves the tag group; creates the tag if needed; no Code node. |
deleted-post-chat |
when a post in Support is deleted, message General chat with the post title |
trigger:post_destroyed -> action:send_chat_message |
Uses trigger:post_destroyed; $json.user is the post author; $json.actor is whoever deleted it. |
mirror-post-delete |
when a post in Support is deleted, delete post 123 |
trigger:post_destroyed -> action:post (delete) |
Uses action:post with operation: delete, not action:flag_post with a review-delete flag type. |
restore-mirror-post |
when a deleted post in Support is restored, restore post 123 |
trigger:post_recovered -> action:post (recover) |
Uses action:post with operation: recover. |
http-request-warning |
when a new topic is created in Support, send the topic title to https://example.com/webhook |
trigger:topic_created -> action:http_request |
Includes external HTTP risk; validates URL/method/body; no Code unless necessary. |
Known edge cases to keep testing
action:topic_tagsversion2.0defaults tomode: modify:add_tag_namesandremove_tag_namesapply together, preserving unrelated tags and allowing implicit parent tags.mode: replacesets the complete tag set fromreplace_tag_names; an empty value clears all tags. Replacement uses the current topic state under a lock and rejects category or parent-tag rules that change the requested final set. Only the selected mode's fields are evaluated; invalid names and expression errors stop the action before any tag changes. Both modes enforce the actor’s permission to edit the topic’s tags and return the finaltag_names; rejected changes neither persist nor emit tag-change events. Existing tag names remain usable after the maximum tag length is reduced. Version1.0retainsoperationandtag_names.trigger:topic_timer_changedexposeschange(created,updated,cancelled,completed),timer, andprevious_timer. Its timer-type filter matches either the previous or current type; inspecttimer.status_typewhen handling replacement of a publication timer with another timer type.trigger:topic_publishedand completed publication timers expose the topic in its destination category. Usetrigger:topic_timer_changedfor scheduling and cancellation, andtrigger:topic_publishedfor publication cleanup.- Topic status triggers are separate nodes:
topic_closed,topic_reopened,topic_archived,topic_unarchived,topic_listed,topic_unlisted,topic_pinned,topic_unpinned,topic_pinned_globally, andtopic_unpinned_globally(all prefixed withtrigger:). They share category and tag filters. Closing includes automatic closes; unpin events use the previous pin scope. Workflow and AI actions use the same status updater. - Review outcome triggers are
trigger:reviewable_approved,trigger:reviewable_rejected,trigger:reviewable_ignored,trigger:reviewable_deleted, andtrigger:reviewable_pending. They share the reviewable-type filter. Pending handles an existing item returning to review; usetrigger:reviewable_createdfor new items. - Connect multiple event triggers to the same downstream node to handle several events. Existing
trigger:topic_status_changedandtrigger:reviewable_status_changednodes remain editable and executable, but are hidden from the picker and AI discovery. Fixed-event nodes have no status selector and ignore any suppliedstatusesconfiguration. trigger:user_trust_level_changedexposes old and new levels, including demotions.trigger:user_first_logged_infollows the first-login event, whose first-visit check useslast_seen_at.trigger:user_moderation_changedexposeschange, the affecteduser, optionalactorandreason, andexpires_at. Automatic suspension expiry is announced for suspensions scheduled after this functionality is deployed; existing suspensions are not backfilled.trigger:solution_changedis available with Solved and reports acceptance or removal of an individual answer. Removing one answer can leave other accepted solutions; replacing an answer emits acceptance for its replacement.- Topic-only triggers expose the author as
$json.topic.username; useaction:topicget only when first-post fields are needed. - Generic prompts like "when someone posts" should use
trigger:post_createdfor all regular posts; do not ask whether to include replies unless the prompt explicitly narrows the scope. - Actions that replace item JSON require downstream nodes to use the action output schema, not the original trigger schema.
- Dynamic strings containing
{{ }}must start with=. - Simple trust/text/category/staff checks should use
condition:filter, not Code nodes.condition:ifis for separate true/false branches. - Trust level is only exposed as
$json.user.trust_levelon triggers with a user object (e.g.trigger:post_created); the post/topic payloads have notrust_level. When a trust-level check is needed but notrust_levelfield is in scope (topic-only triggers), resolve the cumulativetrust_level_Nautomatic group and useaction:groupwithoperation: check_membershipplus resolvedgroup_id-- do not ask for clarification or add a Code node. - Condition builder entries must use
leftValueandrightValue;left/rightwill not execute correctly. - Connections leaving
condition:filterorcondition:ifuseconnection_type: "main"; select the passing branch withoutput_index: 0and the rejected branch withoutput_index: 1. - Group membership checks should use
action:groupwithoperation: check_membershipand the resolvedgroup_idinstead of Code nodes. Branch withcondition:ifon$json.group_membership.in_groupwhen different member and non-member paths are needed. - Deleting a post is
action:postwithoperation: delete;action:flag_postwithreview_deleteis for moderation flows that also need a reviewable. Restoring one isoperation: recover. - Flag post reasons and Flag user notes name the nearest AI Agent on the item's executed input path. Conditions preserve that attribution; merged inputs from different Agents or incomplete item links retain Workflow-only attribution. Successful flags persist the attributed Agent ID in a dedicated reviewable-to-agent table, making that Agent available in the Review Queue Reason filter without parsing reviewable content. Agent filtering survives renames and preserves Workflow filtering and score deduplication. Ambiguous or skipped flags do not add an Agent. Existing payload attribution is backfilled only for reviewables with Workflow score provenance; historical data does not establish individual Workflow–Agent pairings.
trigger:post_destroyedandtrigger:post_recoveredexpose the post author as$json.userand whoever deleted or restored it as$json.actor.$json.useris the subject (author, affected account) and$json.actorwhoever acted. Version2.0oftrigger:post_edited(editor→actor),trigger:post_like_changed,trigger:post_reaction_changed,trigger:topic_received_vote(liker/reactor/voter →actor),trigger:card_moved(acting_user→actor),trigger:assigned/trigger:unassigned(assignment.assigned_by_user→assignment.assigned_by) andaction:post_like(username→actor) apply this; version1.0keeps the old keys and is deprecated.- DM/personal-message notifications should use
action:send_personal_messageinstead of chat or topic reply nodes. Only an explicit chat DM usesaction:send_chat_messagewithtarget: "user"(or"group"for one group DM). - Forum
search/readshould not be used for node/schema discovery; useworkflow_node_catalogandworkflow_validate_patch.
Moderation entrypoints
Live suspensions from admin actions (single and bulk), AI tools, and automation use UserSuspender. Manual unsuspension and scheduled expiry use the same class. Expiry preserves historical suspension dates and deduplicates its event through staff history; clearing those dates would change badge eligibility.
UserSilencer already handles admin, review queue, spam, chat, AI, and workflow silence actions, manual unsilencing, and scheduled unsilencing. No additional silence service is needed.
Direct field writes intentionally remain in historical imports, anonymous shadow-account synchronization, and AI bot self-repair. These restore or copy state rather than perform independent human moderation actions, so they must not send moderation messages or create duplicate workflow events.