◇ Could this help me?
Yes, with the connection scope handled far more carefully than the video suggests. Prebuilt workflows for routine small business finance and operations work are a reasonable use of this tooling, and the demonstration being run against test accounts rather than live ones is the right instinct even though it is not presented as a safety point. The part to insist on is permissions: connecting accounting, payments, and customer systems to an assistant grants reach over money and records, so read-only access is the default and anything that moves funds or alters records should require a person. Financial output also needs verification against the source rather than being trusted because it is formatted confidently. General practice for small business operations, and the creator's own caveat that these are low-complexity automations is a fair expectation to set.
I am considering connecting my accounting, payments, and customer systems to an assistant for routine reporting. Before anything is connected, go through each system and tell me exactly which permissions a read-only connection would grant, what additional permissions would be needed for each task I want, and which of those tasks require the ability to change records or move money. Recommend the narrowest set that still does the job, and tell me what I should refuse outright. Then, for the first report I generate, tell me how to verify every figure against the source system, and which numbers would be most expensive to get wrong.