ChatFrom
In development

Connections

Connect the services your business runs on, and your chatbot and its workflows use them: they look up an order, call your own API or act through your tool server, always for the customer they are talking to.

Everything here is set up under Tools in your dashboard. Once a service is connected, the chatbot uses it when a conversation needs it, and a workflow's Tool Call step can name any of its tools. Every call shows in the conversation log.

Your APIYour own endpoints as actions, with their keys kept on our server.Your tool serverThe tools your MCP server offers, acting for the signed-in user.ShopifyOrder status with the tracking link, and return requests your store approves.

Your API

A custom action is one of your own HTTP endpoints, described once so the model knows when to call it: looking up an order, creating a ticket, booking a slot. The app makes the call for the chatbot, so your API key never reaches the model or the visitor.

  1. Under Tools, Custom actions, press Add action.
  2. Give it a name, such as get_order_status, and a description for the model that says what it does and when to use it.
  3. Choose the method and enter the URL. A {param} in the path is filled from the parameters; the others go in the query for GET, or the JSON body.
  4. List the parameters, one per line: name, type, required or optional, and a description, such as order_id, string, required, The order number.
  5. Add the headers your API needs, such as Authorization: Bearer …. A saved value shows as dots from then on and is never sent back to your browser.
  6. Save, then press Test to call it with sample values and see exactly what the model would receive.

Your tool server

If your product runs an MCP server, the chatbot can use its tools directly. Under Tools, MCP servers, add the server's name and address, and name the tools the chatbot may use; nothing else on the server is shown to the model.

Tick Send the site's signed-in user token to this server for a server your own site runs. When the page embedding the widget passes a token it signed for its user, your server receives it as X-User-Id and can act on that account and no other. In the chat apps, users link their account once to get the same, as Channels explains.

Coming soon

  • Stripe: cancel, pause or resume a subscription for a verified customer.
  • Google Sheets: a new row for every lead, booking or request.
  • Cal.com and Calendly: book, move and cancel appointments.
  • HubSpot: a new contact for every lead the chatbot takes.

Need one of these first, or another service? Tell us.