Block 1 - Schedule Trigger
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
How it works Runs every morning at 8:00 using the Schedule Trigger. Sets a value and queries Salesforce for Opportunities where equals that value and the stage is not Closed Won / Closed Lost. For ...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.set, n8n-nodes-base.salesforce, @n8n/n8n-nodes-langchain.openai, n8n-nodes-base.httprequesttool, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.emailsend
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Le Nguyen.
Original n8n.io sourcestale_days value and queries Salesforce for Opportunities where Stage_Unchanged_Days__c equals that value and the stage is not Closed Won / Closed Lost. query_soql tool to pull recent Notes, the primary Contact, and the Opportunity Owner, then returns a single JSON object with: Estimated setup time: ~30–45 minutes if your Salesforce, OpenAI, SMTP and Slack credentials are ready.
Create Stage_Unchanged_Days__c on Opportunity (Salesforce)
IF(
ISBLANK(LastStageChangeDate),
TODAY() - DATEVALUE(CreatedDate),
TODAY() - DATEVALUE(LastStageChangeDate)
)
Connect credentials in n8n
query_soql HTTP Tool. Configure your follow-up rules
stale_days to the threshold that defines a stalled deal (e.g. 7, 14, 30). Test safely
email, sms, slack, task.api_body). Go live
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Automate stale deal follow-ups in Salesforce with GPT-5.1, email, Slack & tasks |
|---|---|
| Complexity | advanced |
| Nodes | 16 |
| Categories | Lead Nurturing, AI Summarization |
| Author | Le Nguyen |
| Published | 23 Nov 2025 |
Use the JSON export at /data/workflows/11157/11157.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
How it works Runs every morning at 8:00 using the Schedule Trigger. Sets a value and queries Salesforce for Opportunities where equals that value and the stage is not Closed Won / Closed Lost. For ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Nurturing, AI Summarization use case.