January 22, 2026

Salesforce + Slack: never miss a stale deal follow up

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Stale deals don’t usually die loudly. They just sit there in Salesforce, untouched, while your team swears they’ll “follow up tomorrow.” Then “tomorrow” turns into next week.

Sales Ops feels it first, because reporting gets messy fast. Sales Managers feel it in forecast calls. And if you run a small agency or services business, you feel it in cash flow. This Salesforce Slack follow-ups automation makes stalled Opportunities impossible to ignore, without you nagging people all day.

It runs every morning, finds deals that haven’t moved stages, drafts the follow-up for you, posts a clean summary to Slack, and creates a Salesforce Task so the owner has a clear next action.

How This Automation Works

See how this solves the problem:

n8n Workflow Template: Salesforce + Slack: never miss a stale deal follow up

Click to explore

flowchart LR

    subgraph sg0["Schedule Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
        n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Edit Fields", pos: "b", h: 48 }
        n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/salesforce.svg' width='40' height='40' /></div><br/>Perform a query"]
        n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/salesforce.svg' width='40' height='40' /></div><br/>Get an opportunity"]
        n4@{ icon: "mdi:robot", form: "rounded", label: "Message a model", pos: "b", h: 48 }
        n5@{ icon: "mdi:web", form: "rounded", label: "query_soql", pos: "b", h: 48 }
        n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Create Task"]
        n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Parse JSON"]
        n8@{ icon: "mdi:message-outline", form: "rounded", label: "Send Email SMTP Customer", pos: "b", h: 48 }
        n9["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Send Message To Internal Team"]
        n7 --> n8
        n7 --> n6
        n7 --> n9
        n5 -.-> n4
        n1 --> n2
        n4 --> n7
        n2 --> n3
        n0 --> n1
        n3 --> n4
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n0 trigger
    class n4 ai
    class n5,n6 api
    class n7 code
    classDef customIcon fill:none,stroke:none
    class n2,n3,n6,n7,n9 customIcon

The Challenge: Stale Opportunities That Quietly Kill Revenue

If your pipeline is even moderately busy, “stale” deals are guaranteed. Reps get pulled into calls, proposals, internal fires, and suddenly an Opportunity hasn’t moved stages in two weeks. The worst part is that the work to fix it is scattered: check the Opportunity, skim Notes, figure out who the main Contact is, craft a follow-up, then remember to log a Task so it’s trackable. That context switching is exhausting, so the follow-up gets delayed again. And again.

It adds up fast. Here’s where it breaks down in real teams:

Someone has to manually hunt for stuck deals, usually right before a pipeline meeting.
Follow-ups get written from scratch, which means inconsistent tone and missed details from prior Notes.
Slack reminders happen, but they’re vague, so nobody knows what to do next.
Without a Task tied to the Opportunity owner, accountability turns into “I thought you handled it.”

The Fix: Daily Stale-Deal Detection + AI Follow-Up Drafts

This workflow runs automatically every morning at 8:00 and checks Salesforce for Opportunities that have been sitting in the same stage for too long. You choose the threshold (7 days, 14 days, 30 days) and the workflow queries for deals where your Stage_Unchanged_Days__c matches that value, excluding Closed Won and Closed Lost. For each stale Opportunity, it pulls the full record, then sends the deal context to an OpenAI model. The model can also fetch recent Notes, the primary Contact, and the Opportunity Owner via a SOQL helper, then returns one structured JSON response with everything you need: a client email draft, an SMS template, a Slack-ready summary, and a Salesforce Task payload. n8n parses that JSON, sends the email through SMTP, posts the summary to Slack, and creates the Task assigned to the Opportunity owner so the deal gets a real next step.

The workflow starts on a schedule and immediately sets your “stale” definition. Then it finds matching Opportunities, loops through them, and generates drafts using the deal’s real history (Notes and owner/contact context). Finally, it dispatches three outcomes in parallel: email out, Slack update in, and a Salesforce Task logged where it belongs.

What Changes: Before vs. After

What This Eliminates

Impact You’ll See

Manually searching Salesforce each morning for “what’s stuck.”
Reps rewriting follow-up messages with zero context from Notes.
Slack pings that lack specifics and get ignored.
Creating Tasks by hand (or not creating them at all).

Most teams get about 2–4 hours a week back from admin work alone.
Stale deals surface daily, not during last-minute forecast panic.
Follow-ups are clearer because they reflect the Opportunity’s real history.
Owners get assigned Tasks automatically, so accountability is baked in.
Sales Managers get a cleaner Slack signal instead of scattered updates.

Real-World Impact

Say you have 12 stale Opportunities in a week. Manually, a rep might spend about 10 minutes per deal to open the record, scan Notes, find the right contact, draft a follow-up, and then create a Task. That’s about 2 hours of pure admin. With this automation, the rep spends maybe 5 minutes reviewing what’s drafted (Slack summary plus email), then hits send or tweaks wording. The busywork drops to about an hour, and the follow-up actually happens.

Requirements

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Salesforce to query Opportunities and assign Tasks
Slack to notify the team or deal owner
OpenAI API key (get it from the OpenAI dashboard)

Skill level: Intermediate. You’ll connect credentials, edit a SOQL query, and test with a few Opportunities.

Need help implementing this? Talk to an automation expert (free 15-minute consultation).

The Workflow Flow

Morning schedule kicks it off. At 8:00 each day, the workflow starts and sets your stale threshold (for example, 14 days in the same stage).

Salesforce gets queried for stalled deals. It pulls Opportunities where Stage_Unchanged_Days__c matches the threshold and the stage is not Closed Won or Closed Lost, then fetches full deal details per Opportunity.

AI drafts the next actions with real context. The OpenAI step generates one structured JSON response that includes an email, an SMS template, a Slack summary, and a Salesforce Task payload. It can also pull recent Notes, the primary Contact, and the owner using a SOQL helper call.

Messages go out and the Task gets logged. n8n parses the JSON, sends the client email via SMTP, posts the summary to Slack, and creates a Salesforce Task assigned to the Opportunity owner.

You can easily modify the stale threshold to match your pipeline rhythm, or change the Slack destination from a channel to a specific rep based on ownership. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Trigger

Set the workflow timing so the automation runs on a consistent schedule.

Add and open Scheduled Automation Start.
Set the schedule rule to run at Hour 8 (as configured under the interval trigger).
Connect Scheduled Automation Start to Assign Stale Threshold.

Step 2: Connect Salesforce and Identify Stale Opportunities

Define the stale window and query Salesforce for opportunities that have not changed recently.

Open Assign Stale Threshold and set the stale_days value to 14.
Open Retrieve Stale Opportunities and set Resource to search.
Set the Query to =Select id from opportunity where Stage_Unchanged_Days__c = {{ $json.stale_days }} And StageName Not In ('Closed Won', 'Closed Lost').
Credential Required: Connect your salesforceOAuth2Api credentials for Retrieve Stale Opportunities.
Open Fetch Opportunity Record and set Resource to opportunity and Operation to get.
Set Opportunity ID to ={{ $json.Id }}.
Credential Required: Connect your salesforceOAuth2Api credentials for Fetch Opportunity Record.

Step 3: Set Up the AI Drafting Assistant

Use the AI model to draft the email, SMS, Slack message, and task payload based on Salesforce data.

Open Generate Follow-Up Drafts and confirm the model is set to gpt-5.1.
Ensure the system prompt includes the full instructions and the JSON output schema as configured.
Credential Required: Connect your openAiApi credentials for Generate Follow-Up Drafts.
Open SOQL Query Helper and set URL to https://[mydomain].salesforce.com/services/data/v64.0/query/.
Set the query parameter q to ={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('parameters0_Value', ``, 'string') }}.
Credential Required: Connect your salesforceOAuth2Api credentials for SOQL Query Helper.
Confirm SOQL Query Helper is connected as an AI tool for Generate Follow-Up Drafts (credentials are configured on the tool node).

