Documentation
The Flow Designer
Draw what should happen when something is said in a meeting (a trigger, a condition, the steps) and Jaha runs it live, logging each step and what it returned.
Triggers
A flow starts when a meeting begins or ends, when a phrase is said out loud in a call, when a topic keeps coming up, on a voice command, or by hand. Most people build the phrase trigger first: someone says “the printer is not working” in the facilities meeting, and a ticket exists before they finish the sentence.
Steps and conditions
Steps are the things Jaha can do: create a ticket (in Jira, Linear, ServiceNow, Asana and others), send an email, post to a channel, find or update a CRM record, ask the model a question, wait, request an approval, notify someone, or call a webhook. Conditions branch on the transcript, the attendees, the account or any earlier step’s result, with AND/OR groups.
A step that would create a duplicate doesn't: the same issue raised in three meetings becomes one ticket with three mentions.
Templates and the script step
Any field accepts {{templates}}, like the meeting subject, the account domain or an earlier step’s output. For logic that doesn't fit in a field, there's a JavaScript step with a real editor: highlighting, bracket matching, Tab to indent, and the last run’s error marked on the line where it happened.
Runs, errors and Ask Jaha
Every run is logged step by step with its inputs and outputs. When a step fails, the editor shows the error where it happened, and “Ask Jaha” next to the step knows the product: paste the error, ask why it failed, ask for a setup that works, and apply the suggestion to the step in one click.