Choose ONE repetitive task from your work or life (not Marina's example) and describe it as a candidate for automation. Return JSON {"task":"...","trigger":"...","result":"...","why_automate":"..."}. B trigger is the event from which the task begins; in result - what should be the output; in why_automate - why it is worth giving it to the machine (frequency, boredom, economy).
Automation is a conveyor belt: you describe the rule once “when X happens, do Y”, and then the system executes it itself, without you. The mechanics are simple: there is a trigger event (a letter arrived, a row was added to the table, it is 9 am), there is a chain of steps and there is a final action (send, record, notify). A bundle tool simply connects your applications with wires and sends data through them. Newbie Key: Don't try to automate 'everything at once'. Take one task that you do manually every day using the same algorithm. Insider: count not time, but frequency and irritation - a task for 2 minutes, but 20 times a day pays off faster than a rare half-hour. Another trick: before setting up, speak the script out loud with the words 'when... then...'. If you can’t, it means the rule is still unclear. A common mistake: automating a creative or rare task where each case is unique. These eat up more time on setup and repair than they save.