Save your system's https address and key once as a Custom HTTP account, then call it from any automation with the Call another system step and keep parts of its reply. Your system can also start an automation by calling an incoming-webhook URL.
Haiya calls your system
A customer asks when her delivery arrives. The automation calls your system with her order number, saves the delivery date from the reply and sends it back in the chat.
Your system calls Haiya
When your booking system confirms a delivery slot for Wanjiru Kamau (+254712555019), it posts to a Haiya incoming-webhook URL. Haiya checks the call, finds Wanjiru by her phone number and starts the automation.
For developers
The Haiya API and webhooks cover the rest: signed business events posted to your address, and a send endpoint shaped like Meta's Cloud API.
You need its https base URL, for example https://shop.example.co.ke/api, and a key if your system asks for one.
In the other toolOn the Haiya web dashboard, open Settings → Integrations, choose Custom HTTP and pick how Haiya signs in: a bearer token, a key in a header you name, or no sign-in. The key is stored encrypted and never shown again.
In Haiya
Add the Call another system step, pick the account, then choose the method, the path and the values to send. Name the parts of the reply you want to keep.
In HaiyaRun the step's test. Haiya makes the call and shows the status and the start of the reply, so you can map the fields.
In HaiyaAdd the Incoming webhook trigger. Haiya shows its URL once: paste it into your system, add a signing secret if your system signs its calls, and say where the customer's phone number is in the body.
In Haiya and the other tool
GETPOSTPUTPATCHDELETEAuthorization: Bearer <token><a header you name>: <key>no sign-infieldsjsonforma form's answersPOST /hooks/automations/<token>signing: a secret in the URL, or an HMAC signature (hex or base64)mapping: phone (required), name, extra valuesA connected account that holds your system's https address and key. The Call another system step uses it to call your API from an automation and keep parts of the reply for later steps.
Yes. Add the Incoming webhook trigger to an automation. Haiya gives you a URL, shown once, and your system posts to it with the customer's phone number. Haiya checks the call and starts the automation.
With a bearer token, a key in a header you name, or no sign-in. The key is stored encrypted and is never shown again after you save it.
Each call has 10 seconds. If Haiya could not reach your system at all, or it answers with an error, the step takes its failed path. If the request was sent and no answer came in time, Haiya does not send it again: the run waits for a teammate to check your system, so nothing is done twice.
Not in Haiya: the account, the step and the incoming webhook are set up on screens in the web dashboard. You do need to know your system's address, paths and fields, and your system must make or accept https calls.
Start in the app, or book a demo and we will walk you through the set-up.
“…we use Haiya every day, and it has made team communication much easier.”
Cookies on this site
With your permission we use analytics cookies to see how the site is used, and advertising cookies to measure our ads. Nothing is set until you choose, and you can change your mind at any time from cookie settings at the foot of the page. Privacy policy