AutomationFlowsSlack & Telegram › Champion Job Change → Salesforce Task

Champion Job Change → Salesforce Task

Champion job change → Salesforce task. Uses httpRequest, salesforce, slack. Webhook trigger; 4 nodes.

Webhook trigger★★☆☆☆ complexity4 nodesHTTP RequestSalesforceSlack
Slack & Telegram Trigger: Webhook Nodes: 4 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": "Champion job change \u2192 Salesforce task",
  "nodes": [
    {
      "parameters": {
        "httpMethod": "POST",
        "path": "champion-change",
        "responseMode": "lastNode",
        "options": {}
      },
      "id": "webhook",
      "name": "LinkedIn change webhook",
      "type": "n8n-nodes-base.webhook",
      "typeVersion": 1,
      "position": [
        240,
        320
      ]
    },
    {
      "parameters": {
        "url": "=https://api.apollo.io/v1/organizations/enrich?domain={{$json[\"company_domain\"]}}",
        "sendHeaders": true,
        "headerParameters": {
          "parameters": [
            {
              "name": "X-Api-Key",
              "value": "={{$env.APOLLO_API_KEY}}"
            }
          ]
        }
      },
      "id": "apollo-org",
      "name": "Apollo org enrich",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.1,
      "position": [
        460,
        320
      ]
    },
    {
      "parameters": {
        "resource": "task",
        "operation": "create",
        "additionalFields": {
          "Subject": "=Champion change \u2014 {{$json[\"contact_name\"]}} \u2192 {{$json[\"new_title\"]}} @ {{$json[\"new_company\"]}}",
          "ActivityDate": "={{$now.plus({days: 1}).toFormat('yyyy-MM-dd')}}",
          "Priority": "High",
          "Description": "=The original champion on this closed-lost deal just changed roles. Run automations/09-closed-lost-revival/monitor.py with this trigger and review the draft before sending. Source: LinkedIn change webhook."
        }
      },
      "id": "sf-task",
      "name": "Salesforce task",
      "type": "n8n-nodes-base.salesforce",
      "typeVersion": 1,
      "position": [
        680,
        320
      ],
      "credentials": {
        "salesforceOAuth2Api": {
          "name": "<your credential>"
        }
      }
    },
    {
      "parameters": {
        "channel": "#deal-alerts",
        "text": "=Champion change detected \u2014 *{{$json[\"contact_name\"]}}* now at *{{$json[\"new_company\"]}}*. Task created on closed-lost deal. <@AE_handle>"
      },
      "id": "slack",
      "name": "Slack alert",
      "type": "n8n-nodes-base.slack",
      "typeVersion": 2,
      "position": [
        900,
        320
      ],
      "credentials": {
        "slackApi": {
          "name": "<your credential>"
        }
      }
    }
  ],
  "connections": {
    "LinkedIn change webhook": {
      "main": [
        [
          {
            "node": "Apollo org enrich",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Apollo org enrich": {
      "main": [
        [
          {
            "node": "Salesforce task",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Salesforce task": {
      "main": [
        [
          {
            "node": "Slack alert",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "versionId": "champion-change-v1",
  "tags": [
    "closed-lost",
    "champion",
    "salesforce"
  ]
}

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

Champion job change → Salesforce task. Uses httpRequest, salesforce, slack. Webhook trigger; 4 nodes.

Source: https://github.com/elikem2021/gtm-engineering/blob/main/n8n/champion-job-change.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

Non-Tech Team Onboarding - AI Tool Setup Automation. Uses httpRequest, slack, emailSend. Webhook trigger; 4 nodes.

HTTP Request, Slack, Email Send
Slack & Telegram

HR teams, IT Operations, and System Administrators managing employee onboarding at scale. It’s perfect if you use Odoo 18 to trigger account requests and need Redmine + GitLab accounts created instant

HTTP Request, Slack
Slack & Telegram

This workflow is a complete, production-ready solution for recovering abandoned carts in Shopify stores using a multi-channel, multi-touch approach. It automates personalized follow-ups via Email, SMS

HTTP Request, Shopify, SendGrid +5
Slack & Telegram

This workflow automates end-to-end research analysis by coordinating multiple AI models—including NVIDIA NIM (Llama), OpenAI GPT-4, and Claude to analyze uploaded documents, extract insights, and gene

HTTP Request, Postgres, Slack +1
Slack & Telegram

Are you tired of the repetitive dance between git push, creating a pull request in GitHub, updating the corresponding task in JIRA, and then manually notifying your team in Slack, or Notion?

HTTP Request, Stop And Error, Jira +2