Creating Automations
FluentCase automations help you automate repetitive tasks by automatically creating tasks and events based on triggers.
Before You Start
Review Automation Overview to understand:
- How automations work
- Trigger types
- Action types
- Limitations
Creating an Automation
Basic Steps
- Go to Settings → Automations
- Click + New Automation
- Fill in automation details:
- Name - Descriptive name
- Trigger Type - What triggers it
- Actions - What it does
- Scope - Which matters
- Click Save
Automation Name
Choose a clear, descriptive name:
Good names:
- “Create MSC prep task when MSC scheduled”
- “Create follow-up task when demand sent”
- “Schedule status call 30 days after intake”
Poor names:
- “Automation 1”
- “Task creator”
- “Auto”
Trigger Types
Tag-Based Triggers
Automation runs when a specific tag is added to a matter.
Configuration:
- Select Trigger Type: Tag Added
- Select Tag: Choose the tag
- Example: Tag “Demand Sent”
Use cases:
- Tag “MSC Scheduled” → Create prep tasks
- Tag “Settlement Reached” → Create closing tasks
- Tag “New Client” → Create intake tasks
Description-Based Triggers
Automation runs when specific text appears in an activity description.
Configuration:
- Select Trigger Type: Description Contains
- Enter Text to Match: Text to look for
- Example: “demand letter sent”
Use cases:
- “deposition scheduled” → Create prep tasks
- “medical records received” → Create review task
- “settlement offer” → Create review task
Matching rules:
- Case-insensitive (matches “Demand” and “demand”)
- Partial match (matches “demand letter sent to insurance”)
- Exact phrase match
Actions
Create Task Action
Automatically create a task when triggered.
Configuration:
- Click + Add Action
- Select Create Task
- Fill in task details:
- Task Title - Task name
- Description - Task description
- Assigned To - Who gets the task
- Due Date - When it’s due
- Priority - Task priority
- Click Save
Task Title: Use descriptive titles:
- “Prepare for MSC”
- “Review medical records”
- “Follow up on settlement offer”
Assigned To options:
- Attorney Responsible - Lead attorney
- Attorney Handling - Handling attorney
- Paralegal Handling - Assigned paralegal
- Specific User - Specific person
- Unassigned - No one (team can claim)
Due Date options:
- Same Day - Day of trigger
- 1 Day After - Next day
- 3 Days After - 3 days later
- 1 Week After - 7 days later
- 2 Weeks After - 14 days later
- 1 Month After - 30 days later
- Custom - Specific number of days
Create Event Action
Automatically create a calendar event when triggered.
Configuration:
- Click + Add Action
- Select Create Event
- Fill in event details:
- Event Title - Event name
- Description - Event description
- Calendar Category - Category of event
- Date - When it occurs
- Duration - How long
- Attendees - Who attends
- Click Save
Event Title:
- “Status call with client”
- “Internal case review”
- “Deadline reminder”
Date options:
- Same Day - Day of trigger
- Days After - X days after trigger
- Specific Date - Exact date
Multiple Actions
Add multiple actions to one automation:
- Click + Add Action again
- Configure second action
- Repeat as needed
Example: Trigger: Tag “MSC Scheduled” Actions:
- Create task “Prepare MSC brief” (7 days before)
- Create task “Prepare client for MSC” (3 days before)
- Create event “MSC preparation meeting” (2 days before)
Automation Scope
Matter Type Scope
Limit automation to specific matter types:
All Matter Types:
- Automation runs for any matter
- Use for general workflows
Specific Matter Types:
- Workers’ Compensation only
- Personal Injury only
- Employment only
- etc.
Configuration:
- Select Scope: Specific Matter Types
- Check matter types to include
- Click Save
Firm-Wide vs. Personal
Firm-Wide Automations:
- Created by administrators
- Apply to all users
- Standardize workflows
Personal Automations:
- Created by individual users
- Only apply to your matters
- Customize your workflow
Testing Automations
Test Before Activating
Always test new automations:
- Create automation
- Set to Inactive
- Create test matter
- Trigger the automation manually
- Verify actions occur correctly
- Activate automation
Manual Trigger
Test without waiting for real trigger:
- Open a matter
- Go to Automations tab
- Click Run Automation
- Select automation to test
- Click Run
- Check that actions occurred
Managing Automations
Editing Automations
- Go to Settings → Automations
- Click on automation
- Click Edit
- Make changes
- Click Save
Note: Changes apply to future triggers only, not past actions.
Activating/Deactivating
Turn automations on or off:
- Go to Settings → Automations
- Find automation
- Toggle Active switch
- Inactive automations don’t run
Deleting Automations
- Go to Settings → Automations
- Click on automation
- Click Delete
- Confirm deletion
Note: Deleting automation doesn’t delete tasks/events it created.
Automation Examples
See Automation Examples for detailed examples of common automations.
Best Practices
Naming
- Descriptive names - Explain what it does
- Include trigger - Mention what triggers it
- Include action - Mention what it creates
Triggers
- Specific tags - Use specific, unique tags
- Unique phrases - Use distinctive text for description triggers
- Avoid common words - Don’t trigger on “the” or “and”
Actions
- Realistic due dates - Give enough time
- Appropriate assignment - Right person for the task
- Clear descriptions - Explain what needs to be done
- Useful priorities - Mark urgent tasks as high priority
Testing
- Test first - Always test before activating
- Monitor initially - Watch for issues after activation
- Adjust as needed - Refine based on results
- Get feedback - Ask team if automations are helpful
Maintenance
- Review regularly - Quarterly review of all automations
- Remove unused - Delete automations no longer needed
- Update for changes - Adjust when workflows change
- Document purpose - Note why automation exists
Troubleshooting
Automation Not Triggering
Possible causes:
- Automation inactive
- Wrong trigger text
- Scope doesn’t include matter type
- Recursion prevention
Solutions:
- Verify automation is active
- Check trigger configuration
- Verify matter type in scope
- Check if automation already ran
Wrong Actions Created
Possible causes:
- Incorrect action configuration
- Wrong assignment
- Wrong due date calculation
Solutions:
- Review action configuration
- Test with sample matter
- Adjust settings
- Delete incorrect tasks/events