The photo should be copied out of Telegram into durable storage under a job-keyed path. n8n then writes the storage URL, Telegram message id, submitter, timestamp, and optional checksum back to the job record. If the job match is missing or ambiguous, the path should ask for a job number or send the item to a review queue instead of attaching it to the wrong order.
OpenClaw VPS Paid Trial Runbook Sample
This is a public sample for a fixed-price OpenClaw VPS trial. It shows the setup standard, handoff format, and verification style I would use on a throwaway host. It is not a claim about a private customer system.
Scope Table
This is the minimum handoff shape I would want before calling a VPS agent host repeatable.
Telegram Photo To Job Record
If a staff member sends a finished-sign photo to a Telegram agent, I would avoid letting the agent guess the job. The workflow should capture file id, sender, timestamp, and caption or job key, then let n8n validate that job against monday.com or the production source of truth.
Verification Commands
The real handoff would include command output screenshots or a short screen recording. The commands below are the kind of evidence I would capture.
id openclawsystemctl status openclaw --no-pagerss -tulpnufw status verbosefail2ban-client status || cscli decisions listls -la /etc/openclaw /opt/openclawjournalctl -u openclaw -n 80 --no-pager
Handoff Notes
- Use a fresh trial host and keep production credentials out of scope.
- Write down every non-default security decision and why it was chosen.
- Record service restart, log inspection, firewall, and monitoring checks.
- Do not put secrets in shell history, public repos, or systemd unit files.
- Do not leave app ports public unless the exposure is intentional and documented.
- Do not call a box hardened without proving SSH, firewall, service, and monitoring state.