Every new VisualFlowBuilder account starts with one workflow already on the canvas: support triage. It is a good way to see how the four step types fit together, and for many teams it is useful as it stands.
The steps
Trigger: webhook. The workflow has its own URL. Anything that can send an HTTP POST can start it: a contact form, a helpdesk's outgoing webhook, a store's order-issue form, or a line of code in your own app. JSON and ordinary form data both work, and every field in the request becomes available to later steps as {{field}}.
AI step: summarize & classify. This step reads the subject and message and adds three fields: a one- or two-sentence summary, a priority of high or normal, and a category such as billing, bug or account. Words like "down", "can't pay" or "urgent" push the priority up.
Condition: is it urgent? The condition checks priority equals "high". The first connection out of a condition is the yes branch; the others are the no branch.
Actions. On the yes branch, a Slack message goes to your support channel with the customer's email and the summary. Both branches send an email summary to your account address and log the outcome.
Connecting it
- Open the workflow and copy the webhook URL from the panel under the canvas.
- In your form tool or helpdesk, add an outgoing webhook and paste the URL. Make sure it sends at least an email and a message field.
- Connect Slack on the Integrations page by pasting an incoming-webhook URL for the channel you want.
- Send one real test from the form, then open Run history to check what each step did.
Adjusting it
Change the condition to route on category instead of priority, add a second Slack action for billing questions, or swap the email action for a webhook that creates a ticket in your own system. Press Test run after each change; the run history shows exactly which branch ran.