Start from something that already works

A working example you can run right now: it takes an incoming order, tidies up the values, and routes big orders differently from small ones. No accounts to connect — press Test on any step to watch real data flow through it.

Pause the workflow and email someone an approve/reject link — the run waits for their decision, then takes a different path depending on the answer. Useful for refunds, discounts, or anything that shouldn't happen unattended.

Instead of an email per event, quietly collect each one. Pair this with “Send the daily digest”, which empties the pile on a schedule and sends a single summary.

Once a day, empty everything collected by “Collect events for a daily digest” and send it as one email — and stay quiet on days when nothing happened.

Some systems send the same event twice. This remembers the last id it handled and skips anything it has already seen, so the work only happens once.

Read one field and take a different branch for each value — urgent, normal, or anything else — instead of chaining yes/no questions.

Runs on a timer and records a timestamped heartbeat. A good starting point for anything that should happen on a schedule.

An empty workflow with failure notifications already switched on, so you hear about it by email the moment a run breaks.

Take a messy incoming webhook and turn it into tidy, predictable fields — lowercased emails, proper capitalisation, a formatted date — ready for whatever step you add next.

Post a tidy message to a Slack channel whenever someone signs up. Connect Slack once and this works for any signup webhook.

Receive YakDesk ticket webhooks (Ticket Settings → Outbound webhooks) and post each event to a Slack channel.

Receive a form webhook and create a YakDesk ticket via POST /api/v1/tickets (Bearer API key).

Receive free-form text, pull out structured fields with AI, and open a ticket from the result.