Turn X (Twitter) conversations into API actions.
Joe answers an X DM like a colleague who knows your business. Anything your systems expose, Joe can call: reading live data before he answers and triggering actions when the customer says yes. No copy-paste, no flow builder, no morning backlog.
400 credits on us for 7 days to decide if he keeps the job.
One X (Twitter) conversation. The API work, done live.
Watch the left side: an X DM comes in. Watch the right side: API fills itself in as Joe answers. That is the whole product.
Is there a Clio free this weekend?
One automatic left: £78 Saturday to Sunday. Book it?
Yes please, pickup at 9.
Booked for Sat 09:00. Confirmation on its way.
Three steps, every time.
An X DM arrives
A customer writes in on X (Twitter), at whatever hour they like. Joe reads the whole message, not a keyword.
Joe answers and acts
He replies in your words and your prices, and does the API work in the same breath, while the customer is still there.
API is already right
Calls your endpoints with the details collected in the conversation. Nothing waits for the morning, and nothing is retyped by hand.
Real conversations, real records.
Three businesses, three messages, and what API looks like afterwards.
“Is there a Clio free this weekend?”
Joe calls your availability endpoint, quotes the live price, and posts the booking back the moment the customer says yes.
“Can I freeze my membership while I travel?”
Joe verifies the member against your API, applies the freeze through the endpoint you expose, and confirms the restart date.
“Where is my order?”
Joe fetches the tracking status from your system and answers with the real ETA instead of a template.
The record is done before the goodbye.
Calls your endpoints with the details collected in the conversation
Reads live data back and uses it in the reply
Triggers any action your systems expose
Everything Joe does on X (Twitter) → The full API integration →
X (Twitter) to API, answered.
Do I have to build a X (Twitter)-to-API flow?
No. Connect X (Twitter) and API once, then tell Joe in plain language what should happen. He decides in the conversation, so there is no flow chart to maintain when your prices or rules change.
Does every X (Twitter) message end up in API?
Only the ones your rules say should. You decide what gets recorded, what gets escalated to a person, and what needs approval before Joe acts.
What else can Joe do from X (Twitter)?
Everything he does anywhere: answer questions, book appointments, take payments, quote from your price list, and hand over to your team with the whole conversation attached. API is one of the places he can act, not the only one.
How long does this take to set up?
Connecting X (Twitter) and API takes a few minutes each. Most businesses are live, answering and acting, in about twenty minutes.
Joe's ready. Are you?
The next X (Twitter) message could already be in API.
400 credits on us for 7 days to decide if he keeps the job.