automation-onboarding

To scaffold a new Tumai automation, provide the automation id, name, category, variables, and dependencies. The process auto-generates all 7 required artifacts, including catalog entries and JSON Schema, ensuring production-grade completeness.

Onboarding a new automation requires generating 7 artifacts: catalog entries, JSON Schema, config questions, skill.md docs, icon registration, and edge connections. The onboarding process standardizes and validates the coherence of all these artifacts before deployment.

Yes, you can auto-generate JSON Schema and config questions by providing the automation variables and dependencies. The automation onboarding process uses these inputs to standardize artifact generation and validate completeness across the Tumai platform.

Yes, automation onboarding validates the completeness and coherence of all generated artifacts. It satisfies production-grade requirements by verifying that catalog entries, JSON Schema, config questions, docs, icons, and edge connections are fully consistent before deployment.

The best way to standardize catalog entries is using an end-to-end onboarding process that provides templates and guidance. This ensures consistency across all Tumai automations, reducing errors and onboarding time by validating artifact coherence.

Edge connections are required as one of the 7 core artifacts when adding an automation to Tumai. The onboarding process automatically generates and registers these connections alongside catalog entries, JSON Schema, and docs to ensure complete deployment readiness.