Short answer: Drop the "AssemblyAI → LeMUR Task on Transcript" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Transcript IDs transcript_ids | array | Required | Array of completed transcript ids |
Prompt prompt | string | Required | Summarize the call in 3 bullets and list action items |
Model final_model | options | Optional | Model. Options: Claude Sonnet 4.5 (best), Claude Haiku 3.5, GPT-4o |
Max Output Size max_output_size | string | Optional | Max Output Size |
{"transcript_ids": "{{trigger.transcript_ids}}","prompt": "Summarize the call in 3 bullets and list action items","final_model": "{{trigger.final_model}}","max_output_size": "{{trigger.max_output_size}}"}
{"usage": {"input_tokens": 1000,"output_tokens": 200},"response": "Summary: ...","request_id": "req_abc"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.