Friends of the Crustacean 🦞🤝FotC�
Friends of the Crustacean 🦞🤝•6d ago•
6 replies
Boni2k

Cronjob: disable status message

I've got the following cronjob:
System: Check Gmail for *** support requests and create reply drafts (do not send). 1) Run: `GOG_ACCOUNT=for *** /Users/for ***/clawd/scripts/for ***_support_drafts.sh` 2) For each `DRAFT_CREATED` line (now includes latest inbound `messageId` as 5th field): - Fetch the inbound message with `gog gmail get <messageId> --format full --json`. - Generate a short, helpful reply that matches Jonas’ usual tone, references relevant links (for ***), and asks for the minimal missing debug info. - Update the draft via `gog gmail drafts update <draftId> --subject <subject> --body <generated> --reply-to-message-id <messageId>`. 3) If at least one draft was created/updated, send a WhatsApp message to +*** summarizing how many drafts were created (optionally recipients/subjects). Only message when at least one draft was created. If there is an error, message *** with the error.


now every time the cronbjob runs I'm getting the following message:
Ran ⁠ GOG_ACCOUNT=*** /Users/***/clawd/scripts/***_support_drafts.sh ⁠ again.

•⁠  ⁠Result: ⁠ Created 0 draft(s), skipped 10 thread(s). ⁠
•⁠  ⁠No ⁠ DRAFT_CREATED ⁠ lines, so there were no drafts to fetch/update.
•⁠  ⁠Per your instruction, I did not send a WhatsApp message (only send when ≥1 draft created/updated).


It seems like these type of messages shouldn't be sent? I'm using Whatsapp as connection
Using Clawdbot 2026.1.12-2
Solution
The issue is that your cronjob script is outputting status lines (Result: Created 0 draft(s)...), and Clawdbot's default cronjob behavior is to send any script output as a WhatsApp message.

Two ways to fix this:

Option 1: Modify the script to only output when drafts are created


Make the script silent when DRAFT_CREATED lines are 0:

# At the end of your script, only output if drafts were created
if [ "$drafts_created" -gt 0 ]; then
    echo "DRAFT_CREATED: $drafts_created drafts"
else
    exit 0  # Exit silently
fi
Jump to solution
Was this page helpful?