Connect · Integration layer
When one system moves, the others follow.
Connect is how Matterline makes your existing applications exchange information and trigger coordinated workflows. A new enquiry, a signed agreement or a document upload is entered once, and the right records, tasks and messages follow according to rules you agree.
PricingA$1,500 setup · A$190/month

A worked example
A new enquiry, start to finish.
Illustrative example. Your version is designed around your own systems and rules.
- 01
An enquiry arrives
A prospective client completes the form on your website.
- 02
It is recorded in your CRM
A contact and matter or opportunity is created, with the source and answers attached.
- 03
The right person is told
The practitioner for that practice area is notified in email, Teams or Slack.
- 04
A follow-up task is created
With a due time, so nothing depends on memory.
- 05
An acknowledgement is sent
The client receives an approved reply with a booking link.
- 06
Your rules decide what’s next
Reminders, escalation if no one responds, or a consultation booking, as agreed in solution design.

See it work
Four moments in a matter.
Choose a scenario to see how a connected practice responds. Every step is configured per practice, and only with tools that support it.
An enquiry arrives through the website at 9:12 pm
No change
No change
No change
No change
No change
Illustrative example, not a live connection to any system.
What makes an integration possible
We tell you the limits before you commit.
No integration works with everything. Before quoting, we check each of the following for every system involved.
An API or webhooks
Whether the system lets other software read and write its data, and which records it exposes.
Your subscription tier
Some vendors only open their API on higher plans. We tell you if an upgrade is needed.
Permissions you grant
We ask for the least access each workflow needs, and list every connection in an integration inventory.
Scope and approval points
Which steps are automated, which wait for a person, and what happens if a system is unavailable.
How we connect
Four integration patterns.
Direct API connection
Two-way connection to systems that offer a documented API.
Webhooks
A system announces an event the moment it happens, and the workflow responds.
How webhooks workIntegration platforms
Tools such as Microsoft Power Automate, Make or Zapier where they suit your stack and budget.
Scheduled sync or managed fallback
Where no API exists, a regular import or a clear manual step, with the limits stated in writing.
Systems we commonly work with
The tools practices already use.
Categories we regularly connect. Specific products are confirmed in your Diagnostic; listing a category does not imply a partnership with any vendor.
Practice-management systems and CRMs
Legal and migration practice-management software and general CRMs that offer an API.
Email and calendars
Microsoft 365 (Outlook, Exchange) or Google Workspace (Gmail, Calendar).
Document storage
SharePoint, OneDrive or Google Drive, organised by client and matter.
E-signature
Services such as DocuSign or PandaDoc, with a full audit trail.
Payments and accounting
Stripe for card deposits; Xero for reconciliation.
Messaging
WhatsApp Business Platform (through an approved provider), website chat and SMS.
Team chat
Microsoft Teams or Slack for notifications, tasks and digests.
Forms and booking
Website forms, Calendly or Microsoft Bookings.
When something fails
Failures are expected, and handled.
Automatic retries
If a system is briefly unavailable, the step is retried before anyone is alerted.
A person is alerted
If it still fails, we are alerted and the item is queued, not lost.
A one-business-day target
Our target for resolving failed runs, with the fix recorded in the run log.
Connect pricing
Prices in AUD, excluding GST. Larger or custom integrations are quoted separately after the Diagnostic.
Start with a Practice Diagnostic.
A few short questions, then a free 30-minute conversation. You’ll leave knowing what’s worth connecting or automating first.