Marblism Recurring Tasks: Build One in 15 Minutes

Turn one job an AI employee already handles well into a clear schedule—with enough context to review before it runs.

Recurring work saves time only when the instruction is specific. “Follow up every week” leaves the employee guessing about who, when, what counts as finished and whether anything should be sent. A five-line brief makes the schedule easier to inspect and safer to correct.

This guide focuses on the task itself. Run the separate Marblism timezone check before choosing a live run time, and use the usage audit after the task has produced a real result.

What Marblism officially supports

Marblism's current help guide defines a task as a one-time or recurring action assigned to an AI employee for a specific date and time. You can create one from the Tasks section or ask the employee to create it during a chat.

The official task formula includes the employee, recurrence, time, specific action, supporting details and the goal. Marblism also says tasks are best suited to recurring work; a quick chat is usually better for a one-time job needed today.

Build a Marblism recurring task step by step

1. Choose a proven manual job. Use something the employee has already completed correctly in chat. Do not make the first scheduled run an untested customer-facing action.
2. Name the employee and schedule. Enter a recurrence and exact local time. If the clock matters, complete the 12-minute timezone check first.
3. Define one observable output. Replace “help with follow-ups” with a list, draft, summary or other result you can inspect.
4. Add the details. State the source to use, what each item should contain and what “done” looks like.
5. State the goal. Give the employee the business reason so the output supports a real decision.
6. Keep the first run reviewable. Use a draft-only guardrail whenever the work could otherwise contact a customer, publish content or trigger another external action.
7. Create and read back the task. Paste the prompt into the employee's chat, or enter the same fields through Tasks → Create Task. Then open Tasks and verify the employee, next run, recurrence and full instruction.

Search the Tasks list for another job with the same purpose before saving. Marblism's Eva troubleshooting guide warns that recurring or misconfigured tasks can cause repeated daily summaries; one clear schedule is easier to control than two overlapping ones.

Why this setup works for a service business

• One output is easier to review between calls and field work.
• A clear time and goal separate useful routines from vague reminders.
• A draft-only first run keeps the owner in the approval loop.
• A duplicate check prevents two schedules from doing the same job.

Once the first result is correct, refine the task from evidence: keep what saved time, clarify what was misunderstood and remove any field that did not help. The broader Marblism training guide explains where Tasks fit alongside chat, the Brain and employee Guidelines.