Skip to main content
My AI Chatbot gives you the chat window — the widget, the public bot page, and the team inbox. Your backend does the thinking. That backend can be an n8n workflow, a Make scenario, a Zapier Zap, or any HTTP service you write yourself. There is no SDK to install. Everything is plain JSON over HTTPS.

​
How a conversation works

1

A visitor sends a message

They type into your widget, your public bot page, or the in-app inbox.
2

We send the event to your webhook

Your endpoint gets a message.created event. It is signed with HMAC-SHA256 and includes a short-lived response_url.
3

You reply with Block Kit

Reply in the same request, POST to the response_url later, or call the API with a key. All three land in the same chat.

​
Three ways to send a message

Every reply is Block Kit JSON. The only difference is how you send it.

Webhook response

Return the JSON in your HTTP response. The simplest way, but you only get 10 seconds.

Response URL

POST to the response_url from the event. No key needed. Good for slow jobs.

API key

Bearer mac_live_…. Message any conversation, at any time. Never expires.
Not sure which one? Start with the webhook response. Switch to the response_url if your work might take more than ten seconds. See the comparison table.

​
What you can send

Block Kit has ten block types — text, images, files, buttons, forms, cards, dividers, status bars, and hosted pages. We also accept simple shortcuts, so this is a valid reply:
And so is this:

Quickstart

Send your first message in about five minutes.

Block reference

Every block type, every field, every limit.

Receiving events

Check signatures and handle retries safely.

No-code platforms

Setup guides for n8n, Make, and Zapier.