How to Set Up CRM Automation Rules in UniLink (Auto-Tag, Notify, and Move Contacts)

Save hours of manual contact management by building trigger-based rules that tag, move, email, and notify automatically — the moment something happens.

TL;DR: UniLink CRM automation rules let you define a trigger (new subscriber, purchase, tag added, form submitted, score threshold) and an action (add tag, move pipeline stage, send email, Telegram notification, assign to team member). Set them once and they run silently in the background for every contact.

Managing a growing contact list by hand is one of the fastest ways to burn out. When someone buys a product, you need to tag them, move them to the right pipeline stage, and send a follow-up — all within minutes. When a lead fills out a form, it has to land on the right team member's plate immediately. UniLink CRM automation rules handle all of this the moment a trigger fires, without you touching a single contact record.

This guide walks through every aspect of CRM automation rules in UniLink: what they do, how to set them up, how to configure advanced options, and how to troubleshoot the most common issues.

What CRM Automation Rules Do

A CRM automation rule is a simple if-this-then-that instruction stored inside your UniLink CRM. When the trigger condition is met for a contact, the rule executes one or more actions on that contact immediately. Rules run in the background continuously, so every new contact or status change is evaluated without any manual input.

Triggers cover the key moments in a contact's lifecycle. A new subscriber joining your list, a completed purchase, a tag being added by another automation or a team member, a form submission on your page, or a contact reaching a lead score threshold — each of these can kick off a rule. Multiple triggers can be stacked, meaning a single contact event can fire several rules in sequence.

Actions are equally flexible. You can add or remove tags, move a contact forward or backward through a pipeline stage, send an email from your UniLink email sender, fire a Telegram notification to your own account or a team channel, or assign the contact to a specific team member for follow-up. Actions can be combined so that a single trigger does several things at once — tag the contact, move the stage, and notify your sales team simultaneously.

How to Get Started With CRM Automation Rules

  1. Open your CRM dashboard — Log in to UniLink, go to the CRM section from the left sidebar, and click the Automation tab at the top of the page.
  2. Click Create Rule — Hit the blue Create Rule button in the upper right. A rule editor panel slides open on the right side of the screen.
  3. Name your rule — Give it a descriptive name you will recognise later, such as "New subscriber → tag Leads" or "Purchase → move to Customers stage".
  4. Select a trigger — Click the Trigger dropdown and choose from: New Subscriber, Purchase Completed, Tag Added, Form Submitted, or Score Threshold Reached. Each trigger may reveal additional fields — for example, Tag Added asks which specific tag, and Score Threshold asks for a numeric value.
  5. Add one or more actions — Click Add Action and choose from Add Tag, Remove Tag, Move Pipeline Stage, Send Email, Telegram Notification, or Assign to Team Member. Fill in the required fields for each action.
  6. Set a run frequency (optional) — By default rules fire every time the trigger occurs. Toggle Once Per Contact if you only want the rule to run the first time a contact meets the condition, preventing duplicate tags or repeated emails.
  7. Save and enable the rule — Click Save. The rule is active immediately and a green Enabled badge appears in your rules list. Test it by manually triggering the condition on a test contact.

How to Use CRM Automation Rules

  1. Build a new subscriber welcome flow — Create a rule with trigger New Subscriber, actions Add Tag "new-lead" and Send Email "Welcome to [Your Brand]". Every new opt-in gets tagged and welcomed without touching your inbox.
  2. Auto-advance pipeline stages on purchase — Set trigger to Purchase Completed, action Move Pipeline Stage to "Customers". Your pipeline reflects real buyer status at all times without manual drag-and-drop.
  3. Notify your team on hot leads — Use trigger Score Threshold Reached (e.g., 80 points) with action Telegram Notification to your sales channel and Assign to Team Member. Your team gets an instant ping with the contact's name.
  4. Segment by form source — Different forms on your page can trigger different tags. Form Submitted on your "Coaching Inquiry" form adds tag "coaching-interest", keeping that segment clean for targeted campaigns.
  5. Chain rules together — When you add tag "VIP" via one rule, another rule with trigger Tag Added ("VIP") can fire and move the contact to your VIP pipeline. Rules that react to tag additions let you build multi-step flows without a single workflow builder.
  6. Run audits with the activity log — Each rule shows a Recent Activity log. Check it weekly to confirm rules are firing and catching the contacts you expect. Look for zero-fire rules — they may have a misconfigured trigger condition.
  7. Pause rules during migrations — Before bulk-importing contacts, toggle rules off temporarily. Bulk imports can fire thousands of New Subscriber triggers at once. Re-enable after the import is settled.

Key Settings Explained

