Automations
Last updated September 21, 2026
Automations let Matruno react to known legal-work events through workflow-owned logic, Temporal activities, inbox monitoring, webhooks, and scheduled review jobs.
What automation means here#
In Matruno, automation is not a separate no-code automation product. It is workflow-owned behavior that can be triggered by matter creation, document processing, inbox monitoring, scheduled follow-up review, inbound webhooks, outbound webhooks, external tool calls, and Temporal workflows.
The database includes Automation and AutomationExecutionLog records, and the Temporal layer includes automation execution workflows and activities.
Keep automation subordinate to legal workflow#
Automations should start or accelerate legal workflow steps, not bypass the matter/workflow/task model or attorney-review gates. If automation changes a matter, creates a task, calls a tool, sends a notification, or generates a legal document, the result should be visible in matter history, task state, webhook delivery records, or execution logs.
Real trigger surfaces#
Implemented or scaffolded trigger surfaces include:
- matter creation in auto execution mode
- workflow start and advance routes
- document upload and document processing workflows
- inbox monitoring and email processing workflows
- daily follow-up review workflow
- inbound webhooks with idempotency handling
- outbound webhook delivery queue
- external tool execution through Temporal-backed traces
These surfaces can support legal intake from email or document upload. They are not court-feed or docket automations.
No universal connector claim
The repo includes specific integration surfaces. Do not describe Matruno as able to connect anything.
Was this helpful?