Learning paths/Ship your first ProcessFlow

Ship your first ProcessFlow

Automation builder

Design one process from trigger through a safe step that uses secrets correctly.

Outcome: You can create a process step, call tf APIs in the sandbox, and store secrets in the keystore. · 9 stops · ~75 minutes

1. 1.Automations and ProcessFlow

   Open stop

   Sets the mental model for processes, steps, triggers, and executions.

2. 2.Process sandbox tf API

   Open stop

   The tf surface is how step code talks to the platform.

3. 3.Sandbox guardrails

   Open stop

   Prevents failed deploys by knowing what step code may not do.

4. 4.ProcessFlow Keystore

   Open stop

   Secrets must not live in step source; keystore is the supported pattern.

5. 5.Writing step code

   Open stop

   Entry point to recipes; use it as a map, not a cover-to-cover read.

6. 6.Data transformation and mapping

   Open stop

   Most first flows reshape payloads between systems.

7. 7.Webhook calls

   Open stop

   Outbound HTTP is the common first integration style.

8. 8.Data validation and sanitization

   Open stop

   Fail fast on bad input before you call external systems.

9. 9.Integration connectors in steps

   Open stop

   Shows how steps invoke configured integrations instead of raw HTTP only.

Start path