Workflows· Sales & Outreach

    The Sales Response Pipeline

    Automatically drafts a personalized sales reply from CRM context for incoming lead emails and notifies the responsible sales rep for review before it is sent.

    automatingwriting

    Description

    Steps

    Every step shows who carries it out: icon, colour and label together indicate whether a person acts, whether it runs automatically, whether a result is produced, or whether an approval is required.

    01Person

    A new email tagged with the Sales Lead label starts the process.

    02Automated

    03Automated

    04Automated

    05Result

    Key
    PersonAutomatedResultApproval

    Requirements and operations

    Requirements

    • Email tool Gmail, Outlook or a comparable tool that receives leads and can save drafts in the thread.
    • CRM system HubSpot, Salesforce or Pipedrive for context and interaction history.
    • Team chat (optional) Slack, Teams or Discord for notifying the sales owner.
    • LLM access OpenAI, Claude or Gemini, via an API key.

    Testing

    • Test email Send a test inquiry from a known CRM address tagged with the Sales Lead label.
    • CRM lookup Check whether contact, company, deal stage and interaction history are loaded correctly.
    • Draft quality Assess the draft for concrete relevance to the inquiry, CRM context, matching tone and length, and a clear call to action.
    • Edge cases Check the behavior without a CRM entry, with multiple matches, with multilingual inquiries, and with very long emails.

    Go-live

    • Approval to start Activate the workflow only once the CRM lookup, drafting and notification run reliably.
    • Pilot Start with one or two sales owners and review the drafts before they are sent.
    • Refine Adjust tone and template based on the versions that were actually sent.
    • Expand Add urgency scoring, language detection or multiple draft variants for comparison if needed.

    Common issues

    • CRM match runs on the name instead of the address Switch the search field in the CRM lookup to the email address.
    • Draft is saved as a new email instead of a reply Enable the "Save as reply" option in the mail tool.
    • Draft stays too generic Bind the CRM fields as variables and set the tone in the prompt.
    • Duplicate drafts on repeated triggers Check the thread ID for an already existing draft before creating a new one.

    Builder Prompt

    GOAL
    Build a workflow that automatically loads the CRM context for incoming sales inquiries and files a personalized reply draft in the same mail thread. The responsible sales owner is then notified and reviews the draft before it is sent.
    
    Adapt the structure to the concepts of your automation tool, for example nodes, steps, zaps or agent actions. While doing so, preserve the trigger logic, the sequence and the data flow.
    
    TRIGGER
    Type: new incoming email in the email tool (Gmail, Outlook or comparable).
    Filter: only emails tagged with the Sales Lead label or category.
    
    STEPS
    1. Extract email data: sender address, subject, content and thread ID.
    2. Dedup check: if a draft has already been generated for this thread ID, abort the run so no duplicate drafts are created.
    3. CRM lookup (HubSpot, Salesforce or Pipedrive): match on the email address, not the name. Load contact name, company, deal status, interaction history, notes and tags, and the responsible owner.
    4. AI step: create the reply draft, using the prompt below exactly.
    5. Save the draft: as a reply in the same mail thread, not as a new email, ready to send with one click.
    6. Output: notify the sales owner in the team chat, with lead details and a link to the draft.
    
    PROMPT (use exactly as written)
    Sales reply generator:
    """
    You act as an experienced sales representative creating professional email replies for incoming lead inquiries.
    
    CONTEXT INFORMATION FROM CRM:
    - Contact name: [CONTACT_NAME]
    - Company: [COMPANY]
    - Current deal status: [DEAL_STATUS]
    - Past interactions: [INTERACTION_HISTORY]
    - Notes/Tags: [CRM_NOTES]
    
    INCOMING EMAIL:
    From: [SENDER_EMAIL]
    Subject: [EMAIL_SUBJECT]
    Content: [EMAIL_CONTENT]
    
    TASK:
    Create a professional, personalized email reply draft that
    1. addresses the specific inquiry and answers all questions,
    2. uses the CRM context, for example by mentioning earlier conversations or referring to the deal stage,
    3. uses [COMPANY_TONE],
    4. contains a clear call to action, for example a meeting suggestion or next steps,
    5. is at most [MAX_LENGTH] words long.
    
    FORMAT:
    Output only the finished email text, from the salutation to the closing. No explanations, no meta commentary.
    """
    
    DATA FLOW
    Step 1 to step 3: sender address for the CRM match, thread ID for the dedup check and draft filing.
    Step 1 to step 4: sender address, subject and content of the email.
    Step 3 to step 4: contact name, company, deal status, interaction history and CRM notes.
    Step 3 to step 6: the responsible owner as the recipient of the notification.
    Step 4 to step 5: the finished draft text.
    
    ERROR HANDLING
    No CRM entry found: create the draft anyway, using only the email content, and flag this clearly in the owner notification.
    Multiple CRM matches: choose the most recent active deal and flag this choice in the notification.
    Inquiry in a different language: create the draft in the language of the inquiry.
    No owner set in the CRM: send the notification to a defined fallback channel.
    
    PLACEHOLDER CONVENTION
    All placeholders in square brackets are variables. Map all email and CRM placeholders dynamically, as described in the data flow. Not dynamic are [COMPANY_TONE] and [MAX_LENGTH]: set these manually before activation. List all placeholders that require manual configuration separately at the end.
    
    SELF CHECK BEFORE COMPLETION
    Check, before you report the workflow as finished:
    1. Are all steps connected correctly, in particular the dedup check before the draft is created?
    2. Is the prompt inserted in full and unchanged, and are all dynamic placeholders mapped?
    3. Is the draft stored as a reply in the thread, not as a new email, and does the CRM match run on the email address?
    4. Are all points listed that require manual configuration: the Sales Lead label, CRM access, the LLM API key, the team chat channel, [COMPANY_TONE] and [MAX_LENGTH]?

    Working prompts

    Sales reply generator

    The prompt for the AI step that generates the reply draft from the CRM context and the email content. Usable on its own, also outside the full workflow specification.

    You act as an experienced sales representative creating professional email replies for incoming lead inquiries.
    
    CONTEXT INFORMATION FROM CRM:
    - Contact name: [CONTACT_NAME]
    - Company: [COMPANY]
    - Current deal status: [DEAL_STATUS]
    - Past interactions: [INTERACTION_HISTORY]
    - Notes/Tags: [CRM_NOTES]
    
    INCOMING EMAIL:
    From: [SENDER_EMAIL]
    Subject: [EMAIL_SUBJECT]
    Content: [EMAIL_CONTENT]
    
    TASK:
    Create a professional, personalized email reply draft that
    1. addresses the specific inquiry and answers all questions,
    2. uses the CRM context, for example by mentioning earlier conversations or referring to the deal stage,
    3. uses [COMPANY_TONE],
    4. contains a clear call to action, for example a meeting suggestion or next steps,
    5. is at most [MAX_LENGTH] words long.
    
    FORMAT:
    Output only the finished email text, from the salutation to the closing. No explanations, no meta commentary.

    JSON export

    Setup

    Two routes lead to the same result. Pick the one that fits your setup.

    Suitable when you want to build the workflow in your own automation tool.

    1. Open your workflow tool, for example n8n, Make, Zapier or Langdock.
    2. Create a new workflow and give it a name.
    3. Choose the AI-assisted build option if your tool offers one.
    4. Paste the builder prompt from above in full.
    5. Check the result against the step sequence in this document, then add your access credentials and channels.

    Suitable when you want to take the workflow over unchanged.

    1. Download the JSON file from the JSON export section.
    2. Open the workflow area of your tool and create a new workflow.
    3. Give it a name and confirm.
    4. Open the menu on the workflow name and choose to import a JSON file.
    5. Upload the file, then add your own access credentials.
    6. Run a test before you activate the workflow.

    Last reviewed:

    In the workshop this becomes your method.

    A single prompt becomes a repeatable method. We show that in the workshop From Prompt to Method.

    View workshops

    Related resources

    Browse all resources

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call