Skip to main content
Open Connectors in the dashboard sidebar to manage the systems your agent uses during conversations. Choose a Visito-maintained integration, connect your own API, or use an action hosted in Visito. Connectors catalog with installed systems in the left drawer and Add your own system at the top right.

Connector, connection, and action

For a custom API system, configure the shared connection once and add one or more actions in the same modal. After saving, the system appears once in Installed. Open it to manage its Actions and Connections. Each action keeps its own inputs, instructions, business scope, and mode. For a Visito-hosted system, name the system and define several collection actions in one modal. It appears once in Installed. Its Settings row opens a right drawer for the shared name and description; there are no API credentials. Each action keeps its own fields, scope, mode, and optional webhook delivery. A connected account does not by itself prove that an action is ready for customer conversations. Check its configuration, availability, business scope, and test results.

Choose a setup

Custom API system

Add your own system, share its authentication, and define actions to retrieve information or perform supported operations.

Visito-hosted collection

Create a named system with several collection actions, save information in Visito, and optionally configure delivery per action.

Google Sheets

Connect Google, then choose the spreadsheet, columns, and permissions for each action.

Provider integrations

Connect supported business systems such as Cloudbeds and SiteMinder using their provider-specific setup.
Channels such as WhatsApp and Webchat are configured separately. They carry the conversation; connectors provide the systems and operations the agent can use within it.

Create a custom system with two actions

  1. Select Add your own system → API-based.
  2. Name the system and enter its shared API base URL and authentication.
  3. Define the first action, then select Add action for the next one. You can create 1–20 actions in this setup.
  4. Keep the actions in Playground only while testing, then select Create system.
  5. Open the saved system’s Actions tab to edit an action or add more later.
One system with shared Bearer authentication and two actions ready to save together. See the custom API setup guide for input schemas, request formats, and examples of AI instructions.

Create a Visito-hosted system with two actions

Select Add your own system → Visito-hosted to open setup directly. Name the system, configure the first action’s instructions and fields, then select Add action for the second. Keep them in Playground only and select Create system. Add more from the saved system’s Actions page; click a saved action to open its right drawer. One named hosted system and two collection actions saved together. See the collection setup guide for fields, limits, shared settings, and optional webhook delivery.

Test and activate deliberately

Explain when each action should run and which information it needs. Choose only the businesses where it belongs. Start with synthetic data and verify both the conversation and the actual result: the API response, saved submission, or spreadsheet cells. Playground is a conversation test, not a universal dry run. API actions send real HTTP requests. Sheets writes change the configured test spreadsheet. Collection submissions are isolated from live CRM records and webhook delivery. Follow the guide for the action type you are testing.

Review Activity

Open Connectors → Activity, or View activity from a system. Filter by connector, connection, business, environment, action, and status as needed. Open an execution to inspect its parameters, response, timing, and available technical details. Activity filtered to the example CRM and Playground executions. Use Open conversation to connect the execution to the customer’s request. A completed HTTP request does not necessarily mean the intended business operation succeeded; inspect the returned result. See Test and debug actions. Developers can manage supported action configurations, run supported direct tests, and inspect executions through the Actions API. A direct API test does not prove that the agent will choose the action or supply the right arguments in conversation.