a weekly newsletter draft from the sources you choose

a newsletter bot needs an editorial brief before it needs a schedule: who reads the issue, which sources it may use and what deserves a place. ask it to turn that list into a weekly draft in your chat, with links kept beside each item. you check the selection and wording. keep sending on ask every time so an issue never leaves without allow.

by the dusk bot team · checked 12 november 2026 · how we made this

the routine

first send your bot the actual source urls and describe the reader. the routine below uses that list, so there is no need to invent a publication or connect a mailing platform.

paste this into a chat with your bot

every thursday at 3pm, draft next week’s issue in this chat. write for independent workshop owners using the sources list i gave you. include only material published since the last issue, or mark an older item as background.

choose one main item and two shorter notes. for each, explain what happened, why a workshop owner might care and where the reader can check it. keep source links with the item. write an original summary; do not copy articles.

include a subject line, an opening and a closing question. finish with editorial notes: missing dates, unavailable sources and claims i should check. if nothing merits an issue, say so. do not invent a customer quote, a result or a personal experience. never send or publish.

when: thursday at 15:00, leaving time for an editorial review before next week
needs: your source urls, audience notes and a bot that can open web pages; no newsletter connector required

what comes back looks like this (an example, not a real inbox)

draft issue for sam’s workshop letter

subject: a clearer handover note

opening: this week, a small idea for the moment a repair changes hands.
main item: priya’s supplied workshop notes describe a handover card with room for the next person’s question. it may be worth discussing at your next team meeting. source: supplied priya notes, “handover card”.
short notes: held back; no other dated source met the brief.
closing question: what information is usually missing when a job reaches you?
editorial note: ask priya’s permission before quoting her. nothing sent.

make the source list an editorial boundary

give each url a reason to be there: original reporting, a product update or a reference you trust. say which topics to leave out. the bot should not fill an empty issue with loosely related news just to meet a word count.

keep a separate list of links already covered and ask the bot to compare against it. an updated page can look fresh while repeating an old announcement. if you need new sources, run a focused market research brief before changing the editorial list.

draft here, send after review

the draft comes back in chat; you paste it into your newsletter tool. copy the edited issue into your usual editor and check the subject, links and recipient list there.

if you later give a bot a supported way to send, choose Ask every time for sending. the Allow card is the send decision. do not set a daily amount it may send on its own if you want every issue reviewed. one exception: a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so give full-access bots Ask every time under sending.³ a social posting routine can turn the same approved notes into a different format.

leave room for an issue to be skipped

a source may be inaccessible, undated or thin. tell the bot to return an editorial question instead of padding the issue. summaries can still miss a qualification, so read the original before making its claim your own.

for a letter based on product changes, competitor monitoring offers a way to keep a dated change list. on your own computer, the newsletter routine needs dusk bot running and the machine awake. use dusk cloud if the draft must run while that computer is off.

the guard rails

set sending to Ask every time; publishing an issue requires your Allow
keep quotations brief and check permission before including someone’s private notes
check every destination link in the editor before sending to readers
remove unsupported claims even when they would make a stronger subject line

questions

selection and a first draft from a source list you maintain. it is useful when you have material but need help deciding what belongs together. you still own the editorial judgment.

can it write my personal opening?

give it the experience you want to describe in your own notes. without that, ask for a neutral opening. it should not invent a story about your week.

will the weekly issue send while i sleep?

this routine only drafts. keeping sending on Ask every time, with no daily sending allowance, means a supported send waits for your Allow. scheduled drafting on your computer also pauses while it sleeps.

sources

drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].