Automations
ActionConnect's no-code automation engine lets you replace repetitive manual work with rules. Automations apply to both work items and tickets.
How a rule is shaped
Every automation follows the same pattern:
Trigger → Conditions → Actions
- Trigger — the event that starts the rule (an item created, a status changed, a ticket received, an SLA timer at risk, a date reached, and so on).
- Conditions — optional filters that must be true for the actions to run (priority is high, assignee is empty, custom field equals a value, etc.).
- Actions — what happens (assign to a team, change status, add a comment, send a notification, escalate, create a follow-up item, and more).
Examples
- Ticket routing: When a ticket is created and its subject mentions "billing", then assign it to the Finance team.
- Escalation: When a ticket's first-response SLA is about to breach, then raise priority and notify the team lead.
- Project hygiene: When an item's due date passes and it is not done, then flag it and notify the assignee.
- Hand-off: When an item moves to "Ready for QA", then create a subtask for the QA team.
Starter templates
ActionConnect ships a starter template library so you do not have to build common rules from scratch. A starter automation is even seeded into every new organization at provisioning. Clone a template, adjust its conditions and actions, and enable it.
How automations run (and stay safe)
Automations execute asynchronously in the background so they never slow down the action that triggered them. They are scoped to your organization's data only, and they have loop and recursion guards — a maximum depth, a per-item run budget, and cycle de-duplication — so an automation cannot trigger itself into an infinite loop. Each run is recorded so you can audit what fired and why.
Tips
- Start with a template and make small changes.
- Add conditions to keep a rule narrowly targeted.
- Review automation run history when a rule does not behave as expected.
- Pair automations with SLAs for proactive escalation.