Skip to content
← Back to documentation
Technical Reference

MyCase

Automate legal case management workflows with MyCase. Create and manage cases, clients, companies, events, tasks, time entries, documents, and more. Get notified when cases, events, people, companies, or leads are added or updated.

CategoryOther
AuthenticationOAuth 2.0
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect MyCase with Flows360

Automate legal case management workflows with MyCase. Create and manage cases, clients, companies, events, tasks, time entries, documents, and more. Get notified when cases, events, people, companies, or leads are added or updated.

Use the MyCase connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 37 actions and 5 triggers.

Available actions

  • Create Case
  • Create Case Stage
  • Create Company
  • Create Custom Field
  • Create Document
  • Create Event
  • Create Expense
  • Create Lead
  • Plus 29 additional declared actions.

Available triggers

  • Case Added or Updated
  • Event Added or Updated
  • Person Added or Updated
  • Company Added or Updated
  • Lead Added or Updated

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: MyCase
  • Package: @activepieces/piece-mycase-piece@0.1.7
  • Exact artifact digest: sha256:106fc7171cdf73491c936f73e6094a7db9676246f2f0ed7b3109d4961e775494
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Case (create_case), Creates a new case in MyCase Classification: read.
  • Create Case Stage (create_case_stage), Creates a new case stage in MyCase Classification: read.
  • Create Company (create_company), Creates a new company in MyCase Classification: read.
  • Create Custom Field (create_custom_field), Creates a new custom field in MyCase Classification: read.
  • Create Document (create_document), Creates a new document in MyCase Classification: read.
  • Create Event (create_event), Creates a new event in MyCase Classification: read.
  • Create Expense (create_expense), Creates a new expense in MyCase Classification: read.
  • Create Lead (create_lead), Creates a new lead in MyCase Classification: read.
  • Create Location (create_location), Creates a new location in MyCase Classification: read.
  • Create Note (create_note), Creates a new note for a case, client, or company in MyCase Classification: read.
  • Create Person (Client) (create_person), Creates a new individual client (person) in MyCase Classification: read.
  • Create Practice Area (create_practice_area), Creates a new practice area in MyCase Classification: read.
  • Create Referral Source (create_referral_source), Creates a new referral source in MyCase Classification: read.
  • Create Task (create_task), Creates a new task in MyCase Classification: read.
  • Create Time Entry (create_time_entry), Creates a new time entry in MyCase Classification: read.
  • Create Call (create_call), Creates a new call in the call log in MyCase Classification: read.
  • Update Case (update_case), Updates an existing case in MyCase Classification: read.
  • Update Company (update_company), Updates an existing company in MyCase Classification: read.
  • Update Person (Client) (update_person), Updates an existing individual client (person) in MyCase Classification: read.
  • API Request (make_request), Makes a raw HTTP request to the MyCase API Classification: read.
  • Find Case (find_case), Searches for cases with optional filters Classification: read.
  • Find Call (find_call), Searches for calls with optional filters Classification: read.
  • Find Case Stage (find_case_stage), Searches for case stages with optional filters Classification: read.
  • Find Company (find_company), Searches for companies with optional filters Classification: read.
  • Find Location (find_location), Searches for locations with optional filters Classification: read.
  • Find People Group (find_people_group), Searches for people groups with optional filters Classification: read.
  • Find Person (Client) (find_person), Searches for clients (people) with optional filters Classification: read.
  • Find Practice Area (find_practice_area), Searches for practice areas with optional filters Classification: read.
  • Find Referral Source (find_referral_source), Searches for referral sources with optional filters Classification: read.
  • Find Staff (find_staff), Searches for staff members with optional filters Classification: read.
  • Find or Create Case (find_or_create_case), Finds a case by name or creates a new one if it does not exist Classification: read.
  • Find or Create Case Stage (find_or_create_case_stage), Finds a case stage by name or creates a new one if it does not exist Classification: read.
  • Find or Create Company (find_or_create_company), Finds a company by name or creates a new one if it does not exist Classification: read.
  • Find or Create Location (find_or_create_location), Finds a location by name or creates a new one if it does not exist Classification: read.
  • Find or Create Person (Client) (find_or_create_person), Finds a person by first and last name or creates a new one if not found Classification: read.
  • Find or Create Practice Area (find_or_create_practice_area), Finds a practice area by name or creates a new one if it does not exist Classification: read.
  • Find or Create Referral Source (find_or_create_referral_source), Finds a referral source by name or creates a new one if it does not exist Classification: read.

