Qa3at × AmbactiBring Qa3at into
the flow of work.
A little less busywork with Qa3at.
Account2 capabilities+
- Get the account
Read the balance, the free hours left, and the prices
- Get the usage
Read what the last thirty days consumed, day by day
Event1 capabilities+
- Get many events
List the events sent to your hooks, the newest first
Room8 capabilities+
- Close a room
Close a room, empty it, and charge the class
- Erase the personal data of a room
Erase the names and your own user IDs of everyone who sat in a closed room, and kill its open link. Attendance minutes stay, because they were already billed.
- Get a room
Read a room: who is in it now, and what it left behind
- Get the attendance of a room
Read who entered a room, when, and for how long
- Get many rooms
List the rooms this key opened, the newest first
- Get the recording of a room
Read the download link of the recording once it is ready
- Get the transcript of a room
Read the written text of the class once it is ready
- Open a room
Open a live room with video, audio and a shared whiteboard
Ticket1 capabilities+
- Create a ticket
Mint a one-use entry link for one person
Frequently asked
questions.
What could an Ambacti integration do with Qa3at?
The documented operations include Account: Get the account; Account: Get the usage; Event: Get many events; Room: Close a room.
Could I keep a workflow read-only?
For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.
Will every action run automatically?
Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in Qa3at?
Decide which work could run on its own and which steps need your review.