Step 4: Parse the AI Output

Convert the AI response into structured JSON for downstream actions.

Open Extract Draft Output and set JavaScript Code to return JSON.parse($input.first().json.output[0].content[0].text).
Ensure Generate Follow-Up Drafts connects to Extract Draft Output.

Extract Draft Output outputs to both Dispatch Client Email, Create Follow-Up Task, and Notify Internal Slack in parallel.

Step 5: Configure Output Actions

Send the drafted messages and create a Salesforce task for the opportunity owner.

Open Dispatch Client Email and set To Email to ={{ $json.email.to }}.
Set Subject to ={{ $json.email.subject }} and Text to ={{ $json.email.body }}.
Set From Email to [YOUR_EMAIL] and Email Format to text.
Credential Required: Connect your smtp credentials for Dispatch Client Email.
Open Notify Internal Slack and set Text to ={{ $('Extract Draft Output').item.json.slack.message }}.
Set Channel to your target channel ID (currently [YOUR_ID]).
Credential Required: Connect your slackApi credentials for Notify Internal Slack.
Open Create Follow-Up Task and set URL to https://[mydomain ].salesforce.com/services/data/v60.0/sobjects/Task.
Set Method to POST, Specify Body to json, and JSON Body to ={{ $json.task.api_body }}.
Credential Required: Connect your salesforceOAuth2Api credentials for Create Follow-Up Task.

