Trigger
Identify the stated starting event without treating a later email action as the input.
Workflow audit · interactive preview
Describe the process and the proposed map updates automatically. This is a local, rule-based planning tool—not a connected autonomous agent or a security assessment.
Local planning preview
The example updates automatically using simple English-language rules. No inbox is connected, no AI model is called, and no task or message is sent. Do not paste secrets or private customer records.
158 / 6000 characters
Try an example
Text stays in this page's memory. Copying or exporting saves only the proposed planning result to your device. Refreshing the page restores the example.
Proposed result · nothing executed
Local preview: Support operations. No external action has run.
Slack · Linear · Email (provider unspecified)
Priority and escalation rules · Ownership and routing rules · Classification rules · Reply content and approval
This script prints the proposed map in the Browser Preview. It is not an implementation of the external actions.
// Planning preview: prints a proposed map; no external actions.
let trigger = "Incoming email"
let workflow_type = "Support operations"
let review_required = true
print("Review this proposed workflow before connecting production")
print(trigger)
print(workflow_type)
print("Tool mentioned: Slack")
print("Tool mentioned: Linear")
print("Tool mentioned: Email (provider unspecified)")
print("Proposed: Create a support or follow-up task")
print("Proposed: Prepare a reply draft for review")
print("Proposed: Notify the specified owner or channel")
print("Proposed: Apply the reviewed ownership or routing rule")
print("Review: Urgent language detected")
print("Review: Risk is not verified by this preview; authorize live connections separately")Simple English-language rules cannot verify every instruction, negation or risk. Review their suggestions and clarify missing details; the preview never marks a workflow authorized to run.
Identify the stated starting event without treating a later email action as the input.
List explicitly mentioned providers, without pretending that they are connected.
Separate task creation, replies, notifications, ownership, and sensitive changes.
Surface sensitive terms independently from the suggested routing category. Unknown risk stays unknown.
Generate a SolveLang script that prints the proposed map; it does not perform the external actions.
Copy the planning script or export its structured result without sending a request to our inbox.
A production workflow needs an authenticated source, an approved routing policy, permitted destinations, duplicate-event protection, an audit trail and a working stop control. Routine actions can follow that approved policy; sensitive changes must preserve their own authorization boundaries. This preview does not provision or activate any of those connections.
See current capabilities