Skip to main content

Practical Examples

Think of these as recipes from a cookbook — each one is a complete automation you can rebuild in minutes and season to taste. They all follow the golden rule: free blocks for the mechanics, one or two AI steps for the judgment.


1. New-deal alert (app trigger → filter → tool)

"When a big deal lands in HubSpot, email the sales lead — and don't bother anyone with small ones."

#BlockSetup
App triggerHubSpot — Deal created
1Filter (free)Keep {{item.amount}} greater than 1000
2Tool (free)Send email — Subject: New deal: {{trigger.dealname}}

Total credits per run: zero. Small deals are filtered out silently and cost nothing at all.

2. Daily digest with a loop (schedule → loop → code → agent)

"Every morning, collect yesterday's open deals, summarize them, and send me one report."

#BlockSetup
ScheduleDaily, 8:00
1Database (free)Read CRM › Deals where status equals open
2For Each (free)Per deal: a Code block shapes {name, amount, age}
3Agent (credits)"Write a short morning digest from the list below: {{steps.2.output}}" — structured output: subject, body
4Tool (free)Send email — Subject: {{steps.3.output.subject}}, Body: {{steps.3.output.body}}

One agent step does the writing; everything around it is free.

3. Form to database (webhook → condition → database)

"Every complete answer from my website form becomes a lead row; incomplete ones get parked."

#BlockSetup
WebhookYour form sends answers to the automation's private address
1Condition (free){{trigger.email}} is not empty
2aIf true — Database (free)Insert into CRM › Leads: name {{trigger.name}}, email {{trigger.email}}
2bIf false — Database (free)Insert into CRM › Incomplete, for a human to review

4. Message triage (app trigger → switch → agents)

"Sort everything our HubSpot account sends into its own lane, and let an agent answer only what needs answering."

#BlockSetup
App triggerHubSpot — All events
1Switch (free){{item.subscriptionType}}: deal.creation → lane A · contact.creation → lane B · fallback → end
AAgent (credits)Draft a welcome note for the new deal
BDatabase (free)Insert the contact into CRM › Contacts

One trigger feeds many lanes; only lane A ever spends a credit.


Common mistakes

MistakeBetter approach
An agent step doing filtering ("ignore small deals")A free Filter does it for zero credits, every time, deterministically.
Building all four lanes before testing oneBuild lane A, test with a captured event, then add lanes.
Guessing the trigger's field namesListen for one real event first — then the variable picker knows the real fields.

What's next

Rebuild one of these on your own canvas: Building on the Canvas.