How to Send Copper Lead Alerts to Slack with n8n

n8n Canvas > + Node > Webhook

Create the n8n workflow and add a Webhook node

Open n8n and click the orange '+ New Workflow' button in the top right. On the blank canvas, click the '+' node button and search for 'Webhook' in the node panel. Select the Webhook node — this is what Copper will POST to when a lead event fires. Set the HTTP Method to POST and note the generated webhook URL (it looks like https://your-n8n-host/webhook/xxxxxxxx). You'll paste this into Copper in the next step.

1. 1Click '+ New Workflow' in the top-right corner of the n8n dashboard
2. 2Click the large '+' button in the center of the blank canvas
3. 3Type 'Webhook' in the search box and select the Webhook node
4. 4Set 'HTTP Method' to POST in the node parameters panel
5. 5Copy the webhook URL from the 'Webhook URL' field — you'll need it in Step 2

Copper > Settings > Integrations > API > Webhooks > Add Webhook

Register the webhook in Copper

In Copper, go to Settings > Integrations > API and scroll to the Webhooks section. Click 'Add Webhook'. Paste your n8n webhook URL into the Endpoint URL field. Under 'Entity', select 'Lead'. Under 'Event', check both 'new' (lead created) and 'update' (lead updated — covers reassignment). Save the webhook. Copper does not natively filter update events by field, so n8n will handle the logic to check if the assignee changed.

1. 1Log into Copper and click the gear icon in the bottom-left sidebar
2. 2Select 'Integrations' then click 'API'
3. 3Scroll to the 'Webhooks' section and click 'Add Webhook'
4. 4Paste the n8n test webhook URL into 'Endpoint URL'
5. 5Set Entity to 'Lead', check 'new' and 'update', then click Save

n8n Canvas > Webhook Node > Listen for Test Event

Trigger a test lead event from Copper

Back in n8n, click the Webhook node and hit 'Listen for Test Event'. Then in Copper, open any existing lead and either create a new one or change its assignee. Copper will POST the lead payload to your webhook URL immediately. In n8n, the Webhook node will display the raw JSON it received. Look for the 'assignee_id' field — this is a numeric ID, not the rep's name. You'll resolve it to a readable name in a later step.

1. 1Click the Webhook node on the n8n canvas
2. 2Click 'Listen for Test Event' in the node panel on the right
3. 3Switch to Copper and create or reassign a lead
4. 4Return to n8n and confirm the payload appears in the node output panel

n8n Canvas > + Node > IF

Add an IF node to filter for assignee changes

Connect an IF node after the Webhook node. You need to confirm the lead was actually assigned or reassigned before sending any Slack message. Copper's update payload includes 'assignee_id' when the field was part of the change. Set the IF condition to check that the expression {{ $json.assignee_id }} is not empty. Leads with no assignee or events unrelated to assignment will exit the False branch and stop there — connect the False branch to a No Operation node to terminate cleanly.

1. 1Click the '+' connector from the Webhook node
2. 2Search for 'IF' and select the IF node
3. 3Set Value 1 to the expression {{ $json.assignee_id }}
4. 4Set Condition to 'Is Not Empty'
5. 5Connect the False output to a No Operation node

n8n Canvas > + Node > HTTP Request

Fetch the assigned rep's details from Copper API

The Copper webhook gives you assignee_id as a number (e.g., 482910), not a name or email. You need to resolve this to a real name before messaging anyone in Slack. Add an HTTP Request node after the IF True branch. Set the method to GET and the URL to https://api.copper.com/developer_api/v1/users/{{ $json.assignee_id }}. Add three headers: X-PW-AccessToken (your Copper API key), X-PW-Application set to developer_api, and X-PW-UserEmail set to the email of the Copper account the API key belongs to. This returns the rep's name and email.

1. 1Click '+' from the IF node's True output
2. 2Search for 'HTTP Request' and select it
3. 3Set Method to GET
4. 4Set URL to https://api.copper.com/developer_api/v1/users/{{ $json.assignee_id }}
5. 5Under Headers, add X-PW-AccessToken, X-PW-Application (developer_api), and X-PW-UserEmail

n8n Canvas > + Node > Code

Map the rep's email to their Slack member ID

Slack messages sent to a user must use their Slack Member ID (e.g., U04XYZABC), not their email address. Add a Code node after the HTTP Request node. Write a small lookup object that maps each rep's Copper email to their Slack Member ID — you can find Slack Member IDs by clicking a user's profile in Slack, then 'More' and 'Copy member ID'. This avoids a Slack API call on every run and keeps latency low. If the email isn't in your map, the code outputs a fallback channel like #sales-leads.

1. 1Click '+' from the HTTP Request node output
2. 2Search for 'Code' and select the Code node
3. 3Set language to JavaScript
4. 4Paste in the lookup map (see pro tip code below)
5. 5Save the node and run a test to confirm the Slack ID resolves correctly

n8n Canvas > + Node > Code

Build the Slack message with a Code node

Add another Code node to assemble the Slack Block Kit message. Block Kit lets you format the alert with bold fields, a direct link to the Copper record, and a clear call to action. Pull the lead name, company, phone, and the rep name from earlier nodes using n8n's $node syntax. The Copper record URL follows the pattern https://app.copper.com/companies/[your-workspace-id]/app#/leads/[lead-id] — find your workspace ID in Copper's URL when you're logged in. Output the full Slack blocks payload as a JSON object.

1. 1Click '+' from the Slack ID lookup Code node
2. 2Add another Code node
3. 3Build the blocks array with a header block and a section block listing lead fields
4. 4Include the Copper record deep link in a button block
5. 5Output the final object with { channel, blocks } ready for the Slack node

Paste this into two Code nodes: the first (Steps 6-7) resolves the Copper assignee_id to a Slack Member ID using a static lookup map and falls back to a #sales-leads channel if the rep isn't found; the second builds the full Slack Block Kit payload with the lead details and a direct Copper link. Place the first Code node immediately after the HTTP Request node, and the second Code node after the first.

// CODE NODE 1: Resolve Copper rep email to Slack Member ID
// Paste after the HTTP Request node (Step 6)
const repEmail = $node['HTTP Request'].json.email?.toLowerCase();

// CODE NODE 1: Resolve Copper rep email to Slack Member ID
// Paste after the HTTP Request node (Step 6)

const repEmail = $node['HTTP Request'].json.email?.toLowerCase();
const repName = $node['HTTP Request'].json.name || 'Unknown Rep';

// Maintain this map with your team's actual emails and Slack Member IDs
// Find Slack Member IDs: click profile > More > Copy member ID
const emailToSlackId = {
  '[email protected]': 'U04XYZABC',
  '[email protected]': 'U05DEFGHI',
  '[email protected]': 'U06JKLMNO',
  '[email protected]': 'U07PQRSTU',
};

const FALLBACK_CHANNEL = 'C08SALESLEADS'; // #sales-leads channel ID

const slackUserId = emailToSlackId[repEmail] || FALLBACK_CHANNEL;
const isFallback = slackUserId === FALLBACK_CHANNEL;

return [{
  json: {
    slackUserId,
    repName,
    repEmail,
    isFallback,
  }
}];

// -----------------------------------------------
// CODE NODE 2: Build Slack Block Kit message payload
// Paste after Code Node 1 (Step 7)
// -----------------------------------------------

const lead = $node['Webhook'].json;
const { slackUserId, repName, isFallback } = $node['Code'].json;

// Replace 12345 with your actual Copper workspace ID (found in the Copper URL)
const COPPER_WORKSPACE_ID = '12345';
const copperUrl = `https://app.copper.com/companies/${COPPER_WORKSPACE_ID}/app#/leads/${lead.id}`;

const phone = lead.phone_numbers?.[0]?.number || 'No phone on file';
const email = lead.email?.[0]?.email || 'No email on file';
const company = lead.company_name || 'No company listed';
const status = lead.status || 'Unknown';

// Truncate long values to avoid Slack's 3000-char block limit
const truncate = (str, max = 200) => str.length > max ? str.slice(0, max) + '…' : str;

const headerText = isFallback
  ? `⚠️ Unrouted Lead — no Slack ID found for ${repName}`
  : `🎯 New Lead Assigned to You, ${repName}`;

const blocks = [
  {
    type: 'header',
    text: { type: 'plain_text', text: headerText, emoji: true }
  },
  {
    type: 'section',
    fields: [
      { type: 'mrkdwn', text: `*Lead:*\n${truncate(lead.name)}` },
      { type: 'mrkdwn', text: `*Company:*\n${truncate(company)}` },
      { type: 'mrkdwn', text: `*Phone:*\n${phone}` },
      { type: 'mrkdwn', text: `*Email:*\n${email}` },
      { type: 'mrkdwn', text: `*Status:*\n${status}` },
    ]
  },
  {
    type: 'actions',
    elements: [
      {
        type: 'button',
        text: { type: 'plain_text', text: 'View in Copper', emoji: true },
        url: copperUrl,
        action_id: 'view_copper_lead'
      }
    ]
  },
  {
    type: 'context',
    elements: [
      { type: 'mrkdwn', text: `Lead ID: ${lead.id} • Assigned at <!date^${Math.floor(Date.now()/1000)}^{time} on {date_short}|just now>` }
    ]
  }
];

return [{
  json: {
    channel: slackUserId,
    blocks,
  }
}];

n8n Canvas > + Node > Slack > Message > Send

Add the Slack node and send the message

Add a Slack node after the message-builder Code node. Set the Resource to 'Message' and Operation to 'Send'. In the Channel field, use the expression {{ $json.channel }} to pull from your Code node output — this will be the rep's Slack Member ID for a DM, or a channel ID for a group alert. In the Message field, set it to use Block Kit by selecting 'Blocks' and using the expression {{ JSON.stringify($json.blocks) }}. Authenticate by connecting your Slack OAuth app credentials.

1. 1Click '+' from the message-builder Code node
2. 2Search for 'Slack' and select the Slack node
3. 3Set Resource to 'Message' and Operation to 'Send'
4. 4Set Channel to {{ $json.channel }}
5. 5Set Blocks to {{ JSON.stringify($json.blocks) }} and connect your Slack credentials

n8n Canvas > Workflow Settings > Error Workflow

Add error handling with a Slack fallback alert

Connect an Error Trigger node that sends a Slack message to an admin channel (like #n8n-alerts) if any step fails — particularly the Copper API lookup or the Slack send itself. In n8n, click the three-dot menu on the workflow canvas and toggle on 'Error Workflow', then point it to a separate error-handling workflow or add error outputs directly. At minimum, log the lead ID and the error message so you can replay the event manually if a rep misses a hot lead because of an API failure.

1. 1Click the three-dot menu in the top-right of the canvas and select 'Settings'
2. 2Enable 'Error Workflow' and point it to an existing error handler, or create a new one
3. 3In the error workflow, add a Slack node that messages #n8n-alerts
4. 4Include {{ $json.error.message }} and {{ $json.execution.id }} in the alert text
5. 5Save both workflows

Copper > Settings > Integrations > API > Webhooks | n8n Canvas > Activate Toggle

Switch the webhook to the production URL and activate

Go back to the Webhook node in n8n and copy the Production webhook URL (it's listed just below the test URL in the node panel). Return to Copper Settings > Integrations > API > Webhooks and edit the webhook you created in Step 2. Replace the test URL with the production URL. Then in n8n, click the toggle in the top-right corner of the canvas to activate the workflow. The toggle turns green when active.

1. 1Click the Webhook node in n8n and copy the Production URL
2. 2Go to Copper > Settings > Integrations > API > Webhooks
3. 3Click Edit on your existing webhook and replace the URL with the production one
4. 4Save in Copper
5. 5Click the Activate toggle in n8n's top-right — it turns green when live