Introducing SetGet Automations 2.0
SetGet Team
Product
Every growing team eventually hits the same wall: the work that keeps your projects moving forward starts competing with the repetitive tasks that keep them organized. Triage incoming issues, notify the right people, move cards between states, update labels — these are the invisible gears that keep a product team running, but they consume hours that could be spent building.
When we shipped Automations 1.0 two years ago, we gave teams a simple way to define trigger-action rules. It was useful, but limited. Rules were flat, triggers were slow, and there was no way to express conditional logic. Teams with complex workflows had to create dozens of overlapping rules just to approximate the behavior they needed.
Automations 2.0 is a ground-up rebuild. We replaced the old rule engine with a DAG-based workflow system that supports branching, parallel execution, and sub-second trigger latency. Whether you are a two-person startup or a 500-seat enterprise, you can now automate any repeatable process in SetGet without writing a single line of code.
What Changed in 2.0
Four major upgrades that transform how your team handles repetitive work.
Visual Workflow Builder
Design automation rules with a drag-and-drop canvas. See the entire flow at a glance — triggers, conditions, and actions — laid out as a visual graph. No code, no guesswork, and every team member can understand what an automation does just by looking at it.
Conditional Logic
Add if/then/else branches to any automation. Route issues differently based on priority, label, assignee, project, or any custom property. Build decision trees that mirror your real process instead of flattening complexity into dozens of separate rules.
10x Faster Triggers
The new event bus processes triggers in under 100 milliseconds. Issue created? State changed? Comment added? Your automation fires before you finish switching tabs. Real-time responsiveness means your workflows feel instant, not eventually consistent.
Webhook Actions
Send data to any external API when an automation fires. Push notifications to Slack, create tickets in external systems, update your CRM, or hit a custom endpoint. SetGet becomes the orchestration layer that connects your entire tool stack.
How It Works
Building an automation takes three steps. The visual builder guides you through each one.
Choose a Trigger
Select the event that starts your automation: issue created, state changed, priority updated, label added, comment posted, or cycle started. Each trigger can be scoped to a specific project, label, or member to keep automations targeted and efficient.
Add Conditions
Define the criteria that must be true for the automation to proceed. Combine multiple conditions with AND/OR logic — for example, priority is urgent AND label is bug AND assignee is empty. Conditions can inspect any property on the issue, including custom fields.
Define Actions
Specify what happens when conditions are met: assign to a team member, change state, add a label, move to the current cycle, send a notification, or fire a webhook. Chain multiple actions together — they execute in order, and each action can reference the output of the previous one.
Before & After
Before Automations 2.0
- ✗Manual triage: every new issue waited in the backlog until someone noticed it, sometimes for hours or even days during busy sprints.
- ✗Forgotten follow-ups: high-priority bugs slipped through because the right person was not notified in time, leading to missed SLAs.
- ✗Inconsistent processes: different team members applied different labels, assigned to different people, and moved issues through different state sequences.
After Automations 2.0
- ✓Auto-triage in seconds: new issues are classified, labeled, and assigned within milliseconds of creation based on properties and context.
- ✓Zero missed deadlines: urgent items automatically notify the on-call lead and get added to the current sprint, with escalation rules if unresolved.
- ✓Consistent workflows: every issue follows the same path through your process, regardless of who created it or when it was filed.
Built for Every Workflow
From bug triage to release management, automations adapt to how your team works.
Bug Triage Automation
Automatically classify incoming bugs by severity, assign to the right team, and add to the current sprint — all within seconds of creation.
Release Pipeline
When all issues in a cycle move to Done, automatically notify stakeholders, update the changelog, and trigger the deployment webhook.
Onboarding Workflows
When a new member joins a project, auto-create a set of onboarding tasks, assign a buddy, and send a welcome notification with getting-started links.
Example: Webhook Automation Config
{
"name": "Auto-triage high priority bugs",
"trigger": {
"event": "issue.created",
"filter": {
"priority": "urgent",
"label": "bug"
}
},
"conditions": [
{ "field": "assignee", "is": null }
],
"actions": [
{ "type": "assign", "to": "@on-call-lead" },
{ "type": "move_to_cycle", "cycle": "current" },
{ "type": "webhook", "url": "https://hooks.slack.com/..." }
]
}Try Automations 2.0 Today
Start automating your workflows and reclaim hours every week.