Creating Automations (Triggers → Actions)
Last updated: October 29, 2026
Estimated reading time: 2–3 minutes
Overview
The Automation Builder lets you set up rules that run automatically in Coperniq. Each automation follows a simple structure:
Trigger: the event that starts the automation
Conditions, if needed: Rules that must be met before the action runs
Action: what Coperniq does automatically after the trigger happens
When an event occurs → check conditions, if any → perform the action.
Triggers
A trigger is the event that starts the automation. Available triggers include:
Work Orders: Created, marked complete, status updated, or SLA violated
Projects: Created, property or status updated, phase started/completed, or phase SLA violated
Opportunities: Created, property updated, phase started/completed, or phase SLA violated
Appointments: Created, rescheduled, or opportunity appointment status updated
Calls: Created or updated
Notes: Created
Depending on the trigger, you may need to select a workflow, phase, property, or status.
SLA violated means the configured time limit for a work order or phase has been exceeded.

Conditions
Conditions determine whether the action should run after the trigger occurs. Leave them out if the action should run every time that event happens.
Select the property or filter, choose a comparison, and enter the value to check. Combine conditions using:
AND: All conditions must be met.
OR: At least one condition must be met.
For supported date properties, use Within or Not Within to check a date range.
Conditions are checked when the trigger occurs. A date condition does not create a daily scheduled check.

Understand What the Filter Checks
Some filters check the overall record rather than the specific item that triggered the automation.
For example, Work order with title checks whether a project contains a work order with that title. Combined with Note Created, it does not restrict the automation to notes posted on that particular work order
Actions
An action is what Coperniq performs when the trigger occurs and the conditions are met.
Action | Purpose |
|---|---|
Send email | Email customers or internal team members |
Send sms | Send a text message |
Update Property | Set or change a property value |
Create Project | Create a project |
Create Task or Work Order | Create work using a template |
Assign Work Order | Assign a work order to a user |
Assign Collaborators to Work Order | Assign collaborators to a work order |
Call webhook | Send an event to an external system |
Create Reminder | Create a reminder |
Create Document | Create a document using a template |
Create Form | Create a form using a template |
Run Agent | Run an AI agent; requires an AI subscription or active trial |

Access Automations
Steps:
Click the Settings icon in the bottom-left corner.
Under Process Studio, select Automations.
Review existing automations, or click + Automation.

Create an Automation
Steps:
Click + Automation.
Enter a clear Name.
Choose a Trigger.
Select the Parent Record if required (Client, Project, or Request).
Add Conditions, if needed.
Choose an Action.
Fill in all required action fields.
Click Create.

Example: Opportunity Phase Completed → Create a Project
Automatically create a project when an opportunity completes the selected sales phase and has a sales rep assigned.
Trigger: Opportunity Phase Completed → choose the phase.
Parent Record: Opportunity.
Condition: Sales Rep is not empty.
Action: Create Project → choose the workflow for the new project and complete the remaining fields.
click Create.

What happens:
When the selected phase is completed, Coperniq creates a project in the chosen workflow only if a sales rep is assigned.
Email and SMS Automations
For setup instructions, recipient options, and examples of personalizing messages with tokens, see Customizing Email and SMS Automations.
Managing Automations
You can manage automations from the Automation list.
Available options:
Enable/Disable: use the toggle switch
Click the three-dot menu (⋮) to Edit, Duplicate, or Delete an automation

Search: use the search bar to find automations quickly

Best Practices
Use descriptive automation names
Avoid duplicate or conflicting automations unless intentional
Test automations by performing the trigger once
Keep customer-facing vs internal rules separate
Review automations periodically as workflows evolve