AutomationFlowsSlack & Telegram › Generate Weekly Plan

Generate Weekly Plan

Generate Weekly Plan. Uses httpRequest, slack. Scheduled trigger; 3 nodes.

Cron / scheduled trigger★☆☆☆☆ complexity3 nodesHTTP RequestSlack
Slack & Telegram Trigger: Cron / scheduled Nodes: 3 Complexity: ★☆☆☆☆ Added:

This workflow follows the HTTP Request → Slack recipe pattern — see all workflows that pair these two integrations.

The workflow JSON

Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →

Download .json
{
  "name": "Generate Weekly Plan",
  "nodes": [
    {
      "id": "cron",
      "name": "Every Sunday 20:00",
      "type": "n8n-nodes-base.cron",
      "typeVersion": 1,
      "position": [
        100,
        100
      ],
      "parameters": {
        "triggerTimes": {
          "item": [
            {
              "hour": 20,
              "minute": 0,
              "weekday": 0
            }
          ]
        }
      }
    },
    {
      "id": "http-build",
      "name": "Call Plan Endpoint",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 1,
      "position": [
        320,
        100
      ],
      "parameters": {
        "method": "POST",
        "url": "={{ $env.APP_URL + '/api/plan/generate' }}",
        "authentication": "headerAuth",
        "options": {
          "retryOnFail": true,
          "maxRetries": 3
        }
      },
      "credentials": {
        "httpHeaderAuth": {
          "name": "<your credential>"
        }
      }
    },
    {
      "id": "slack",
      "name": "Notify Slack (optional)",
      "type": "n8n-nodes-base.slack",
      "typeVersion": 1,
      "position": [
        540,
        100
      ],
      "parameters": {
        "channel": "fitness-notify",
        "text": "Weekly plan generation executed."
      },
      "disabled": true,
      "credentials": {
        "slackApi": {
          "name": "<your credential>"
        }
      }
    }
  ],
  "connections": {
    "http-build": {
      "main": [
        [
          {
            "node": "Notify Slack (optional)",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  }
}

Credentials you'll need

Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.

Pro

For the full experience including quality scoring and batch install features for each workflow upgrade to Pro

About this workflow

Generate Weekly Plan. Uses httpRequest, slack. Scheduled trigger; 3 nodes.

Source: https://github.com/Rruubeenn23/WebCursor/blob/ec319ac3dd0f628d3fcff2b80bd3aca56f77741a/n8n-workflows/generate-week.json — original creator credit. Request a take-down →

More Slack & Telegram workflows → · Browse all categories →

Related workflows

Workflows that share integrations, category, or trigger type with this one. All free to copy and import.

Slack & Telegram

Politician Social Media Monitor. Uses httpRequest, slack. Scheduled trigger; 7 nodes.

HTTP Request, Slack
Slack & Telegram

6️⃣ Full Pipeline - News → Webhook → Blotato → Analytics. Uses httpRequest, slack. Scheduled trigger; 7 nodes.

HTTP Request, Slack
Slack & Telegram

Flow. Uses httpRequest, slack, pagerDuty. Scheduled trigger; 7 nodes.

HTTP Request, Slack, Pager Duty
Slack & Telegram

Flow. Uses httpRequest, slack, linear. Scheduled trigger; 7 nodes.

HTTP Request, Slack, Linear
Slack & Telegram

TitanCrew — Daily Churn Prevention Scan. Uses httpRequest, slack. Scheduled trigger; 5 nodes.

HTTP Request, Slack