⚠️ Common Pitfall: The AI response must be valid JSON. If the AI returns extra text, Extract Draft Output will fail to parse. Keep the system prompt intact to enforce the JSON-only response.

Step 6: Test & Activate

Validate the workflow end-to-end, then turn it on for daily execution.

Click Execute Workflow to run Scheduled Automation Start manually.
Confirm that Retrieve Stale Opportunities returns records and Fetch Opportunity Record pulls full details.
Verify Generate Follow-Up Drafts produces output that Extract Draft Output parses into email, sms, slack, and task objects.
Check that the email is sent by Dispatch Client Email, a Slack message is posted by Notify Internal Slack, and a task is created by Create Follow-Up Task.
When successful, toggle the workflow to Active so it runs at the scheduled time.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Watch Out For

Salesforce OAuth credentials can expire or lack the right scopes. If things break, check the Salesforce connected app and the n8n credential status first.
If you’re querying Notes or related objects through the SOQL helper, your Salesforce permissions matter. A user that can read Opportunities but not Notes will produce thin AI drafts.
Default AI prompts are generic. Add your product language and tone in the OpenAI “Generate Follow-Up Drafts” step early, or you will keep rewriting messages every morning.

Common Questions

How quickly can I implement this Salesforce Slack follow-ups automation?

About 30–45 minutes if your Salesforce, Slack, SMTP, and OpenAI credentials are ready.

Can non-technical teams implement this Salesforce Slack follow-ups automation?

Yes, but someone should be comfortable editing a Salesforce query and testing with a few Opportunities. No app code is required.

Is n8n free to use for this Salesforce Slack follow-ups workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs, which are usually a few cents per batch of deals depending on message length.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

How do I adapt this Salesforce Slack follow-ups solution to my specific challenges?

You can change the stale definition in the “Assign Stale Threshold” step, and refine which deals qualify by editing the SOQL in “Retrieve Stale Opportunities.” If you want different messaging, adjust the prompt in “Generate Follow-Up Drafts,” then keep the same JSON structure so “Extract Draft Output” can still route email, Slack, and the Task payload. Common customizations include routing Slack messages to the owner instead of a channel, filtering by minimum amount, and skipping certain record types.

Why is my Salesforce connection failing in this workflow?

Usually it’s expired OAuth credentials or missing permissions on the Salesforce user tied to the n8n credential. Check that the user can read Opportunities, related Contacts, and any Notes you’re pulling via SOQL, then re-auth in n8n and re-run a single test deal.

What’s the capacity of this Salesforce Slack follow-ups solution?

On n8n Cloud Starter, you’re typically fine for a small team doing daily checks, and higher plans handle more volume. If you self-host, there’s no execution limit; it mainly depends on your server and Salesforce/OpenAI rate limits. In practice, this workflow processes deals one-by-one through the AI step, so if you have a large backlog (hundreds of stale deals), expect the run to take a while and consider batching or limiting the query.

Is this Salesforce Slack follow-ups automation better than using Zapier or Make?