SettingWhat it controlsBest practice
Trigger typeThe event that starts the rule — New Subscriber, Purchase, Tag Added, Form Submitted, Score ThresholdChoose the most specific trigger available to avoid unintended fires on unrelated contacts
Run frequency (Once / Every time)Whether the rule fires once per contact lifetime or every time the trigger condition is met againUse Once Per Contact for welcome emails and onboarding tags; use Every Time for score-based alerts
Action delayOptional minutes/hours to wait before executing the action after the trigger firesAdd a 10-minute delay on welcome emails so the contact receives a natural-feeling message, not an instant bot response
Pipeline stage targetFor Move Pipeline Stage action, which specific stage the contact is moved toMap stages to actual business milestones (Lead → Qualified → Customer → Churned) so the pipeline reflects reality
Assign to team memberWhich team member receives the contact assignment and optional Telegram pingAssign based on contact source or tag to distribute leads fairly; avoid routing all high-score leads to one person
Pro tip: Use the Score Threshold trigger as a quality gate. Set your lead scoring rules to award points for page visits, link clicks, and purchases, then fire an automation at 75 points to notify your sales team. This means your team only sees contacts who have already shown real intent — not everyone who signed up.

How to Get the Most Out of CRM Automation Rules

The biggest unlock from automation rules is not replacing one manual task — it is building a system where contacts move through your funnel without any human intervention until they are ready for a real conversation. Map your entire funnel on paper first: what are the stages, what actions move someone from one stage to the next, and who needs to know when that happens. Then translate each transition into a rule.

Combine rules with UniLink's email and Telegram integrations for a closed loop. A contact who buys gets tagged, moved, emailed a receipt, and their assigned team member gets a Telegram ping — all within seconds. This level of responsiveness is difficult to match manually even with a dedicated team, and it scales to thousands of contacts without extra cost.

Tag hygiene matters as your rule count grows. Establish a tagging taxonomy early: use prefixes like "src-" for source tags (src-instagram, src-form-coaching), "int-" for interest tags, and "st-" for status tags (st-customer, st-churned). Rules that react to Tag Added triggers become far easier to read and maintain when tags follow a consistent pattern.

Review your rules monthly. Disable any rules that are no longer firing (check the activity log) and remove tags they create — stale tags pollute segments and make email targeting less accurate. A rule library with 5 clean, active rules is more valuable than 30 rules that half-work.

Troubleshooting Common Issues

ProblemLikely causeFix
Rule fires but action does not executeThe action target (email template, pipeline stage, team member) was deleted after the rule was createdOpen the rule, re-select the action target from the dropdown, and save again
Rule fires multiple times on the same contactRun frequency is set to Every Time instead of Once Per ContactEdit the rule and toggle Once Per Contact; existing duplicate tags can be removed via bulk tag editor
Score Threshold rule never firesLead scoring is not configured or the scoring conditions award fewer points than the thresholdCheck Lead Scoring settings under CRM → Settings; verify individual contacts are accumulating points in their profiles
Telegram notification is not receivedTelegram integration not connected or the bot was removed from the destination channelGo to Integrations → Telegram, reconnect the bot, and re-send the test notification from the settings panel

Pros

  • Runs silently 24/7 — contacts are tagged and moved even when you are offline
  • Supports chaining through Tag Added triggers, enabling multi-step flows without a visual workflow builder
  • Covers the full communication stack: email, Telegram, and pipeline movement in a single rule
  • Once Per Contact toggle prevents duplicate emails and tag spam on re-triggering contacts

Cons

  • No native branching (if/else logic) within a single rule — complex branching requires multiple separate rules
  • Bulk imports can trigger all New Subscriber rules simultaneously unless rules are paused first
  • Rules do not have a built-in history of which contacts triggered them beyond the recent activity log

Frequently Asked Questions

Can I run multiple actions from a single trigger?

Yes. When building a rule, click Add Action as many times as needed. All actions execute when the trigger fires. You can add a tag, move a pipeline stage, and send an email all from one trigger event.

Will automation rules apply to contacts imported before the rule was created?

No. Rules apply prospectively — they fire for contacts who meet the trigger condition after the rule is saved and enabled. Contacts imported before the rule was created are not retroactively processed.

Can I test a rule without affecting real contacts?

Yes. Create a test contact in your CRM, then manually trigger the condition (add a tag, submit a form with the test email, etc.). The rule will fire on the test contact so you can verify the actions before going live.

How many automation rules can I create?

The number of rules available depends on your UniLink plan. Most paid plans support unlimited rules. Check your plan details under Account → Billing for the exact limit on your tier.

What happens if two rules have the same trigger and conflicting actions?

Both rules execute. If one rule adds a tag and another removes the same tag, the result depends on execution order (rules run in the order they were created). To avoid conflicts, review your rules list for duplicate triggers and consolidate overlapping logic into a single rule.

Key Takeaways

  • Automation rules use a trigger-action structure: pick what event fires the rule and what happens next.
  • Triggers include new subscriber, purchase, tag added, form submitted, and lead score threshold.
  • Actions include tagging, pipeline movement, email, Telegram notification, and team assignment.
  • The Once Per Contact toggle prevents duplicate emails and tags for returning contacts.
  • Chain rules by using Tag Added as a trigger to build multi-step flows without a visual workflow builder.

Ready to automate your CRM?

Set up your first automation rule in minutes and let UniLink handle the contact management while you focus on growing your business.

Get Started Free