Skip to main content
Tell Lana what your customer-facing agent needs to do with another system. Lana can research the provider’s public documentation, prepare supported actions in Visito, and test their responses with your approval. This is a worked example of that workflow using Hostaway availability and stay pricing. Follow the same steps for your own use case: describe the outcome, review the proposed actions, arrange private credential entry, and check the result in Playground. Replace the provider, customer task, and test inputs with your own. You do not need to write the action schemas yourself.

Before you start

  • Select the intended business and sign in as a registered administrator with access to Lana.
  • Have authorized API access to the external system. An administrator or support operator will need to enter its credentials privately.
  • Start with a narrow test. The Hostaway example checks availability and quotes, without reservations, date blocking, or customer messages.
One integration often needs several actions. In this example: The agent combines the results during the conversation. A listing’s base price is not a quote for the requested stay.

1. Ask Lana to connect your system

Open Lana, start a chat, and describe the result in your own words. For example:
You can name the system without supplying a documentation URL. Ask Lana to use official sources and explain anything it cannot verify. If you have a specific API version or documentation link, include it. Lana reviews your business configuration and the provider documentation to identify the connection options. You can ask it to check whether a direct connection fits your workflow:
Lana can explain which requests map to Visito actions and whether your workflow needs an adapter or additional technical work.

2. Review the proposed actions

Lana prepares the actions and asks you to approve each configuration change. Review the selected business, purpose, destination, inputs, and intended effects. For this example, both actions should be read only and initially Off while authentication is missing. The example uses the action names hostaway_disponibilidad_prueba and hostaway_precio_prueba. Your names can differ. Confirm that the availability action passes real returned apartment IDs to pricing and that both use the same dates and guest count.
Lana pricing-action proposal with Approve and Reject controls.

Review the pricing action before choosing Approve or Reject. The example conversation is in Spanish; the dashboard controls are in English.

Select Reject if a proposal needs changing. Approving one action does not approve the next action or a later provider test. A saved configuration is not yet proof that the connection works.

3. Add credentials through private settings

Keep passwords, API keys, and access tokens out of the Lana chat, action instructions, and input schema. An authorized administrator or support operator must obtain the appropriate provider access token and save it in the action’s private Authentication settings. Follow the provider’s access process: an API key and an access token are not necessarily interchangeable. For bearer authentication in the HTTP action editor, enter the token without the Bearer prefix. Save the access token in the private authentication settings of both actions. If you need help obtaining the token or configuring authentication, contact your administrator or Visito Support. After saving authentication, return to the same chat:
Use future dates appropriate to your own test. Lana can verify whether authentication is configured without receiving the token in the chat.

4. Approve the provider tests

Lana proposes Playground only activation and each external action test separately. Review the action, dates, guests, and apartment ID before approving. Playground-only actions still contact the real provider. In this walkthrough, the approved requests retrieve availability and calculate quotes. They do not reserve an apartment. Ask Lana to summarize the availability response, identify the returned apartment IDs, and use those IDs for pricing. If a response is incomplete or clipped, ask it to inspect the saved execution and diagnostic before proposing another request.
Lana reports four available apartments and two stay totals, with accommodation and cleaning charges.

Lana's completed direct tests: availability and two stay quotes, with both actions limited to Playground.

Review the availability and pricing results, including any missing information or errors. Once the actions return the expected results, check the full guest conversation in Playground.

5. Test the guest conversation in Playground

Open Playground for the same business to check how your agent uses the actions during a conversation. Start without stay details:
The agent should ask for arrival, departure, and number of guests before consulting Hostaway. Then send:
Check the availability and pricing receipts and compare them with the answer. Here is an example quote for two nights:
Playground shows the first two available apartments with stay totals of MXN 7,436 and MXN 11,273.

Playground answer using the Lana-created actions, with stay totals and a breakdown of charges.

These sample prices illustrate the response. Availability and prices depend on the requested dates, guest count, and current Hostaway rates. Availability and pricing queries do not create a reservation.

6. Change the stay details

Check that the agent obtains fresh results rather than repeating the earlier quote:
The agent should check availability again and request new prices for the same apartment IDs. In this example, the updated totals are MXN 6,700 and MXN 9,451, including the returned additional-guest and cleaning charges.
Playground confirms availability for the revised stay and shows new totals of MXN 6,700 and MXN 9,451.

Changed dates and guest count produce new totals from Hostaway for the same apartments.

Compare the new answer with the latest action results. Confirm that each displayed total uses the correct apartment, dates, guest count, currency, and included charges.

If something does not work

Keep the actions Playground only while you review the answers. When you are ready, confirm their business scope and switch them to Active for use in customer conversations. Choose Off to pause future calls.

Adapt the example to your own workflow

Start with this prompt and replace the bracketed details:
Use the customer task to decide which actions to ask Lana to investigate: As with the Hostaway example, pass the IDs returned by one action into the next and keep shared inputs consistent. Test missing information first, then a complete request, then changed inputs. Compare each answer with the latest action results before activating the workflow. The provider needs an API and an access method Visito supports. Each workflow has its own actions and access requirements; the two Hostaway actions are specific to this example. Ask Lana to explain the proposed connection and whether it needs additional actions, an adapter, or technical assistance.

Lana overview

Review access, approvals, progress, downloads, and credits.

Test your agent

Learn how to inspect the guest conversation and its recorded results in Playground.