Integration
Connect Laposta to Human Approval - HITL Platform
When something happens in Laposta, your agent does the next thing in Human Approval - HITL Platform. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Laposta and Human Approval - HITL Platform to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Laposta and Human Approval - HITL Platform
Triggers and actions 3 triggers ยท 11 actions
Trigger
A New Relation Has Been AddedTriggers when een new relation has been added to the list in your Laposta account.
Trigger
A Relation Has Been EditedTriggers when a relation of your Laposta list has been edited.
Trigger
A Relation Has Been RemovedTriggers when a relation of your Laposta list has been removed.
Action
Add or Edit a RelationEdit an existing relation, or add a new relation, in your Laposta list.
Action
Delete RelationDelete an existing relation.
Action
Add LoopCreate a new approval loop (a queue of approvers). POST /loops
Action
Create Decision RequestSends a decision request to the HITL system and waits for a human response via callback
Action
Delete LoopDelete an approval loop. DELETE /loops/{id}
Action
Delete RequestCancel a pending decision request. DELETE /requests/{id}
Action
Find Request StatusFind the current status and details of a HITL request
Action
Get LoopGet an approval loop by ID. GET /loops/{id}
Action
List LoopsList the user's approval loops. GET /loops
Action
List RequestsList the user's decision requests. GET /requests
Action
Update LoopUpdate an approval loop's settings. PUT /loops/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.