What can trigger a rule

A trigger is a record type plus an event on it. Events are not shared between record types: each type supports its own list, and picking an event that does not exist for that type is the most common reason a rule never fires.

What each type supports:

• Opportunity: created, stage changed, a custom field changed, a date reached
• Customer: created, updated, a custom field changed, went quiet
• Lead and contact: created, updated, a custom field changed
• Activity and task: created, completed, a date reached; tasks also on status changed
• Invoice: created, overdue, a date reached
• Subscription: a date reached
• Ticket: created
• Project: created, completed, stage changed
• Document: signed, declined
• Form: submitted
• Sales sequence: enrolment created, completed, or replied to
• Checklist: an item completed, or the whole checklist completed
• Resource: over-allocated

Two worth knowing about specifically:

Document signed also starts when a customer accepts a contract shared from an opportunity. It does not require a move to another sales stage. The rule can create an activity on that opportunity and email its contact. For documents with several signers, the rule starts once everyone has signed. Existing signatures are not replayed when the rule is enabled or updated.

Custom field changed is how you automate on your own fields: a KYC status reaching compliant, a contract status changing. You name the field, and you can narrow it to one specific transition rather than any change, which is usually what you want.

Form submitted covers landing pages as well as forms. Under Lytt på pick one page or form, or Alle skjemaer og landingssider. Every answer is available to later steps, so "email Anna whenever someone registers interest on the course page" is one rule. A lead, contact or company the page creates also starts its own created rules, exactly as one typed in by hand does, so pick the form trigger when the rule is about the signup and the lead trigger when it is about the lead wherever it came from.

Went quiet fires when a customer has had no contact for a while, which is the one trigger that fires because something did *not* happen.

Invoice created now covers invoices that arrive from your accounting system as well as ones DealJourney raises itself. That is what makes "a customer buys something in the webshop, it reaches the accounting system, we react" possible. Two things about it are worth knowing. An invoice is only ever treated as new once, so the sync re-reading it every hour does not re-run your rule. And when you first connect an accounting system, the years of invoices it imports do not fire anything, because an invoice dated more than a fortnight ago is history rather than news.

A rule on an invoice can also ask which products are on it. Matching on the product name is a contains test, so a name that is contained in another product's name will match both; where that matters, match on the product number instead. The buyer's contact is available too, but only when the company has exactly one contact person, because with several there is no honest way to tell which of them bought.

If the event you want is not on this list for the type you want it on, the rule cannot be built that way. Borrowing an event from a different record type looks plausible in the builder and produces a rule that silently never runs.

Watch an ordinary field change. Leads, customers, contacts, opportunities, subscriptions, activities, tasks and tickets also offer a field-change event. Choose Følg endringer i dette feltet and optionally narrow Fra (valgfritt) and Til (valgfritt). The available fields include ownership, status and other fields relevant to that record type. Changing an opportunity owner, a ticket's priority, or a subscription's status can therefore start a rule. Saving the same value again does not count as a change. These transitions are captured when records are written and processed by the scheduled workflow check, normally every five minutes. Changes made before the rule was created are not replayed.

Use the customer's related records in conditions. The condition picker also offers days since incoming and outgoing contact, whether an open follow-up task exists, whether a subscription is active, whether an opportunity contract is unsigned, the overdue invoice balance and its currency, and the age of the oldest overdue unpaid invoice. Incoming contact includes matching received email and logged incoming interactions. Outgoing contact uses logged outgoing interactions. A missing contact date is unknown, not zero days ago.

Forfalt saldo (én valuta) is only a number when overdue invoices have one known currency; mixed currencies are not added together. Access to invoice amounts is required to configure or preview that condition. Dager i nåværende salgsfase is measured from captured stage changes. If no stage change has been captured yet, the value is unknown. Use an empty-value condition when you want an explicit path for unknown values.