Flow: notifications and reminders

SENSEVER

The official Sensever channel: guides and API documentation for Chat, Requests, Flow, Studio, bots and messaging channels.

อ่าน 10 นาที

Flow: notifications and reminders

Flow tells you about important things in Sensever chat and, if you want, by email: you were assigned, a task is done, a deadline is approaching, a process is waiting for your decision, you were mentioned in a task description. This article explains where notifications come from, who gets them, how to tailor them to yourself and how deadline reminders work.

Where notifications arrive

All Flow notifications arrive in a single direct chat in Sensever chat — with the "Sensever Flow" bot. It appears in your chat list with the first notification. It is a regular conversation: the unread counter, push to your phone and browser, muting and blocking work as in any chat. You can't write in this conversation — there's no one to read replies.

The message is short:

  • the workspace — "Flow · workspace name";

  • the title and text written by the rule's author;

  • the object's name as a link to its card.

Flow's system notifications — "You were mentioned", "Your approval is needed", deadline reminders — reach everyone in the language of their Flow interface (in chat and in emails). The text of automation and process rules arrives as the author wrote it: Flow doesn't translate it.

Notifications contain no field values: you see the object's contents only by opening it, and only if you have access. The notification stays in chat even after you lose access to the object, but its link no longer opens the object.

Redelivery after a failure doesn't create a second message.

Emails

You can also get notifications by email — at your Sensever account address. This is a separate "Email" channel in your personal workspace settings (see below), off by default. Emails don't arrive one by one: everything accumulated is combined into one email no more than once every 15 minutes, and during your quiet hours the email waits until they end. Every email has an "Unsubscribe" link.

Besides copies of notifications, there is a daily digest and a calendar subscription — they are set up once for all workspaces. Learn more in Flow: emails and calendar subscription.

Where notifications come from

Notifications are sent by the workspace's rules, not by Flow itself:

Source

Example

Category in settings

Automations with the "Send notification" action

"You were assigned", "Task completed"

"Automations"

The type's reminder rules

"Due tomorrow", "Overdue"

"Due date reminders"

Processes

"Your approval is needed", an escalation, a notification in a process step

"Approvals and processes"

@ mentions in an object's description

"You were mentioned"

"Mentions"

In workspaces created from templates, the necessary rules are already turned on:

Template

Rule

Who receives it

"Tasks", Main

"Notify the assignee about a new task", "Notify the new assignee"

Assignee

"Tasks", Main

"Notify the author and watchers that the task is done"

The task's author and watchers

"Tasks"

"Notify the assignee and watchers that the task is unblocked"

Assignee and watchers

"CRM"

"Notify the assignee about a new deal", "Notify the deal's new assignee"

Assignee

"CRM"

"Won deal: onboarding project and notification"

Workspace owners and administrators, watchers

You can see and turn off these rules in the type settings → the "Automations" tab.

