Automatic rules (if-then)

Let Chorilo take care of steps on its own: when something happens in the choir, a rule sends an email, copies an attendance response or shares the minutes.

Web
Chöre›Chor›Chor-Einstellungen›Automatische Regeln

This feature is only available on the web.

Permission required: Automatic rules – Create, change and delete automatic rules
✉ Sends email

What is this?

With automatic rules you decide what should happen on its own when something happens in the choir. Each rule reads like a sentence:

  • When something happens, for example: someone has been to rehearsal for the third time.
  • And conditions apply, for example: the person sings soprano.
  • Then Chorilo does something, for example: sends the person an email with the music pack.

Rules run in the background. It can take a few minutes, sometimes a few hours, before something happens.

How to create a rule

  1. Click Ensembles in the sidebar, pick your choir and then Choir settings.
  2. Select Automatic rules and click New rule.
  3. Choose a template or Empty rule.
  4. Give the rule a name and choose the trigger under When.
  5. Add conditions under And if you need them.
  6. Under Then, set what should happen. For emails you write the subject and text and insert placeholders such as the first name with one click.
  7. Under How often, choose whether the rule applies only once per person, every time or with a pause.
  8. Click Start test run to see who the rule would have affected in the last 30 days. Nothing is sent.
  9. Click Save.

What can trigger a rule

Around events

  • An event is over: for everyone who was listed for the event, so once per person. The rule waits after the event ends, 24 hours by default, so the leaders can record attendance. Once it's recorded after the event, the rule starts earlier.
  • An event is over (once per event): runs only once per event. Good for a summary email, for example with the list of everyone who was missing.
  • Someone attended for the Xth time: counts past events the person accepted and fires exactly when the number is reached.
  • Someone missed several events in a row: declined, maybe or no response. Excused absences and planned time away don't count by default.
  • Someone's attendance drops below a rate: for example fewer than half of the last six rehearsals. Fires when the rate drops below the value, not at every further rehearsal.
  • An event is coming up (once per event): a few days before the event, for example for an overview of who hasn't responded yet.
  • Someone hasn't responded before an event: for everyone whose response is still open a few days before.
  • Someone responds to an event: accept, decline or maybe for an upcoming event. By default only the person's own responses count, that is what the person, their parents or the link in the email enter.
  • An event is cancelled or tentative: also when it is back on. Handy for an email to the landlord of the rehearsal room.

Around members

  • A new member joins: right away or after a waiting time, for example 28 days for the end of a trial period.
  • Someone is waiting to be approved: when someone signed up through an invitation and still hasn't been approved after the set time.
  • A member is no longer active: someone leaves, is set to passive or is removed by the leaders.

Board

  • Board minutes are completed: the finished minutes can be sent as a PDF. You only see this trigger if you have access to the board area.

Birthdays

  • Someone has a birthday: on the birthday or a few days before, from 8 a.m. Optionally only for milestone birthdays. The rule runs again every year. You only see this trigger if you are allowed to see birthdays.

Conditions

Conditions narrow down who the rule applies to: by voice part, group, role, length of membership, project, under 18 or never signed in. Tick Does not apply to reverse a condition, for example “person is not in the group”.

What a rule can do

  • Send email to the person, with up to five files from the choir's file storage if you like.
  • Send email to the parents: goes to the person's linked parents. Meant for children's and youth choirs.
  • Send email to fixed recipients: selected members, everyone with a role such as section leader and up to 20 more addresses. More addresses are only available after the trial.
  • Copy response to linked rehearsals: anyone who accepts a concert is accepted for the upcoming linked rehearsals, including rehearsals you add later. Rehearsals the person has already responded to themselves stay as they are.
  • Send push notification to the person: shows up on the person's phone and in their bell, for example a birthday greeting from the choir.
  • Send push notification to members: to selected members, groups, roles or all active members. The person it is about gets no notice about themselves.

You can only attach files that you are allowed to open yourself.

History and switch

Every rule has a switch to turn it on and off. Under History you see who the rule applied to, what happened and what is still waiting. If a rule fires unusually often, Chorilo pauses it to be safe and sends the administrators an email. Check the rule and then switch it back on.

Permission

You need the permission Create, change and delete automatic rules. By default only administrators have it.

Tips

  • Start with a template. The texts are already written, you just adjust them.
  • Always do a test run before you switch a rule on.
  • Narrow down the event types. A welcome after the third rehearsal should only count rehearsals, not concerts.
  • One email per event instead of per person. If the section leaders should get just one email after the rehearsal, use the trigger with the addition “once per event”.
  • Switching a rule off for a while is harmless. Whatever would have been due during the break is skipped and doesn't count as “already done” later.

Frequently asked questions

Why wasn't the email sent right away?▾
Rules run in the background. Usually something happens within a few minutes, sometimes it takes a few hours. With “An event is over”, the rule also waits the set time after the event ends, 24 hours by default.
Will members who have already been to ten rehearsals all get the email for the third rehearsal now?▾
No. A rule only counts what happens from the moment you create it or switch it back on. Anyone who reached their third rehearsal before that gets nothing.
Can two rules keep triggering each other forever?▾
No. Chorilo checks this when you save and refuses rules that would trigger each other in a loop. On top of that, a rule pauses itself if it fires unusually often, and the administrators get an email.
Which address do the emails come from?▾
Like all emails from your choir, they come from Chorilo on behalf of the choir. If you enter an address under “Replies go to”, replies end up there.
What happens to members without an email address?▾
They are skipped. The rule's history then shows “No email address on file”.
I want a single email after each rehearsal with everyone who was missing. How do I do that?▾
Use the trigger “An event is over (once per event)” and insert the list “not accepted” in the text. With the trigger “An event is over” without that addition, a separate email goes out for every person listed for the event.
Does someone on holiday get the check-in about missed rehearsals?▾
No. Anyone who has entered planned time away in their profile or has been marked as excused by the leaders doesn't count as missed by default.
Someone declines the concert later after all. What happens to the acceptances copied to the rehearsals?▾
If the rule also listens for declines, it takes back its own acceptances: the rehearsals are open again. What the person entered for a rehearsal themselves stays as it is. The template “Concert acceptance counts for rehearsals” is set up this way.
Why can't I enter more email addresses?▾
During the trial, emails from rules only go to members of your choir. More addresses are available to you afterwards.
Who gets the birthday reminder?▾
Everyone you choose in the rule, but only if they are allowed to see birthdays. This also applies to "All active members". You set who may see birthdays in the permission groups. The birthday person does not get a reminder about their own birthday.
Can I be reminded a few days in advance?▾
Yes. Set how many days before the notification should arrive in the trigger. For one reminder in advance and one on the day itself, create two rules. The placeholder "Date of the birthday" puts the day in the text.

Related features

Still have a question? Ask the AI help bot.

Click the help button in the bottom right and ask your question.