How to write a strong workflow prompt

A good workflow prompt gives Rox enough structure to build something useful on the first pass.

Include these four things:

1. The trigger

Say exactly when the workflow should run.

Examples:

• every Friday at 4 PM

• before a timed event

• when a transcript is completed

• when a deal changes stage

• when a webhook is called

2. The context

Tell Rox what information it should use.

Examples:

• account data

• contact data

• meetings

• transcripts

• emails

• deal history

• generated values

• webhook payload data

3. The output

Be specific about what you want at the end.

Examples:

• Slack message

• email draft

• HTML report

• prep brief

• slides

• downloadable file

4. Guardrails

Tell Rox what matters and what to avoid.

Examples:

• do not invent dates or owners

• only run for meetings with external attendees

• only continue if a meaningful signal exists

• keep the output concise and factual

• notify the owner when the workflow is complete

A strong workflow prompt is not just descriptive. It is directional. It tells Rox what the job is, what inputs matter, and what a good result looks like.