The body_prompt field on an automation is the natural-language description of what each run should send. At fire time, the agent reads it, gathers the relevant tour data, and composes the actual message.
Be specific about what to include
Bad: "send the daysheet" Better: "Send today's daysheet: venue, address, hotel, full schedule, parking, hospitality (catering / buyout / wifi / green room), plus a one-line summary of tomorrow."
The agent uses your specificity to know what to fetch and what to omit.
Be specific about what to exclude
If your hospitality field tends to contain the whole rider with production specs, parking notes, and audio details — but you only want the comfort fields in the broadcast — say so:
"...hospitality: ONLY catering / buyout, wifi, green room, and shower/laundry. Skip production/parking/audio."
(That said, the composer prompt is already trained to filter hospitality narrowly; this is belt-and-suspenders.)
Always-surface vs nice-to-have
For critical fields like parking and van call, the composer treats them as REQUIRED. If the data is missing, it renders "Not listed — confirm with venue" so the crew sees the gap and chases it. You don't need to mention this in your prompt — it's hard-coded composer behavior.
Day-type awareness
The composer checks find_today.day_type (show / off / travel) FIRST, then composes appropriately:
- Show days get a full daysheet
- Off / travel days get a different message: tonight's hotel, distance to next show city, tomorrow's venue + load-in
You don't have to write a special prompt for off days — the composer pivots automatically.
Examples that work
Morning daysheet
"Send today's daysheet: venue, address, hotel name + address, full schedule with timezone (van call, load-in, soundcheck, doors, set, curfew), parking + shore power, hospitality (catering or buyout, wifi, green room, shower/laundry), plus a one-line preview of tomorrow."
Nightly heads-up
"Send tonight's hotel name + full address, and tomorrow morning's van call time + load-in time + venue + city + drive distance."
Pre-show reminder
"Send doors time and set time for tonight, plus any guest list reminders."
Examples that DON'T work well
"send everything"
Too vague — the agent has to guess. Likely composes a kitchen-sink message that's too long for SMS.
"send the daysheet for tomorrow"
Tomorrow's daysheet probably hasn't been advanced yet by 6am today. The composer will note "no data for tomorrow yet" and the broadcast will be a confused half-message. Schedule it later in the day, or rephrase to "next show day".
Iterate
If a broadcast goes out and is wrong (extra sections, missing field, weird tone), pause the automation, edit the body_prompt with more specific instructions, resume. Next run uses the updated prompt.