Build it
What do you want Qwilr and Temi 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 Qwilr and Temi
Triggers and actions 3 triggers ยท 5 actions
Trigger
Project AcceptedTriggers when a project is accepted.
Trigger
Project First ViewedTriggers when a project is first viewed.
Trigger
Project PublishedTriggers when a project is published.
Action
Delete Transcription JobDelete a transcribed job. DELETE https://api.temi.com/v1/jobs/{id}. Only allowed once the job's status is transcribed or failed; returns 204 on success.
Action
Get AccountFetch Temi account balance and email. GET https://api.temi.com/v1/account. Returns {balance, email}.
Action
Get TranscriptFetch the transcript text/JSON for a completed job. GET https://api.temi.com/v1/jobs/{id}/transcript?version=latest|machine, with Accept header selecting text/plain, application/json, application/msword, or application/pdf.
Action
Get Transcription JobFetch the current status and details of a submitted transcription job. GET https://api.temi.com/v1/jobs/{id}. Returns the job object (status: in_progress/transcribed/failed, web_url, duration_seconds, name).
Action
Submit Transcription JobSubmits a new transcription job.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews