Integrations
Three ways to plug Leadiosa into the rest of your stack. Pick whichever matches the shape of the problem.
Overview
Push every event we generate to your own backend. HMAC-signed; built-in retries.
Pull and push the same data the dashboard sees. Bearer-token auth, JSON in/out.
Two-way bridge — Leadiosa conversations as Rocket.Chat channels.
Operator notifications in Slack, with reply-from-Slack. On the roadmap.
Rocket.Chat
The Rocket.Chat bridge mirrors each Leadiosa conversation into a Rocket.Chat channel, lets operators reply from either surface, and keeps both sides in sync in real time.
- Configure under
Settings → Integrations → Rocket.Chat: host URL, bot token, default channel. - Each new Leadiosa conversation creates a channel named after the contact.
- Operators with Rocket.Chat-only access can reply there; messages flow back to the visitor through Leadiosa.
- Internal notes in Leadiosa become threaded replies in Rocket.Chat — operator-only.
Webhook quickstart
Register a delivery URL under Settings → Integrations → Webhooks. A shared secret is generated for you — store it somewhere you can read on the receiving end.
import crypto from "crypto";
app.post("/leadiosa-webhook", express.raw({ type: "*/*" }), (req, res) => {
const signature = req.header("X-Leadiosa-Signature");
const expected = crypto
.createHmac("sha256", process.env.LEADIOSA_WEBHOOK_SECRET)
.update(req.body)
.digest("hex");
if (signature !== expected) return res.status(401).end();
const event = JSON.parse(req.body.toString());
// handle event.type ...
res.status(200).end();
});See Webhooks for the full event catalogue, retry behaviour, and example payloads.
REST API quickstart
Generate an API token under Settings → API → Tokens. Tokens are scoped to one workspace; rotate them from the dashboard.
curl https://leadiosa.com/api/v1/conversations \ -H "Authorization: Bearer $LEADIOSA_TOKEN"
See REST API for the resource map and the full endpoint reference.