Plan integrations and human handover

Define connection ownership, permissions, failure recovery, and the point where a person takes responsibility.

Map each connection

  • Name the system and account owner.
  • Identify the data the workflow needs to read or change.
  • Confirm the supported connection method for the selected product.
  • Keep credentials in the appropriate server-side configuration, outside public pages and client code.

Define the handover

Decide which requests need a person, who receives them, and which conversation context they need. Include requests outside the agent's knowledge or authority, explicit requests for a person, and failed tool actions.

Agree recovery and ongoing ownership

Document how connection failures are reported, who can reconnect accounts, and how interrupted work is reviewed. Confirm the workflow's actual capabilities with Ayroflow before connecting live business systems.