Point us at your API. That is the integration.
No SDK. No webhook to host. Nothing to install. Add an action step to a flow, tell it three things, and the bot answers your customers with real data from your systems.
You keep your stack. Nothing moves, nothing gets rebuilt. Hiiifive only calls what you point it at.
Three things to tell the step
Everything else is already handled. Fill these in and the step is live.
Any endpoint you own
Things the customer typed earlier drop straight into the path, the query or the body. Ask for an order number and the very next call carries it.
Reads and writes
All four are live. Read, create, replace or update, whichever your endpoint expects.
Paste the key once
Bearer tokens are stored encrypted and sent on every call. Keys that expire are refreshed by a cron job on your schedule, so the call always carries a live token. An API key in a header is just a header.
Then tell us which fields of the response matter, and the bot answers the customer with your data. That is the whole integration.
One step, start to finish
A customer asks where their order is. Your service answers. Nobody on your team touches it.
You pick the three fields that matter. The rest is ignored.
Written by you once. Sent thousands of times.
We call your API the way you require.
Some APIs cannot accept a generic call, and should not have to. Your security team requires signed requests. Your infrastructure demands mutual TLS. You verify HMAC digests, rotate credentials on your own schedule, or run a handshake nothing off the shelf understands.
For that, we build the connection to your specification, and it appears in your builder as a step only your workspace can see. Your team drags it into a flow like any other step. Underneath, every call is made exactly the way your rules demand.
Built and tested against your sandbox, maintained by us. When your API changes, the step keeps up.
Whatever your scheme signs and however it is canonicalised, we match it exactly.
Client certificates issued by you, rotated on your schedule, never leaving our vault.
Body digests and timestamps computed per call, verified against your own checks.
Visible only to your workspace. Your ops team uses it without ever seeing the plumbing.
Every call we make to you is signed
Requests carry a signature and a timestamp, and always come from the same two addresses, so your service can turn away anything else.
If your service never answers, the customer is told plainly and handed to a person. They never see a status code.
One thing to be straight about
Today the traffic goes one way: Hiiifive calls your services. There is no public Hiiifive API to build against yet. It is on the roadmap and the shape of it is still open, so if you know what you would want to call, tell us and it will steer what we build.