Wiki

Assignments

Assignments are "do this later" instructions for your assistant. Instead of doing something now, DMJBot runs it automatically later — either on a schedule (a timer assignment) or when something happens (an event assignment, for example a new file in a monitored folder or a new email).

Create one from chat — the easy way

The simplest way to create an assignment is to just ask in normal chat. Describe what you want and when, and DMJBot turns it into a timer or event assignment for you. A few examples:

"Every weekday at 9:00, summarize my pending Jira issues and send me a short plan."

"In 30 minutes, remind me to review the deployment logs."

"When a new email arrives about a job that asks for a CV, get my CV from the CV folder on my storage and reply with it attached plus a short relevant message."

"Whenever a new file lands in my monitored Invoices folder, summarize it and post the key points to the Slack #finance channel."

After the bot creates one, ask it to show the assignment details (trigger, one-time vs repeated, and the task text) so you can confirm it's exactly what you meant.

You can also create assignments formally with the Assignments form if you prefer a guided UI — see Creating with the form below.

Triggers: timers and events

Timer assignments run at a time or on a schedule you describe — in 20 minutes, every day at 09:00, every Monday.

Event assignments run when an event is reported by a connected tool. Events are available only after the relevant MCP server is connected and its monitoring / notification settings are turned on. Common events and the servers that emit them:

• New file — File Storage, Dropbox, rclone remote.
• New email — Gmail, Any Email.
• New Slack message / thread reply / DM — Slack.
• Jira issue assigned / mention in a comment — Jira & Confluence.
• Task finished / failed — long-running tools such as Command, Agent and Git.

See Tools and MCP for the full catalog and each server's events.

Example: a small automation you can build

Here is a complete flow that takes only a few minutes to set up:

1. Connect a device (your laptop) with the DMJBot Bridge and install the File Storage MCP server, pointed at a folder with folder monitoring enabled.

2. Add the Gmail tool so the bot can send email.

3. In chat, say:

   "When a new file arrives in my monitored storage folder, send an email to alex@example.com with the file's name as the subject and a short summary of the file in the body, and attach the file."

From then on, every time a file appears in that folder DMJBot automatically reads it, writes a summary, and emails it — with the file attached — to the address you gave. No further action from you. This combines a file event (File Storage) with an action (Gmail) in one assignment, and the file moves between the two tools without you touching it (see Files and Attachments).

Creating with the form

If you prefer a guided UI instead of chat:

1. Open the Assignments page from the sidebar.
2. Click Add / Create assignment.
3. Choose the type — Timer or Event.
4. Enter the task instruction (what the assistant should do).
5. For a timer, set the schedule text; for an event, choose an available event key.
6. Choose one-time or repeated.
7. Save.

Where to see your assignments

In the web interface there are two places to find them:

• The right panel during a chat. While you have a chat open, assignments are shown in the right-hand panel, so you can see what is scheduled or watching for events right next to the conversation.
• The Assignments page (left menu). A dedicated page lists everything in one place: active assignments, their execution results / history, and archived assignments. Open any assignment to see its trigger, task text, and the record of past runs.

One-time vs repeated

• Repeated — runs again every time the schedule fires or the event happens.
• One-time — runs once, then is archived and becomes inactive.

What happens when an assignment runs

• DMJBot creates a background task for the work.
• You can watch status and progress in the Tasks page and in the assignment's history.
• Results appear in the related chat session.

You can view active and archived assignments, open an assignment's details and execution history, and archive or delete assignments at any time.

Tips

• Keep the task text specific: what to check, the output you want, and where to put the result.
• Use one-time assignments for ad-hoc actions, repeated ones for ongoing routines.
• If an event assignment never triggers, check that the related MCP server is connected and that its notifications/monitoring are enabled.