Automation 101

Apply existing file, script and Workspace skills to explicit contracts, outcomes and dependencies.

1. Define the Job Before the Workflow

   Turn an ambiguous request into a trigger, expected result and boundaries.

   AvailablePro25 min

2. Build a Lead Intake Route

   Capture a supplied lead and deliver a visible result in the Professional Workspace.

   AvailablePro40 min

3. Choose the Right Trigger

   Compare a schedule, a new event and a changed record for the same job.

   AvailablePro30 min

4. Put Dependencies in the Right Place

   Separate steps that depend on earlier output from steps that can run independently.

   PlannedPro (planned)

5. Repair a Workflow That Runs Too Soon

   A notification references a record that has not been created yet; trace the failure.

   PlannedPro (planned)

Move beyond arrows: inspect the values each step receives and produces.

1. Follow a Value Through the System

   Trace one customer identifier through input, step output and final result.

   PlannedPro (planned)

2. Map the Fields That Matter

   Match incoming field names to the action's expected input.

   PlannedPro (planned)

3. Separate Run Data From Configuration

   Combine input variables with YAML and environment defaults across different runs.

   PlannedPro (planned)

4. Find the Missing Field

   Debug absent, empty and unexpected values before an action fails.

   PlannedPro (planned)

5. Build an Intake Flow That Adapts

   Combine mapping, dynamic values and defaults across several supplied requests.

   PlannedPro (planned)

Revisit conditions with multiple branches, boundaries and human decisions.

1. Make One Decision Explicit

   Express a useful condition with a field, comparison and expected value.

   PlannedPro (planned)

2. Build a Priority Support Router

   Send requests to the appropriate team and produce a visible message.

   PlannedPro (planned)

3. Test the Edges of a Rule

   Explore equality, thresholds and unexpected values using boundary inputs.

   PlannedPro (planned)

4. Repair the Branch Nobody Checked

   A workflow handles common cases but drops an unmatched request.

   PlannedPro (planned)

5. Keep Judgment in the Loop

   Separate mechanical routing from a decision that needs human review.

   PlannedPro (planned)

Turn real-shaped data into usable values and repeated actions.

1. Load Structured Data Across Files

   Use known JSON to load a customer file, trace nested values and handle the expected shape.

   PlannedPro (planned)

2. Clean Data Before Sending It

   Normalize supplied names, dates and identifiers without losing the original meaning.

   PlannedPro (planned)

3. Turn Repeated Steps Into Functions

   Introduce def, parameters and return values, then reuse one transformation in several steps.

   PlannedPro (planned)

4. Process a Batch With Reusable Functions

   Apply known loops to per-item functions, collected results and rejected records.

   PlannedPro (planned)

5. Build a Batch Summary

   Combine loader, transformation and summary functions; introduce project imports before splitting work across files.

   PlannedPro (planned)

Use context across runs without confusing one execution with another.

1. Schedule Work at the Right Time

   Compare intervals and calendar schedules; reason about local time and delayed runs.

   PlannedPro (planned)

2. Respond to a Change, Not Just a Clock

   Compare event-driven intake with checking repeatedly for new work.

   PlannedPro (planned)

3. Remember What Happened Last Time

   Distinguish current-run variables from state stored between executions.

   PlannedPro (planned)

4. Stop a Duplicate Event From Doing Double Work

   Replay a supplied event and inspect why a second notification appears.

   PlannedPro (planned)

5. Build a Reminder System That Remembers

   Combine scheduling, saved state and an explicit completion check.

   PlannedPro (planned)

Introduce record-store operations through supplied lookups and updates; SQL and database administration are not assumed.

1. Give Every Record an Identity

   Separate record IDs from names and fields that can change.

   PlannedPro (planned)

2. Find the Right Record

   Look up an order and inspect zero, one and multiple matches.

   PlannedPro (planned)

3. Update a Record Without Erasing Its History

   Choose which fields to change and keep useful execution references.

   PlannedPro (planned)

4. Repair an Update to the Wrong Customer

   Trace a stale or incorrect identifier through a record update.

   PlannedPro (planned)

5. Build an Order Follow-Up Workflow

   Look up orders, branch on status, update records and notify the right person.

   PlannedPro (planned)

Chain known API calls, introduce webhook intake, and handle service failures through supplied simulations.

1. Chain API Calls in Your Workflow

   Pass one service response into another request using known GET/POST and explicit mappings.

   PlannedPro (planned)

2. Receive Work Through a Webhook

   Inspect an incoming simulated event and identify the workflow it should start.

   PlannedPro (planned)

3. Understand What a Credential Allows

   Use a dummy credential and distinguish identity, permission and secret handling.

   PlannedPro (planned)

4. Repair a Failed Service Step

   Inspect a supplied service failure and distinguish bad input from missing permission.

   PlannedPro (planned)

5. Build a Connected Intake Workflow

   Receive an event, enrich its data through a simulated API and create a record.

   PlannedPro (planned)

Revisit every core skill with failures, repeat runs, oversight and evidence.

1. Explain a Run From Its History

   Compare two executions and trace each action back to its input and decision.

   PlannedPro (planned)

2. Retry Without Making the Problem Worse

   Separate temporary failures from invalid work and choose a bounded retry policy.

   PlannedPro (planned)

3. Recover From a Broken Run

   Work through supplied failure points with partial records and pending human work.

   PlannedPro (planned)

4. Build an End-to-End Automation

   Design a supplied business process using events, records, decisions and recovery.

   PlannedPro (planned)

5. Prove It Works and Hand It Over

   Review test evidence, ownership, alerting, approval and maintenance assumptions.

   PlannedPro (planned)