Custom systems
Connect your own system to Cuego via REST and webhooks
Running custom software or a system not listed here? Cuego retrieves your data via your own endpoints.
Cuego AI agent
- Understand the questionWhat is this about and what does the customer really want to know.
- Gather contextOrder, customer data and earlier conversations from your own systems.
- Prepare the answerAn answer that holds up, with the follow-up action included.
- Get it doneReturn filed, ticket updated, queued for your approval.
Many companies run something that appears in no integration list. A custom order system, an industry-specific package, an ERP built to measure years ago. That system often holds exactly the information customers ask about, and that is precisely where a standard integration stops.
With the REST integration you point Cuego at your own endpoints. You specify which address Cuego may query and with which authentication, and Cuego uses that response in the conversation the way it would use a Shopify or Magento response. In the other direction, webhooks let your system react to what happens in Cuego.
What an integration is worth depends on what your system returns. If it returns an order number with status and date, Cuego can answer delivery questions. If it only returns a customer ID, recognition is as far as it goes. That is the first thing we walk through together.
The context that comes with it
This information already exists somewhere
Cuego doesn't copy your system. This data comes in the moment a customer gets in touch about it, and moves back into the background afterwards.
Any endpoint you expose yourself over HTTPS
Authentication via API key, bearer token or basic auth
Outgoing webhooks from Cuego to your system
The fields you decide on, because your endpoint determines the response
The integration in motion
1. The question comes in
Cuego only knows what the message says
A customer gets in touch. At that point Cuego knows nothing beyond what the message says: a name, an address and a question. Everything that makes the answer complete still sits in REST API & webhooks.
Register a return for order #8124
Questions that answer themselves
With that data in place, nobody has to go looking. This is what can happen next.
Our order system is custom-built
As long as the system has an address Cuego may query, an order can be looked up and appear in the conversation.
We want data from an industry-specific package
Many industry packages have an API that is rarely used. It is usually enough to retrieve customer data and statuses.
Our system needs to act when a ticket closes
Via a webhook Cuego sends that event to your endpoint, so your own process can react to it.
We want to know first whether it is possible
Show what your endpoint returns and we will say which questions can be answered with it. That is a shorter conversation than an implementation project.
How it works
How to connect your own system
You provide the address of your endpoint, how Cuego should authenticate and a sample response. Based on that we determine which fields are usable for orders, customers or statuses. You then configure the integration under Settings, Integrations. If you have no API at all, that is the first thing to build, and that is work on your side.
FAQ
Frequently asked questions
Then there is nothing to connect to. Some packages have an API that is not advertised, so it is worth asking your supplier before writing it off.
See also
Keep exploring
Everything in Cuego connects. Discover the modules, solutions and integrations that belong with this.
Your Cue to Go.
Everything around your customer. Together.
The Customer Contact Platform where conversations, customer data, knowledge, workflows, people and AI come together. Book a 30-minute demo and see it against your own situation.
30-minute demo · then we set it up together
Rather look for yourself first? Take the free website scan