A chatbot API integration that books, orders and confirms first

Yes, if your store or order system has an API that creates orders. You add an action such as place_order that sends the product, the quantity and the customer's details, and switch on Requires approval so the AI reads the order back before sending it. Risolva has no ready-made Shopify or WooCommerce connection, so the chatbot API integration points at your own endpoint.

It reads the action's When to use text, which becomes the AI's description of that tool. A specific cue such as “Use when a patient wants to book or move a visit” works far better than a vague label. Before the call runs, the AI asks the customer for any required parameter it doesn't have yet and checks it against your constraints.

Yes. Secrets are encrypted at rest and write-only, so once saved they can be replaced but not read back, and they're inserted into headers or the body as {{secret:name}} when the call is made. For web chat, Runs in host page lets the call run in the visitor's browser with your site's own login, so that token never reaches Risolva.

The call stops at the action's timeout, from 1 to 120 seconds and 15 by default. When a chatbot API integration call fails, the AI gets the failure back instead of a result, so it can tell the customer and offer a teammate. Failed and timed-out calls show in the action's history with their inputs and response, and don't count toward Max calls per conversation.

Yes. With Send it as a file, an action delivers a PDF or image from your API, whether the response body is the file, a base64 field or a link Risolva downloads (a file body or a download is capped at 16 MB). It goes out as an attachment in the same chat, with your filename and caption template. On WhatsApp, the 24-hour reply window still applies.

Google Sheets (read a range, append rows, update cells, create a spreadsheet), Google Docs (create, read, append, insert text) and Google Meet (create or look up a meeting) on a connected Google account, plus Send email, which needs no account. Order systems, calendars and help desks connect through a chatbot API integration to your own endpoint.

Yes. Signed-in user only hides an action unless your website has verified the web chat visitor with a signed JWT or HMAC user hash, and unverified visitors are asked to sign in. Auto-filled values like the verified email or customer phone go into the request directly, so the AI can't be talked into using someone else's details.

Yes. With a connected Google account, an action can read a range, append rows, update cells or create a spreadsheet, for example to keep a simple order or booking log. It's a built-in operation, so there's no endpoint of your own to host.

There's no Zapier or Make app. A custom action can POST to any public URL, though, including a webhook URL those tools give you, with the details the AI collected in the request body. Test it with a few real calls during onboarding before you rely on it.