How automations work in Teamopipe

Automations let you build rules that keep deals, contacts, organizations, and tasks moving automatically. Instead of doing routine updates by hand, you define a rule once — when something happens, react to it — and Teamopipe runs it for you across your workspace.

Where to find automations

Open the Automations section in Teamopipe. The page shows three counters — Total automations, Active, and Inactive — followed by the list of your automations. Click + Create automation in the top-right corner to build a new rule.

The anatomy of an automation

Every automation is built from three parts, and the builder walks you through them top to bottom:

• Trigger — the event that starts the automation. You pick an entity (a deal, contact, organization, or task) and the event to react to.
• Conditions — optional filters. The automation only continues if these match, so you can narrow a rule down to exactly the situations you care about.
• Actions — what Teamopipe does when the rule fires. An automation can run one action or several in sequence.

Tip: The bar at the top of the builder always shows your rule in plain English — "When a deal is [event] — conditions — run actions" — so you can sanity-check the logic before saving.

Triggers

The trigger has two dropdowns: Entity and Event. For deals, you can react to these events:

• Added — a new deal is created
• Stage changed — a deal moves to a different stage
• Field changed — a deal field gets a new value
• Won or Lost — a deal is closed either way
• Deleted — a deal is removed

Contacts, organizations, and tasks have their own event lists, so a rule can react to changes anywhere in your workspace — not just in the pipeline.

Conditions

Conditions are optional — without them, the automation runs every time the trigger event happens. Each condition is a field, an operator, and a value. Conditions in the main group must all match ("all of these must match"). If you need alternative paths, click + Add OR block — conditions there work as "any one of these can match".

For example, a rule triggered by "Stage changed" can be narrowed with a condition so it only fires for deals in one specific pipeline, or above a certain deal value.

Actions

Actions are what actually happens when the rule fires. The list of available actions adapts to the trigger you picked — different entities and events offer different actions, so check the Action dropdown after setting your trigger. Click + Add action to chain several actions in one automation; they run in order.

How to create your first automation

1. Open Automations and click + Create automation.
2. Replace "Untitled automation" with a name that describes the rule — you'll thank yourself once you have ten of them.
3. In the Trigger block, choose the Entity and the Event to react to.
4. Optionally add conditions with + Add condition, or an alternative group with + Add OR block.
5. Pick what happens in the Action dropdown. Add more steps with + Add action if needed.
6. Leave the Active toggle on and click Create automation. The rule starts running immediately.

Pausing and managing automations

Use the Active toggle to pause a rule without deleting it — inactive automations stay saved and show in the Inactive counter, but never run. Start with one simple rule for your most repetitive chore, watch it work for a few days, then add more. A few well-named rules beat a dozen you can't remember the purpose of.

If you run into issues, use the chat in the bottom-right corner or the contact form at teamopipe.com/en/contact — we typically respond within 4 hours on business days.