In addition, workspaces created from templates have deadline reminders turned on (the type's "Reminders" tab):

Template

Reminder rule

When

Who receives it

"Tasks", "Simple tasks" (Main)

"Task deadline"

a day before the deadline and on the day, at 09:00

Assignee and watchers

"CRM"

"Deal close date"

a day before the date and on the day, at 09:00

Assignee and watchers

"Product development"

"Planned release date"

7 days before the date and on the day, at 09:00

Assignee

Workspaces created before these rules appeared don't change — you can add the rule yourself (see "Deadline reminders" below).

You set up your own notifications with automations — see Flow: automations.

Who receives a notification

The rule defines the recipients: the assignee, the object's author, people from a field (for example, "Watchers"), workspace roles. Before sending, Flow checks each recipient:

  1. We don't notify the author of the action. Someone who moved a task to "Done" or assigned themselves won't get a notification about it. A rule can add the author back to the recipients with the "Also notify the author of the change" checkbox in the notification action. If the change was made by an automation or a process, there is no human author and no one to exclude.

  2. The workspace member is active. Deactivated members don't get notifications.

  3. The recipient can see the object. The notification arrives only if the recipient can open the object at the moment of sending.

  4. The recipient's personal settings allow this notification (see below).

Process notifications (for example, a request to decide on an approval) don't exclude the author: the process acts, not a person.

Personal settings

Settings → the "Notifications" tab. The settings are personal and apply only to the current workspace; another workspace has its own. Every change is saved immediately.

Setting

What it does

"Don't send me notifications from this workspace"

Turns off all notifications from the workspace

"What to send" → "Automations"

Notifications from the workspace's rules. Under the switch is a list of rules by object type: each can be turned off separately

"What to send" → "Due date reminders"

Reminders from the types' rules; each rule can also be turned off separately

"What to send" → "Approvals and processes"

Requests to decide on approvals, escalations and process messages

"What to send" → "Mentions"

You were named with @ in a task description (learn more in Flow: mentions)

"How to send" → "Chat messages"

Notifications in the "Sensever Flow" conversation. If you turn off both chat and email, notifications don't arrive at all

"How to send" → "Push"

Without push, the message arrives in chat silently. Available only when chat messages are on

"How to send" → "Email"

A copy of notifications by email. Under the switch you choose which categories to send by email; by default "Due date reminders" and "Approvals and processes"

"Quiet hours"

"No push during this time": from, to and the time zone

A category that is turned off is off for all channels at once: you can't get it by email only. But if chat is off and email is on for a category, notifications of that category arrive by email only.

Under the channels is the "Email and calendar" link: there you turn on the daily email digest and emails in general (one setting for all workspaces); see Flow: emails and calendar subscription.

The rule list shows only rules of types whose objects you can read. This way you can see exactly what is messaging you, even without access to the automation settings.

Quiet hours

During quiet hours, notifications are not postponed: the message arrives right away, but without push — your phone stays silent and the unread counter grows. In the morning, everything you missed is waiting in the "Sensever Flow" conversation.

  • Emails, on the other hand, are postponed: an email with notifications from quiet hours arrives after they end.

  • The setting is available only when chat messages are on.

  • By default, quiet hours are from 22:00 to 08:00 in your browser's time zone; you can choose the time zone.

  • The interval can cross midnight. The start and end can't be the same.

  • Time is compared using the clock of the chosen time zone, accounting for daylight saving time.

To turn off all Flow notifications in chat across all workspaces at once, do it in chat itself: mute or block the "Sensever Flow" conversation. Emails are turned off in "Email and calendar" or with the "Unsubscribe" link in an email.

Daily digest

The digest is one email a day covering all your workspaces: overdue tasks, tasks due today and tasks assigned to you in the past 24 hours. Only open objects where you are the assignee are included. An empty digest isn't sent.

The digest is off by default. You turn it on in "All workspaces" → "Email and calendar": the "Daily digest" checkbox and the sending time (08:00 by default, in your time zone). Learn more in Flow: emails and calendar subscription.

Deadline reminders

A reminder is a message that an object's deadline is approaching, has arrived or has been missed. Reminder rules are set by the type's administrator: type settings → the "Reminders" tab → "New rule". You need permission to manage this type's automations.

Form field

What to enter

"Name"

What the rule is called in lists and in personal settings

"Key"

Latin letters, digits and _, starting with a letter; set on creation and can't be changed

"Due date field"

A "Date" or "Date and time" field. If the type has none, first add such a field to the schema

"Time zone"

An IANA time zone, for example Europe/Moscow: reminder times are calculated in it

"When to remind"

From 1 to 10 moments: "+ before the deadline", "+ on the deadline day", "+ overdue"

"To"

This type's fields with people, "Owner" (the assignee) and "Author"

"On"

A rule that is turned off doesn't schedule reminders

Only those who can see the object at the moment of the reminder receive it. There may be no recipients: then the reminder only triggers automations with the "deadline reminder" trigger (for example, "move to status" or "create an escalation task").

When a reminder arrives

Moment

"Date" field

"Date and time" field

Before the deadline

N days or weeks before, at the specified time

N minutes, hours, days or weeks before the deadline

On the deadline day

At the specified time on the deadline day

At the specified time on the deadline day

Overdue

N days after the deadline day, at the specified time; "0 days" means the day after the deadline

N after the deadline; 0 means at the moment of the deadline

  • Days and weeks are calendar days and weeks; hours and minutes are exact. Business hours and the business calendar's days off don't affect reminders.

  • A deadline in a "Date" field counts as reached once its day is over: a task due January 15 is overdue from the 16th.

  • The default time is 09:00.

What cancels a reminder

  • Moving the deadline cancels scheduled reminders and sets new ones for the new date. Clearing the deadline field cancels them.

  • Closing the object (a transition to a status in the "Completed" or "Cancelled" category) cancels reminders, and reopening sets them again.

  • Archiving cancels reminders, and restoring sets them again.

  • Changing, turning off or deleting a rule recalculates reminders for all objects of the type in the background.

Past moments aren't caught up on: if the deadline was moved into the past or a rule was created over old tasks, a "due tomorrow" reminder won't arrive retroactively. The same reminder for the same deadline never arrives twice.

Only those allowed to read the deadline field see the deadline date in the reminder text. Everyone else gets "Deadline approaching" without the date.

What's next

ความคิดเห็น

ผู้เขียน