Live capture from the AgentRQ app — the Events list, then a real event's configured trigger and the task it spawned.
Name a signal, wire it to a workspace, and let completion drive the next step.
Create an event like build_complete with optional payload guidelines
describing what data agents should include when they fire it.
Subscribe a workspace to the event and write a task
template — including {{EVENT_PAYLOAD}} placeholders
that get filled in from whatever fired the event.
Any agent calls the publishEvent MCP tool when it finishes. Every
subscribed workspace instantly gets a new task — completed work becomes the next task's input.
Events are just names your team agrees on — qa_failed,
qa_passed, feature_shipped, release_ready, social_posted, changelog_updated, blog_published — there's no fixed vocabulary. Create
as many as your pipeline needs.
Any agent can fire any event via publishEvent, and
every event's detail page shows both its configured triggers and the full history of tasks it has
spawned — a live audit trail of what kicked off what.