←BaldanAll skillsLet's talk

Automation & AI Agents · Methods

Every way to automate, and what it's made of.

29 kinds of automation in 6 families, and the 24 building blocks they're all assembled from: triggers, logic, reliability and safety. Every one is animated step by step; four you can try right here.

01 · Kinds of automation

What does the work.

Six families, from code a developer writes to robots that use the screen and models that read and decide. Open any card for the full story, when to use it and what to watch out for.

Code & schedules

a developer writes it, a timer or an event runs it · 6

Workflows & integrations

apps connected to each other · 6

Screens & browsers

when the only way in is the screen · 4

Data & background work

moving data and doing slow work reliably · 4

AI-powered

reading, writing and deciding · 6

Business processes

work that passes between people · 3

02 · Building blocks

What every automation is made of.

Whatever the tool, an automation is a trigger, some logic, and the unglamorous parts that keep it working: retries, timeouts, alerts, approvals and safely kept secrets.

Triggers

what starts a run · 7

Logic

what happens in between · 6

Reliability

what keeps it working when things fail · 6

Safety & people

who can see it, stop it and approve it · 5

03 · Try them

Four building blocks, hands-on.

The cron lab works on real dates in your time zone; the other three are simulations, so you can break things safely.

Cron, explained

Type a schedule, read it in plain words, see the next runs in your time zone.

0

minute

7

hour

*

day of month

*

month

1-5

weekday

At 07:00, on weekdays.

Next runs

    Edit the expression freely: numbers, *, ranges (1-5), lists (1,15), steps (*/10) and names (MON, JAN). When both day fields are set, cron runs on either, a classic surprise.

    Polling or webhook?

    How late and how wasteful checking every few minutes really is.

    Poll every
    06:0007:0008:0009:00PollingWebhook

    Polling: requests a day

    288

    …that found nothing

    265 (92%)

    Polling: average delay

    2.7 min

    Webhook: requests · delay

    24 · instant

    Simulated: 24 events at random times over a day; 06:00–09:00 shown. Orange dots are events, grey ticks are polls, green marks are when the workflow finds out.

    Retries, backoff and jitter

    Two dozen jobs hit a service that's down. Watch what each retry policy does to it.

    service downretries per second (biggest spike 24)0 s10 s20 s30 s40 s

    Jobs that succeeded

    24 of 24

    Calls to the service

    78

    Biggest retry spike

    24 in 1 s

    Half done by

    6.3 s

    Simulated: 24 jobs start at once. Red dots are failed attempts, green is success. Without jitter, every job retries in the same second, hammering a service that's trying to recover; retrying every second gives up before it's back.

    Idempotency keys

    A lost reply, a retry, and a customer charged twice, unless…

    1. Press a button. Try “reply gets lost” with the key off, then on.

    Customer was charged

    Rp 0

    for 0 purchases · 0 charges

    With a key, the server remembers each purchase and answers a repeat with the stored result.