Trigger contracts

  • Case Added or Updated, webhook.
  • Event Added or Updated, webhook.
  • Person Added or Updated, webhook.
  • Company Added or Updated, webhook.
  • Lead Added or Updated, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

AuthenticationOAuth 2.0
Supported objects42
Supported actionsNot published
Triggers5

Authentication

Authentication method: OAuth 2.0

Authentication profiles

connection · oauth2

Supported objects

ObjectReadWriteNotes
Create Case Yes No Creates a new case in MyCase
Create Case Stage Yes No Creates a new case stage in MyCase
Create Company Yes No Creates a new company in MyCase
Create Custom Field Yes No Creates a new custom field in MyCase
Create Document Yes No Creates a new document in MyCase
Create Event Yes No Creates a new event in MyCase
Create Expense Yes No Creates a new expense in MyCase
Create Lead Yes No Creates a new lead in MyCase
Create Location Yes No Creates a new location in MyCase
Create Note Yes No Creates a new note for a case, client, or company in MyCase
Create Person (Client) Yes No Creates a new individual client (person) in MyCase
Create Practice Area Yes No Creates a new practice area in MyCase
Create Referral Source Yes No Creates a new referral source in MyCase
Create Task Yes No Creates a new task in MyCase
Create Time Entry Yes No Creates a new time entry in MyCase
Create Call Yes No Creates a new call in the call log in MyCase
Update Case Yes No Updates an existing case in MyCase
Update Company Yes No Updates an existing company in MyCase
Update Person (Client) Yes No Updates an existing individual client (person) in MyCase
API Request Yes No Makes a raw HTTP request to the MyCase API
Find Case Yes No Searches for cases with optional filters
Find Call Yes No Searches for calls with optional filters
Find Case Stage Yes No Searches for case stages with optional filters
Find Company Yes No Searches for companies with optional filters
Find Location Yes No Searches for locations with optional filters
Find People Group Yes No Searches for people groups with optional filters
Find Person (Client) Yes No Searches for clients (people) with optional filters
Find Practice Area Yes No Searches for practice areas with optional filters
Find Referral Source Yes No Searches for referral sources with optional filters
Find Staff Yes No Searches for staff members with optional filters
Find or Create Case Yes No Finds a case by name or creates a new one if it does not exist
Find or Create Case Stage Yes No Finds a case stage by name or creates a new one if it does not exist
Find or Create Company Yes No Finds a company by name or creates a new one if it does not exist
Find or Create Location Yes No Finds a location by name or creates a new one if it does not exist
Find or Create Person (Client) Yes No Finds a person by first and last name or creates a new one if not found
Find or Create Practice Area Yes No Finds a practice area by name or creates a new one if it does not exist
Find or Create Referral Source Yes No Finds a referral source by name or creates a new one if it does not exist
Case Added or Updated Yes No webhook trigger declared by the pinned package.
Event Added or Updated Yes No webhook trigger declared by the pinned package.
Person Added or Updated Yes No webhook trigger declared by the pinned package.
Company Added or Updated Yes No webhook trigger declared by the pinned package.
Lead Added or Updated Yes No webhook trigger declared by the pinned package.

Triggers

Case Added or Updated · Webhook

Triggers when a case has been added or updated

Event Added or Updated · Webhook

Triggers when an event has been added or updated

Person Added or Updated · Webhook

Triggers when a person has been added or updated

Company Added or Updated · Webhook

Triggers when a company has been added or updated

Lead Added or Updated · Webhook

Triggers when a lead has been added or updated

Setup

Setup

  1. Add the MyCase connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-mycase-piece@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 37 actions and 5 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required MyCase connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-mycase-piece@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.