Skip to content

Rules for changes ​

Rules that run when someone creates or changes a record: the most common kind. If you have not built a rule yet, start with your first rule.

When a field changes to a value ​

"When the stage changes to Won" takes two settings together:

  • In When: A record is changed, and in Only when one of these fields changes (optional), the field Stage. The box then reads "Stage changes".
  • In Only if: Stage is any of Won.

The condition alone says "the stage is Won", not "the stage became Won". Without the first setting, the rule would run again each time someone changes anything on a won deal, such as its amount. With both, it runs once: when the stage changes and the new stage is Won.

The examples below use this pair.

Won deals get a kick-off call ​

Step: Create a record. When a deal is won, a call is put in its Activities, three days later.

  1. Administration › Automation, Entity: Deals, then Add a rule.

  2. Name: Won deals get a kick-off call.

  3. When: A record is changed. Only when one of these fields changes: Stage.

  4. Only if: Stage is any of Won.

  5. Add a step: Create a record:

    • A record of: Activities.

    • Linked to this record: As a sub-record of this Deal.

    • Under Its fields, click Add a field for each of these:

      FieldHowValue
      SubjectTo a valueKick-off call
      TypeTo a valueCall
      DayTo a formulaTODAY() + 3
  6. Save the rule.

Try it. Open a deal, set its Stage to Won and save. Its Activities now hold "Kick-off call", three days from today.

A record of another entity, not a sub-entity, can be linked Through its field …: a relation field of the new record that points at this entity. It can also be Not linked.

Lost deals close their activities ​

Step: Update related records. When a deal is lost, each of its activities is marked done, so that nobody calls about it.

  1. Entity: Deals, Add a rule, Name: Lost deals close their activities.
  2. When: A record is changed, only when Stage changes.
  3. Only if: Stage is any of Lost.
  4. Add a step: Update related records:
    • Which records: Its Activities.
    • Only those that match (optional): leave it empty, for all of them.
    • Set: Add a field, Done, To a value, ticked (Yes).
  5. Save the rule.

Which records offers what this record is tied to: its parent record (for a sub-entity), its sub-records, the record a relation field points at ("The Companies of Company"), and records that point at it. A step changes up to 500 records.

Before saving: the probability follows the stage ​

Step: Set fields, before saving. When a deal is won, its probability becomes 100 in the same save. The person who saved sees 100 at once.

  1. Entity: Deals, Add a rule, Name: Won deals are certain.
  2. When: A record is changed, only when Stage changes. In the same settings, tick Before saving: set fields of the record in the save itself. The When box now ends with "before saving".
  3. Only if: Stage is any of Won.
  4. Add a step. The menu now offers only Set fields: choose it. Add a field, Probability, To a value, 100.
  5. Save the rule.

Make a second rule the same way for Lost, with 0.

Before saving or after?

  • After saving (the box unticked, the usual way): the change is saved first, then the rule runs, at once after the page answers. The record's history has two entries: the person's change, then the rule's.
  • Before saving: the values are part of the save itself, whatever the door (the form, the API, an import). Only Set fields steps can run this way, and only for A record is created or A record is changed. If a value is refused (a required field emptied, say), the save stops, and the message names the rule.

Ways to set a field. In each row of Set fields, after the field, choose how:

  • To a value: what you type or pick.
  • Copied from a field: the value of another field of the record.
  • To a formula: TODAY() + 3, amount * 1.2, DATEADD(close_date, 1, "month"); see Formulas.
  • Emptied.
  • For a field that holds several people or records: Add people or records or Take away people or records, with And whoever set the rule off for people.

A comment reopens a waiting ticket ​

Trigger: Someone comments on a record. When the customer's contact writes on a ticket that waits for them, the ticket goes back to Open.

  1. Entity: Tickets, Add a rule, Name: A comment reopens a waiting ticket.
  2. When: Someone comments on a record.
  3. Only if: Status is any of Waiting.
  4. Add a step: Set fields, Status, To a value, Open.
  5. Save the rule.

A comment by anyone sets it off, your own team included. To have only some people's comments count, choose them, or their role or team, in Done by.

Other changes: trash and restore ​

A record is moved to the trash and A record is restored work like the others. For example, a rule of Tickets on A record is restored, with the step Set fields, Status, To a value, Open: a ticket brought back from the trash is open again.

A record moved to the trash before its rule ran is left out by the other rules: only rules for A record is moved to the trash still run for it.

Who did it, and through which door ​

Done by and Through, in Only if, narrow rules that changes set off:

  • Done by: people, roles or teams. "When someone of the Sales role changes a ticket": choose Sales.
  • Through: The interface, The API, An import, Automation. Untick An import for a rule that sends messages, so that importing many records does not send a message for each.

Rules that hear other rules ​

A rule hears the changes people make. Records that other rules create or change do not set it off, unless you tick Also when other rules change records in the settings of When. For example: tickets created by the contact form set off your first rule only if that rule has this box ticked.

So that rules cannot set each other off without end, a chain stops after five rules, and a rule does not run twice on the same record in one chain. Such a run shows as Skipped.