Send New Company Signals From Bounce Watch to Email

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 →

{
  "name": "Send new company signals from Bounce Watch to email",
  "nodes": [
    {
      "parameters": {
        "content": "## Send new company signals from Bounce Watch to email\n\nBounce Watch tells you what just happened at a company and when \u2014 funding, senior hires, new offices, customer wins and partnerships, each carrying the date it happened. What the API covers: bouncewatch.com/products/data-enrichment-api\n\nThis template watches the companies on your Bounce Watch watchlist and emails you the moment one of them moves.\n\n### How it works\n\nThe Bounce Watch trigger checks your watchlist and hands over each new signal once. A filter drops anything marked unconfirmed, so rumours and inferences never reach you. What is left carries the company, what happened, the date it happened and a link to the company page.\n\n### Setup\n\n1. Get an API key at bouncewatch.com/register/api. It is free, no card, and every new account starts with 2,500 credits.\n2. Paste it into the Bounce Watch credential on the trigger node.\n3. Put a few companies on your watchlist first. Use the Bounce Watch node's Watch \u2192 Add operation, or add them from your Bounce Watch account. An empty watchlist means an empty trigger.\n4. Set the from and to addresses on the email node, and pick your SMTP credential.\n\nChecking the watchlist costs no credits. An empty run means nothing matched your watches, not that those companies were quiet.\n\n### Customization tips\n\nRaise the importance threshold on the trigger to hear only about the big moments. Point the trigger at a single company if you only care about one. Or swap email for Slack, a task in your tracker, or a row in a sheet.",
        "height": 960,
        "width": 520
      },
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        -380,
        -120
      ],
      "id": "sticky-overview",
      "name": "Sticky Note"
    },
    {
      "parameters": {
        "minWeight": 3,
        "limit": 25
      },
      "id": "b1a7c0de-0001-4000-8000-000000000001",
      "name": "New signal at a watched company",
      "type": "n8n-nodes-bouncewatch.bounceWatchTrigger",
      "typeVersion": 1,
      "position": [
        -220,
        0
      ],
      "credentials": {
        "bounceWatchApi": {
          "name": "<your credential>"
        }
      },
      "notes": "Polls the companies this API key watches. The first poll records what is already there without firing \u2014 history is not news."
    },
    {
      "parameters": {
        "conditions": {
          "options": {
            "caseSensitive": true,
            "version": 2
          },
          "conditions": [
            {
              "id": "c0000000-0000-4000-8000-000000000001",
              "operator": {
                "type": "boolean",
                "operation": "false",
                "singleValue": true
              },
              "leftValue": "={{ $json.unconfirmed }}",
              "rightValue": ""
            }
          ],
          "combinator": "and"
        },
        "options": {}
      },
      "id": "b1a7c0de-0002-4000-8000-000000000002",
      "name": "Drop unconfirmed",
      "type": "n8n-nodes-base.filter",
      "typeVersion": 2,
      "position": [
        40,
        0
      ],
      "notes": "Some signals are inference rather than announcement. They carry `unconfirmed`, and a channel post reads as fact \u2014 so they stop here."
    },
    {
      "parameters": {
        "fromEmail": "",
        "toEmail": "",
        "subject": "={{ $json.company.name }} \u2014 {{ $json.label }}",
        "emailFormat": "text",
        "text": "={{ $json.summary }}\n\n{{ $json.company.name }} \u00b7 {{ $json.company.country }}{{ $json.company.employees ? \" \u00b7 \" + $json.company.employees + \" people\" : \"\" }}{{ $json.company.funding_stage ? \" \u00b7 \" + $json.company.funding_stage : \"\" }}\n{{ $json.label }}\n{{ $json.date }}{{ $json.date_is_measurement ? \" (the date we picked it up, not necessarily when it happened)\" : \"\" }}\n\n{{ $json.company.profile_url }}",
        "options": {}
      },
      "id": "b1a7c0de-0003-4000-8000-000000000003",
      "name": "Send the email",
      "type": "n8n-nodes-base.emailSend",
      "typeVersion": 2.1,
      "position": [
        300,
        0
      ],
      "notes": "Fill in From and To, and pick your SMTP credential."
    }
  ],
  "connections": {
    "New signal at a watched company": {
      "main": [
        [
          {
            "node": "Drop unconfirmed",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Drop unconfirmed": {
      "main": [
        [
          {
            "node": "Send the email",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "settings": {
    "executionOrder": "v1"
  },
  "meta": {
    "templateCredsSetupCompleted": false
  }
}

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.

• bounceWatchApi

About this workflow

Send new company signals from Bounce Watch to email. Uses n8n-nodes-bouncewatch, emailSend. Event-driven trigger; 4 nodes.

Source: https://github.com/bouncewatch/n8n-nodes-bouncewatch/blob/main/templates/new-signal-to-email.json — original creator credit. Request a take-down →

More General workflows → · Browse all categories →

Related workflows

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