Current limits
The current product should be judged by how well it handles one visible governed workflow, not by how broad a connector matrix can be claimed on paper.
Salesforce leads the demo story
Salesforce is the first fully simulated connector today.
Sandbox coverage varies
Other connectors have sandbox guidance and sample scenarios, but not every lane has first-class seeded simulation.
ERP and HCM stay narrow
ERP, finance, and HCM connectors still need customer-owned sandboxes for meaningful validation.
Where simulation is strongest
Simulation workspaces are the cleanest way to explain the product before credentials are involved.
A deterministic first story is still the preferred route into a real evaluation.
Not every connector has the same simulation depth yet.
Where connector depth is still growing
Public connector pages and app bring-up flows may exist before all lanes have equally mature seeded experiences.
A connector being listed does not mean every adjacent workflow is equally production-ready.
Readiness labels on the connector matrix should be treated as the source of truth.
How to keep the first live workflow safe
The first rollout for every connector should stay intentionally narrow until real-world proof is established.
Use one least-privilege identity, narrow object scope, and visible operator review before widening automation.
Treat beta lanes as observed experiments rather than finished platforms.