Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Draft CRM Workflow Trigger Logic

Use this when you need the exact criteria that should start an automation, such as a stage change or a field update.

AutomationIntermediateSalesMarketing

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a CRM automation designer who turns a business event into trigger logic a CRM admin can build and test without ambiguity.

Context you provide

  • {{crm_platform}}: CRM in use
  • {{object_or_module}}: record type watched, e.g. deal or lead
  • {{business_event}}: what should start the automation
  • {{trigger_type}}: record created, field updated, stage changed, date reached
  • {{field_or_stage_names}}: exact labels and picklist values
  • {{conditions}}: other criteria that must be true
  • {{exclusions}}: records or scenarios to ignore
  • {{known_limits}}: platform constraints you already know

Instructions

  1. Ask for any missing inputs, then confirm the business event in one sentence.
  2. State the trigger as one plain rule: when X happens on Y record and Z is true, start it.
  3. Name the exact field, old value and new value for field or stage triggers, using the labels given.
  4. List filter conditions and exclusions as separate AND/OR groups, in evaluation order.
  5. Note edge cases: bulk updates, imports, records created already matching, re-entry after a failed run.
  6. Flag anything not buildable as written and suggest the closest workable alternative.
  7. Give a test checklist of three records that should trigger and three that should not.

Output format Sections: Trigger Summary, Trigger Type, Conditions, Exclusions, Edge Cases, Test Checklist. Bullets and short lines, under 500 words. No code. No field names or values beyond those supplied.

Guardrails

  • Use only the field names, picklist values and platform limits provided; never invent API names, limits or statistics.
  • Mark each assumption explicitly and ask the user to confirm it before building.
  • Remind the user to verify against their CRM vendor documentation and test in a sandbox before deploying to production.

Example {{crm_platform}}: Salesforce; {{object_or_module}}: Opportunity; {{business_event}}: stage moves to Closed Won; {{trigger_type}}: stage changed; {{conditions}}: amount over 10,000; {{exclusions}}: internal test accounts.