Let an assistant run on its own: schedules, changes and webhooks

On a schedule

Under Runs on its own, choose Every day, Weekdays or Every week, then a time on the hour; for weekly, also a day. The time is in your time zone when you save. At that time it runs once.

When something changes

• There is new knowledge-base content: content was added or changed in the sources it reads. Duaer’s own cases and cards do not count here.
• A process case changes: a process case changed. Cases reach the knowledge base as soon as they change.
• It checks at most once an hour. Changes within the hour are taken together, in one run.
• Each person gets a run only for changes they may see, and the result names only those items, up to 20. With no change they may see, there is no run for them.
• It counts from the moment you tick the box; earlier changes do not start it.

When an outside system calls it

Once an owner or admin creates a webhook for the assistant, each call runs it once. See the assistant webhook.

Where results go

• Each run answers once for the person who built it and once for each colleague it is shared with, each with their own access. The result is a note on each person’s home page, kept for 30 days.
• With Also send results to my chat tool ticked, each person also gets the result in the first of Feishu, WeCom, DingTalk, Slack and Microsoft Teams that the organization connected and that finds them, or by email when none does. If sending fails, the home page note is still there.
• Scheduled and triggered runs only read; they never run actions.

Also post to a group

Under Also post results to a group, choose a Feishu group or Slack channel, and scheduled and triggered results also go there. You can choose only groups that you and the Duaer bot are both in.

• The group’s answer uses only what everyone in the group may read: on every run Duaer reads the members again and keeps only content all of them may open, so nothing only some may read reaches the group.
• With anyone in the group who is not in your organization (outside contacts, guests), or more than 200 people, it does not post, and the form says why; it also stops once you leave the group.
• The form shows whether and when the last post went out, or why it did not.
• Personal home page notes and chat tool results go on as before. Microsoft Teams, WeCom and DingTalk groups are not supported yet.

Daily limit

• Runs started by changes and by the webhook: up to 24 per assistant per UTC day, all three triggers together.
• A check that runs for several people counts once.
• Scheduled runs do not count toward it.