Integrations
Connect Clio Manage and Zapier, and review upcoming practice-system connections.
Workspace admins manage available connections under Settings → Integrations. API keys are managed in the adjacent API Keys section.
Integrations apply to the workspace, not to one matter at a time. There are no per-matter integration grants. Private Clara conversations and unshared drafts stay outside integration access.
API keys and Zapier require a Pro or Enterprise plan. The public API is currently a beta interface, so validate your workflow before relying on it in production.
Clio Manage
Clio Manage can import clients and matters into Ardela.
- Open Settings → Integrations and connect Clio.
- Complete Clio's consent flow.
- Choose an accountable Ardela member as the owner of newly imported matters.
- Choose the initial audience: Only you, or one workspace group.
- Save the creation policy, then run the first sync.
A connection without a saved creation policy does not import automatically. Existing Ardela matters keep their identity and ownership. Clio Open, Pending, and Closed map to the same statuses in Ardela.
Pause imports if you need to stop creating new matters without disconnecting. Disconnect disables the connection and clears stored credentials.
Changing the configured owner or audience applies to future imports, not to matters already in Ardela. After you change local field mappings, run a full sync so retained connections can update unchanged Clio records.
Zapier
Zapier connects to Ardela with an API key. There is no separate OAuth connection in Ardela.
- Open Settings → Integrations and select Set up on Zapier
- Continue to API Keys
- Create a key with
read:recordings - Add
write:recordingsonly if the Zap must mark work as filed - Copy the key when it is shown and paste it into the Ardela app in Zapier
Keep the key in Zapier's connection settings. Do not place it in a browser script, document, or source repository.
The integration can use completed-recording data and record a filing checkpoint after a separate destination step succeeds. Ardela does not upload to the destination simply because a recording is marked filed.
Coming soon
The settings screen currently lists these connections as coming soon:
- Microsoft 365
- Actionstep
Do not plan a rollout around their connect or sync controls until the relevant card is marked available in your workspace.
Custom integrations
For a direct system integration, use the REST API and webhooks. Treat webhooks as notifications and retain a recovery process for missed or delayed delivery.