Build with Engage

Overview

Engage turns customer activity and business events into automated journeys across your connected channels.

Customer journeys often stall after the first signal. Someone asks a question, leaves a cart, misses a payment, or goes quiet, and nobody follows up because remembering the next action is somebody's job on top of their actual job. Engage is the part that remembers.

You send it two kinds of thing: who your customers are, and what they did. It matches them to workflows configured in the dashboard, and takes the next action when the moment arrives - twenty-four hours later, three days later, or whenever the workflow says.

The whole model, in four nouns

A customer is a person, identified by a phone number in E.164 format and optionally by your own id. You never have to create one explicitly — an event carrying a phone number will enrol them.

An event is something that happened: order.created, cart.abandoned, price.quoted. The type is free text and means whatever your workflows say it means.

A workflow waits for an event type and then does something — usually after a delay, usually only if the customer has not replied in the meantime. See Workflows.

A conversation is the customer thread on a connected channel. Messages your workflows send land in it, and so do the customer's replies, where the business can see and answer them.

What an API key can do

Deliberately narrow. A key issued for your integration reaches exactly two paths:

/v1/events      record what happened
/v1/customers   enrol and update people

Everything else - connecting channels, writing workflows, reading conversations, replying to a customer — belongs to a signed-in person, not to a key sitting in a server somewhere. Those endpoints are documented here too, and take a user access token instead: see Authentication. A key that leaked can record an event. It cannot read your conversations or message your customers directly.

When something happens that your server should know about, Engage calls you: see Webhooks. You do not have to poll for a customer’s reply.

Base URL

https://api.engentra.io

Every path below is relative to it. All requests and responses are JSON, and every failure comes back in the same envelope.