tres-onboarding

Automating entity onboarding requires executing sequential sub-skills for wallet uploads, data collection, and balance validation. This process validates inputs at each stage to ensure complete workflow integration while allowing you to skip steps not relevant to your specific scenario.

The automated entity onboarding process includes wallet uploads, data collection, and balance validation orchestrated in a defined sequential order. It validates input at each stage to ensure completeness and allows flexibility to skip steps not relevant to your specific ledger management scenario.

Yes, finance automation onboarding workflows require the Tres Finance MCP connector and all associated sub-skills to be available. The orchestration process depends on this connector to execute sequential processes and validate inputs at each stage successfully.

Yes, you can skip steps during the entity onboarding flow that are not relevant to your scenario. The automated process is designed with flexibility to accommodate different workflows while still executing necessary sub-skills sequentially to ensure completeness.

The best way to start a full onboarding flow for transaction analysis is to initiate the process with a command like 'start onboarding' or 'run full onboarding flow'. This triggers sequential execution of sub-skills including wallet uploads, data collection, and balance validation.

You should not use automated onboarding for entity management if the required MCP connector or necessary sub-skills are unavailable in your environment. Additionally, if your scenario requires a non-sequential workflow, the defined execution order may not fit your specific needs.