Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Quick Overview This workflow runs daily to pull closed won HubSpot deals with upcoming renewal dates, scores each contract for renewal risk based on usage and engagement fields, and alerts the team...
n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.set, n8n-nodes-base.asana, n8n-nodes-base.slack
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Avkash Kakdiya.
Original n8n.io sourceThis workflow runs daily to pull closed-won HubSpot deals with upcoming renewal dates, scores each contract for renewal risk based on usage and engagement fields, and alerts the team by creating an Asana task, logging a HubSpot note, posting to Slack, and sending an email via Gmail.
Authorization: Bearer YOUR_HUBSPOT_API_KEY values in both HubSpot HTTP Request steps.renewal_date, hubspot_owner_id, product_usage_score, engagement_score, last_login_days, amount, dealname) or update the request and scoring logic to match your schema.YOUR_SLACK_CHANNEL_ID with the channel that should receive renewal-risk alerts.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 | Monitor contract renewal risk with HubSpot, Asana, Slack, and Gmail |
|---|---|
| Complexity | intermediate |
| Nodes | 14 |
| Categories | CRM, AI Summarization |
| Author | Avkash Kakdiya |
| Published | 11 Jun 2026 |
Use the JSON export at /data/workflows/16270/16270.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.
Quick Overview This workflow runs daily to pull closed won HubSpot deals with upcoming renewal dates, scores each contract for renewal risk based on usage and engagement fields, and alerts the team...
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 CRM, AI Summarization use case.