Workflow steps

After the trigger, a workflow runs its steps from top to bottom. Click Add step, or Insert step here between two steps, and choose a type.

Variables

Each step saves its result under a name, and later steps use it in double curly braces. The variable picker lists what is available: Built-in, Trigger and Steps. If a step returns fields, you can use one field instead of the whole result.

New event: {{trigger.event}}
Category chosen by the AI step: {{classify.category}}

Input

Inputs sit in their own section above the steps and load data before each run, such as recent orders or new files. Pick the integration, then an action, fill in its parameters and give the result a name. If you have no account of that type you may use, connect your own or ask the owner of an existing one for Can use access.

Ask Harmona

• Profile & behavior: name, description and a system prompt applied to every run. Analysis mode is Fast for routine steps or Deep analysis for thorough work, which is slower and costs more.
• Input prompt: the prompt for each run, built from earlier outputs.
• Connections: the knowledge sources the step may read, and Web search on or off.
• Skills and Model.
• Output schema: named fields (Text, Integer, Boolean, List of text) the answer must fill in. Add fields whenever a later step needs a specific value, such as a category or a title.

Logic

• Check condition compares a value using operators such as Equals, Contains, Is empty, Greater than or Matches regex. Text comparisons ignore case unless you turn on Case-sensitive.
• Steps placed under a Check condition (Add sub-step) run only when it is true. When it is false they are skipped and the run continues with the next step.
• Filter list keeps only the items of a list whose field matches a rule, and passes the filtered list on.

Action

Pick an integration, then an action, then fill in its parameters. Many parameters can be picked from the connected account, such as a channel or a project, or filled with a variable. The workflow can only use integrations enabled in its settings.

Human in the loop

This step pauses the run and sends an approval request to the Inbox. Set the Message to display (it can include variables), Assign to a person, Expires After (Day) and the Result variable.

The person answers Approve, Reject or Request changes. The answer is saved in the result variable as response (approve, reject or request_changes), with any requested changes in changes.

To act only on an approval:

1. 1Add a Logic step with Check condition right after the approval.
2. 2Compare {{approval.response}} with Equals approve.
3. 3Put the email, ticket or other action under it as a sub-step.

Harmona Inbox

Sends a one-way message to the Inbox. Write the Message to display; every run participant of the workflow receives it. Use it to report a result or confirm that something was sent.