Tests from your own team stay quiet
Messages that give an email address at your own domain are kept without an alert.
For a team that tries its own form now and then, so your own tests do not wake the person on call. Matching messages are still kept in the console, so you can read them at any time.
Rules come with a team plan. A rule can alert a channel (a group of people, listed under Channels in the console's sidebar) or one person.
Make it in the console#
- Sign in to the console at nowlark.com/org, the website where your team is run, and choose Rules in the sidebar.
- Choose New rule and give it a Name, such as “Tests stay quiet”.
- Under Only if, choose Add a condition, pick the email question, then “ends with”, and type your own email domain, such as “@yourcompany.com”. Capital letters do not matter.
- Under Do, in Tell, choose Nobody: keep it in the form.
- Look at Try it beside the rule: a dry run on your latest messages, each with what this rule would do to it. Nothing is sent.
- Choose Create rule, then drag it to the top of the list, so a test never matches another rule first.
What happens#
A message from an address at your domain is kept with the form's messages in the console and alerts nobody.
Rules are checked from the top, and only the first that fits is used. A message no rule matches alerts its form's usual channel, the one chosen under Send alerts to when the form was made.
No team yet? See what a team gets.
Or with the API#
For developers: the same rule, saved in one call to the team API by a team admin (Authentication names the key it needs). Put in your team's id from the console. A rule with no form reads every form. Every field is in Routing rules.
curl -X POST \
https://nowlark.com/v1/teams/team_…/rules \
-H "Authorization: Bearer nla_…" \
-H 'Content-Type: application/json' \
-d '{
"name": "Tests from your own team stay quiet",
"conditions": [
[
{
"field": "email",
"op": "ends",
"value": "@yourcompany.com"
}
]
],
"actions": [{"do": "file"}]
}'