Often, yes. This workflow mixes a scheduled Salesforce query, AI generation that returns structured JSON, and a multi-branch output (email + Slack + Task) in one place, which is easier to maintain in n8n when logic grows. n8n also gives you a self-hosting path if you don’t want per-task pricing to creep up as volume increases. Zapier or Make can still be fine for a simple “find records then send a Slack message” setup. The moment you care about consistent drafts, SOQL helpers, or Salesforce Task payloads, n8n is usually the cleaner option. Talk to an automation expert if you’re weighing tradeoffs.

Once this is live, stalled deals stop slipping through the cracks, and your team gets a clear next action every morning. Set it up once, then let the workflow do the nudging.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"id": "",
"name": "Automated Salesforce Follow-Up Flow",
"versionId": "",
"meta": {
"instanceId": "5a778fdd64f8500f933ee454f82f9b879482337261575ab4c4de9069e8a53737",
"templateId": null,
"templateCredsSetupCompleted": null
},
"nodes": [
{
"id": "flowpast-topbar-11157",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
50
],
"parameters": {
"color": 7,
"width": 1330,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "e9d9200c-3696-4f76-b04b-9472c205a39a",
"name": "Scheduled Automation Start",
"type": "n8n-nodes-base.scheduleTrigger",
"position": [
0,
170
],
"parameters": {
"rule": {
"interval": [
{
"triggerAtHour": 8
}
]
}
},
"typeVersion": 1.2
},
{
"id": "62cf078e-066a-492d-9882-c8dac3ea5baf",
"name": "Assign Stale Threshold",
"type": "n8n-nodes-base.set",
"position": [
260,
215
],
"parameters": {
"options": [],
"assignments": {
"assignments": [
{
"id": "2790e2d6-bf5f-4d3a-a02a-705afd3b1caf",
"name": "stale_days",
"type": "number",
"value": 14
}
]
}
},
"typeVersion": 3.4
},
{
"id": "8a0f4a2f-9339-4de1-a614-e00ef8298139",
"name": "Retrieve Stale Opportunities",
"type": "n8n-nodes-base.salesforce",
"position": [
540,
150
],
"parameters": {
"query": "=Select id from opportunity where Stage_Unchanged_Days__c =  {{ $json.stale_days }} And StageName Not In ('Closed Won', 'Closed Lost')",
"resource": "search"
},
"credentials": {
"salesforceOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1
},
{
"id": "7ba41db7-0f84-4cd3-8a19-b0ea640601b5",
"name": "Fetch Opportunity Record",
"type": "n8n-nodes-base.salesforce",
"position": [
830,
235
],
"parameters": {
"resource": "opportunity",
"operation": "get",
"opportunityId": "={{ $json.Id }}"
},
"credentials": {
"salesforceOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1
},
{
"id": "75389940-46a3-4512-aca9-b8c21bab5f9b",
"name": "Generate Follow-Up Drafts",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
1100,
185
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "list",
"value": "gpt-5.1",
"cachedResultName": "GPT-5.1"
},
"options": [],
"responses": {
"values": [
{
"role": "system",
"content": "=You are a Salesforce Sales Follow-Up Assistant.\n\nYour job:\n- When an Opportunity stage has not changed for some time, draft:\n  1) A follow-up EMAIL to the client\n  2) A short SMS to the client\n  3) A concise SLACK message to the internal team\n\nYou will receive:\n- A Salesforce Opportunity record as JSON (called `opportunity`).\n{{ JSON.stringify($json) }}\n- Key fields include (but are not limited to):\n  - Id, Name, AccountId, StageName, Stage_Unchanged_Days__c,\n    Amount, CloseDate, Type, LeadSource, OwnerId,\n    MainCompetitors__c, OrderNumber__c, IsClosed, IsWon.\n\nYou have access to the following tool:\n- SOQL Query Helper(soql: string)\n  - Executes a SOQL query and returns a list of records as JSON\n    with the fields specified in the SELECT clause.\n\nTOOL USAGE \u2013 ALWAYS DO THESE QUERIES\n\n1) Fetch Opportunity Notes\n- Goal: personalize messages with recent context / pain points / last interactions.\n- Call `SOQL Query Helper` with a SOQL that fetches notes on this Opportunity, for example:\n  - SELECT Id, Title, Body\n    FROM Note\n    WHERE ParentId = '{opportunity.Id}'\n    ORDER BY LastModifiedDate DESC\n    LIMIT 5\n- Use the returned notes (Title and Body) to understand:\n  - recent discussions,\n  - customer concerns,\n  - agreed next steps,\n  - any specific products or competitors mentioned.\n\n2) Fetch Primary Contact on the Account\n- Goal: address the right person and use email/phone where possible.\n- Call `SOQL Query Helper` with a SOQL that fetches ONE contact for the Opportunity\u2019s Account that has an Email, for example:\n  - SELECT Id, Name, Email, Phone\n    FROM Contact\n    WHERE AccountId = '{opportunity.AccountId}'\n      AND Email != null\n    ORDER BY LastModifiedDate DESC\n    LIMIT 1\n- Treat the returned Contact (if any) as the **primary contact**.\n- Use:\n  - Contact.Name to personalize greeting (\u201cHi <Name>,\u201d).\n  - Contact.Email as the assumed receiver of the email.\n  - Contact.Phone for SMS (if Phone is null, still write an SMS template as if sent to their mobile).\n- If no contact is returned:\n  - Use a generic salutation like \u201cHi there,\u201d\n  - Still draft the email and SMS text as templates.\n\n3) Fetch Opportunity Owner (for Signature and Slack)\n- Goal: include the owner\u2019s name (and optionally email) in the email signature and Slack mentions.\n- Call `SOQL Query Helper` with a SOQL that returns the Owner user, for example:\n  - SELECT Id, Name, Email\n    FROM User\n    WHERE Id = '{opportunity.OwnerId}'\n    LIMIT 1\n- Use:\n  - Owner.Name in the email signature and in the Slack message.\n  - Owner.Email in the signature if available.\n  - Owner.Id (or opportunity.OwnerId) as the Task OwnerId.\n- If no owner record is returned, you can:\n  - Still use opportunity.OwnerId for the Task OwnerId field.\n  - Sign the email as \u201cYour account manager\u201d without a name.\n\nYou should:\n- Perform up to THREE calls to `SOQL Query Helper` (Notes, Contact, Owner) at the beginning.\n- Incorporate the returned data into your reasoning before drafting any messages.\n- If a query returns no rows, handle it gracefully and write more generic content.\n\nCOMMUNICATION LOGIC\n\n- This assistant is triggered because `Stage_Unchanged_Days__c` indicates the stage has not changed for some time.\n- Adapt the messaging based on `StageName` and status flags:\n  - If the Opportunity is still open (IsClosed = false):\n    - Use a polite, value-driven nudge to move things forward.\n    - Reference any relevant notes or previous conversations.\n  - If the Opportunity is Closed Won (IsClosed = true AND IsWon = true):\n    - Treat it as a post-sale check-in, onboarding, or upsell touch.\n    - Confirm everything is going smoothly and offer next steps.\n  - If the Opportunity is Closed Lost (IsClosed = true AND IsWon = false):\n    - Keep it short: thank them, request brief feedback if appropriate, and keep the door open for future opportunities.\n- Refer to the delay naturally (\u201cover the past few weeks\u201d, \u201crecently\u201d) instead of exact day counts,\n  unless referencing Stage_Unchanged_Days__c is clearly helpful.\n\nSTYLE GUIDELINES\n\nEMAIL:\n- Audience: the primary Contact (if found) or generic client.\n- Tone: professional, friendly, concise.\n- Structure:\n  - Greeting: use Contact.Name if available; otherwise \u201cHi there,\u201d.\n  - Intro: who you are + why you\u2019re reaching out (reference Opportunity Name in natural language:\n    e.g., \u201cyour order for mobile generators\u201d).\n  - Context: mention that things have been quiet / unchanged for a while, referencing notes if possible.\n  - Value: 1\u20133 sentences focusing on next steps, clarifying questions, or how you can help.\n  - CTA: clear and simple (e.g., propose a time to talk, ask for confirmation/feedback).\n  - Signature:\n    - Include Owner.Name (and Owner.Email if available).\n    - Include company name or generic role (\u201cSales Team\u201d) if needed.\n- Do NOT invent discounts, promises, or contractual commitments that are not mentioned.\n\nSMS:\n- Very short and to the point.\n- Assume they know who you/your company are (add a short identifier like \u201c\u2013 <Owner Name>, <Company>\u201d).\n- Use a clear CTA (e.g., \u201cReply if you\u2019d like to schedule a quick call this week.\u201d).\n- If Contact.Phone is missing, still generate an SMS template as if it will be sent to the right number later.\n\nSLACK (INTERNAL TEAM):\n- Target: Opportunity Owner and sales / deals channel.\n- Include:\n  - Opportunity Name, StageName, Amount, CloseDate, Stage_Unchanged_Days__c.\n  - Account/Contact name (if available).\n  - Short summary of key insights from Notes.\n  - Short summary of the angle of the email/SMS (no need to paste the full text).\n- Recommend the next internal action (e.g., \u201ccall the client\u201d, \u201creview pricing\u201d, \u201cconfirm delivery timeline\u201d).\n- Mention the Owner by name; if your environment supports @mentions, format text in a way that could be used\n\nTASK (for Owner):\n- Purpose: ensure there is a clear owner action in Salesforce linked to this Opportunity.\n- The Task should:\n    - Be assigned to the Opportunity Owner (OwnerId = opportunity.OwnerId or Owner.Id).\n    - Be related to the Opportunity (WhatId = opportunity.Id).\n    - Have a clear Subject describing the follow-up (e.g., \u201cFollow up on stalled opportunity \u2013 <Opportunity Name>\u201d).\n    - Have a Description summarizing:\n      - Why the task was created (stage unchanged),\n      - Key context from notes,\n      - The gist of the email/SMS that will be sent.\n    - Use reasonable default fields:\n      - Status: \"Not Started\"\n      - Priority: \"Normal\"\n    - DueDate can be set conceptually to \u201ctoday\u201d or \u201ctomorrow\u201d as a short text description in the Description,\nbut leave it out of the api_body if you are not given a date field.\n\nOUTPUT FORMAT\n\nReturn ONLY a JSON object with this structure (no extra text, no markdown):\n\n{\n  \"email\": {\n    \"to\":\"email\"\n    \"subject\": \"string\",\n    \"body\": \"string\"\n  },\n  \"sms\": {\n    \"to\":\"Phone\"\n    \"body\": \"string\"\n  },\n  \"slack\": {\n    \"channel_hint\": \"string\",\n    \"message\": \"string\"\n  },\n  \"task\": {\n    \"subject\": \"string\",\n    \"description\": \"string\",\n    \"status\": \"string\",\n    \"priority\": \"string\",\n    \"api_body\": {\n    \"Subject\": \"string\",\n    \"Description\": \"string\",\n    \"Status\": \"string\",\n    \"Priority\": \"string\",\n    \"OwnerId\": \"string\",\n    \"WhatId\": \"string\"\n  }\n}\n\n- email.subject: clear and concise.\n- email.body: multi-paragraph email using \"\\n\\n\" for paragraph breaks.\n- sms.body: 1\u20133 sentences max.\n- slack.channel_hint: short hint to help route this message (e.g., \"#sales\", \"@OwnerName\", \"#opportunity-followup\").\n- slack.message: a concise message summarizing the situation and internal recommendation.\n\nREASONING\n\nBefore you generate the JSON:\n- Think through:\n  - What is the current stage and has it stalled?\n  - What do the Notes say about last interactions and customer concerns?\n  - Who is the primary Contact and how to address them?\n  - Who is the Owner and how to include them in signature and Slack?\n  - What is the most reasonable, low-friction next step for the client?\n  - What does the internal team need to know and do?\n\nThen, generate the JSON output EXACTLY in the specified schema.\n"
}
]
},
"builtInTools": []
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2
},
{
"id": "29cfe789-91e7-48ef-8f5f-b7e15275b883",
"name": "SOQL Query Helper",
"type": "n8n-nodes-base.httpRequestTool",
"position": [
1210,
360
],
"parameters": {
"url": "https://[mydomain].salesforce.com/services/data/v64.0/query/",
"options": [],
"sendQuery": true,
"authentication": "predefinedCredentialType",
"queryParameters": {
"parameters": [
{
"name": "q",
"value": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('parameters0_Value', ``, 'string') }}"
}
]
},
"toolDescription": "Use to query opportunity notes ",
"nodeCredentialType": "salesforceOAuth2Api"
},
"credentials": {
"salesforceOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.3
},
{
"id": "cd24d4f9-9d47-4994-9b0a-26253ec5f7cd",
"name": "Extract Draft Output",
"type": "n8n-nodes-base.code",
"position": [
960,
440
],
"parameters": {
"jsCode": "return JSON.parse($input.first().json.output[0].content[0].text)"
},
"typeVersion": 2,
"alwaysOutputData": true
},
{
"id": "7f5a791d-7a0e-42ec-b46e-599aa85c458b",
"name": "Dispatch Client Email",
"type": "n8n-nodes-base.emailSend",
"position": [
620,
675
],
"webhookId": "0d00699f-5b81-4090-a172-fdc18f658efa",
"parameters": {
"text": "={{ $json.email.body }}",
"options": [],
"subject": "={{ $json.email.subject }}",
"toEmail": "={{ $json.email.to }}",
"fromEmail": "[YOUR_EMAIL]",
"emailFormat": "text"
},
"credentials": {
"smtp": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.1
},
{
"id": "c9998bd2-6222-45b0-917e-b9cb1a7948b1",
"name": "Notify Internal Slack",
"type": "n8n-nodes-base.slack",
"position": [
940,
710
],
"webhookId": "1dbf4e8a-16a6-4c49-9240-2d3c7f12d505",
"parameters": {
"text": "={{ $('Extract Draft Output').item.json.slack.message }}",
"select": "channel",
"channelId": {
"__rl": true,
"mode": "id",
"value": "[YOUR_ID]"
},
"otherOptions": []
},
"credentials": {
"slackApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.3
},
{
"id": "33b39d65-3f0e-4f4d-ba59-6770bd21a831",
"name": "Create Follow-Up Task",
"type": "n8n-nodes-base.httpRequest",
"position": [
1230,
660
],
"parameters": {
"url": "https://[mydomain ].salesforce.com/services/data/v60.0/sobjects/Task",
"method": "POST",
"options": [],
"jsonBody": "={{ $json.task.api_body }}",
"sendBody": true,
"specifyBody": "json",
"authentication": "predefinedCredentialType",
"nodeCredentialType": "salesforceOAuth2Api"
},
"credentials": {
"salesforceOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.2
}
],
"pinData": [],
"connections": {
"Extract Draft Output": {
"main": [
[
{
"node": "Dispatch Client Email",
"type": "main",
"index": 0
},
{
"node": "Create Follow-Up Task",
"type": "main",
"index": 0
},
{
"node": "Notify Internal Slack",
"type": "main",
"index": 0
}
]
]
},
"SOQL Query Helper": {
"ai_tool": [
[
{
"node": "Generate Follow-Up Drafts",
"type": "ai_tool",
"index": 0
}
]
]
},
"Create Follow-Up Task": {
"main": [
[]
]
},
"Assign Stale Threshold": {
"main": [
[
{
"node": "Retrieve Stale Opportunities",
"type": "main",
"index": 0
}
]
]
},
"Generate Follow-Up Drafts": {
"main": [
[
{
"node": "Extract Draft Output",
"type": "main",
"index": 0
}
]
]
},
"Retrieve Stale Opportunities": {
"main": [
[
{
"node": "Fetch Opportunity Record",
"type": "main",
"index": 0
}
]
]
},
"Scheduled Automation Start": {
"main": [
[
{
"node": "Assign Stale Threshold",
"type": "main",
"index": 0
}
]
]
},
"Fetch Opportunity Record": {
"main": [
[
{
"node": "Generate Follow-Up Drafts",
"type": "main",
"index": 0
}
]
]
},
"Dispatch Client Email": {
"main": [
[]
]
}
}
}