How to Send Copper Deal Stage Alerts to Slack with n8n

n8n Dashboard > Workflows > + New Workflow

Create a new n8n workflow

Log into your n8n instance (cloud at app.n8n.cloud or self-hosted). Click the '+ New Workflow' button in the top right of the Workflows dashboard. Give the workflow a name like 'Copper Deal Stage → Slack'. You'll land on a blank canvas with a default Start node — delete it, since you'll be using a Schedule trigger instead.

1. 1Click '+ New Workflow' in the top right
2. 2Type 'Copper Deal Stage → Slack' in the workflow name field at the top
3. 3Click the existing Start node on the canvas and press Delete

Canvas > + > Schedule Trigger > Interval

Add a Schedule trigger

Click the '+' button on the canvas to open the node picker. Search for 'Schedule Trigger' and select it. Set the interval to every 3 minutes — this is the polling frequency that checks Copper for changes. Every 1 minute is available but will hit Copper's API rate limit faster; every 5 minutes is safer for teams with high deal volume.

1. 1Click the '+' icon on the empty canvas
2. 2Type 'Schedule' in the search box
3. 3Select 'Schedule Trigger'
4. 4Set 'Trigger Interval' to 'Minutes'
5. 5Set the value to '3'

Copper Node > Credentials > Create New

Connect your Copper credentials

Click '+' after the Schedule Trigger to add a new node. Search for 'Copper' and select it. In the node configuration panel, click 'Credential for Copper API' and then 'Create New'. You'll need your Copper API key and the email address of your Copper account — both found in Copper under Settings > Integrations > API Keys. Paste them in and click Save.

1. 1Click '+' after the Schedule Trigger node
2. 2Search 'Copper' and select the Copper node
3. 3Click 'Credential for Copper API' dropdown
4. 4Click 'Create New Credential'
5. 5Paste your Copper API Key and account email
6. 6Click 'Save'

Copper Node > Resource > Opportunity > Get All > Filters

Configure Copper to list recently modified deals

In the Copper node, set Resource to 'Opportunity' and Operation to 'Get All'. Enable the 'Return All' toggle so you retrieve every result, not just the first page. Under Filters, add a filter for 'Updated At' greater than or equal to the current time minus 5 minutes — this scopes each poll to only recently changed deals. Without this filter, you'll return your entire pipeline on every execution.

1. 1Set Resource to 'Opportunity'
2. 2Set Operation to 'Get All'
3. 3Toggle 'Return All' to ON
4. 4Click 'Add Filter'
5. 5Set filter field to 'Updated At'
6. 6Set operator to 'is after'
7. 7Set value to '={{ new Date(Date.now() - 5 * 60 * 1000).toISOString() }}'

Canvas > + > Filter > Conditions

Filter to deals where stage actually changed

Copper returns all recently updated deals regardless of what changed — a note, a contact link, or an activity update will all appear here. You need to filter down to only deals where the pipeline stage changed. Add an n8n 'Filter' node after the Copper node. The problem: Copper's API doesn't return a 'previous stage' field, so you'll use a static data store to compare. For now, filter to deals where 'stage_id' is not null as a baseline — you'll add deduplication in the next step.

1. 1Click '+' after the Copper node
2. 2Search 'Filter' and select the Filter node
3. 3Click 'Add Condition'
4. 4Set the left value to '={{ $json.stage_id }}'
5. 5Set operator to 'is not empty'

Canvas > + > Remove Duplicates > Mode

Deduplicate with n8n's built-in deduplication node

Add a 'Remove Duplicates' node after the Filter node. Set the mode to 'Remove Items Seen in Previous Executions'. Set the deduplication key to a composite value: the deal ID combined with the stage ID, like '={{ $json.id }}-{{ $json.stage_id }}'. This ensures a notification only fires once per deal-per-stage combination. If a deal moves from Stage A → B → C, you'll get three separate notifications.

1. 1Click '+' after the Filter node
2. 2Search 'Remove Duplicates' and select it
3. 3Set Mode to 'Remove Items Seen in Previous Executions'
4. 4Set the Deduplication Key to '={{ $json.id }}-{{ $json.stage_id }}'

Canvas > + > HTTP Request

Look up pipeline stage name

Copper stores stage changes as a numeric stage_id, not a human-readable name. Add an HTTP Request node to fetch the pipeline stages from Copper's API. Call GET https://api.copper.com/developer_api/v1/pipelines and parse the response to find the stage name matching the deal's pipeline_id and stage_id. This lookup runs once per deal notification, so it adds one API call per triggered deal.

1. 1Click '+' after the Remove Duplicates node
2. 2Search 'HTTP Request' and select it
3. 3Set Method to 'GET'
4. 4Set URL to 'https://api.copper.com/developer_api/v1/pipelines'
5. 5Under Headers, add 'X-PW-AccessToken' with your Copper API key
6. 6Add header 'X-PW-UserEmail' with your Copper account email
7. 7Add header 'Content-Type' as 'application/json'

Canvas > + > Code

Extract and format the stage name with a Code node

Add a Code node after the HTTP Request to resolve the stage name from the pipeline response and build the Slack message payload. This is where n8n's code node earns its keep — you can do the lookup and message formatting in one step. Paste the JavaScript from the Pro Tip section below. The output will be a single object with all the fields your Slack message needs.

1. 1Click '+' after the HTTP Request node
2. 2Search 'Code' and select it
3. 3Set Language to 'JavaScript'
4. 4Paste the code from the Pro Tip section into the code editor
5. 5Click 'Test Step' to verify the stage name resolves correctly

Paste this into the Code node (Step 8) between the HTTP Request and Slack nodes. It resolves the stage name from the pipeline API response, formats the deal value, picks an emoji based on stage name, and builds the complete Slack message string — all in one pass.

// Inputs:
// - $input: the current deal item from Remove Duplicates
// - $node['HTTP Request'].json: the pipeline data from Copper

// Inputs:
// - $input: the current deal item from Remove Duplicates
// - $node['HTTP Request'].json: the pipeline data from Copper

const deal = $input.first().json;
const pipelines = $node['HTTP Request'].json;

// Find the correct pipeline, then the correct stage within it
const pipeline = Array.isArray(pipelines)
  ? pipelines.find(p => p.id === deal.pipeline_id)
  : null;

const stage = pipeline
  ? pipeline.stages.find(s => s.id === deal.stage_id)
  : null;

const stageName = stage ? stage.name : 'Unknown Stage';

// Emoji map — add your own stage names here
const stageEmoji = {
  'Won': '🏆',
  'Lost': '❌',
  'Negotiation': '🔴',
  'Proposal Sent': '🔵',
  'Qualified': '🟡',
  'Discovery': '🟢',
};
const emoji = stageEmoji[stageName] || '📋';

// Format monetary value
const rawValue = deal.monetary_value;
const dealValue = rawValue != null
  ? `$${Number(rawValue).toLocaleString('en-US')}`
  : 'No value set';

// Format close date (Copper returns Unix seconds)
const closeDate = deal.close_date
  ? new Date(deal.close_date * 1000).toLocaleDateString('en-US', {
      month: 'short', day: 'numeric', year: 'numeric'
    })
  : 'No close date';

// Build deep link back to Copper deal
const dealUrl = `https://app.copper.com/companies/app#/deals/${deal.id}`;

// Owner name: Copper returns assignee_id (numeric).
// For a real name, you'd need a second API call to /people/{id}.
// As a placeholder, we flag it clearly:
const ownerLabel = deal.assignee ? deal.assignee.name : `Rep ID ${deal.assignee_id}`;

// Build Slack message
const slackMessage = [
  `${emoji} *${deal.name}* moved to *${stageName}*`,
  `💰 ${dealValue} · 👤 ${ownerLabel} · 📅 Close: ${closeDate}`,
  `🔗 View in Copper: ${dealUrl}`
].join('\n');

return [{
  json: {
    dealId: deal.id,
    dealName: deal.name,
    stageName,
    dealValue,
    ownerLabel,
    closeDate,
    slackMessage,
    dealUrl
  }
}];

Canvas > + > Slack > Message > Send

Connect your Slack credentials and configure the message

Add a Slack node after the Code node. Set Resource to 'Message' and Operation to 'Send'. Click 'Credential for Slack API' and create a new credential using your Slack Bot Token (starts with xoxb-). Set the Channel field to your target channel name, like #pipeline-updates. Set the Message Text field to '={{ $json.slackMessage }}' to pull in the formatted message from the Code node.

1. 1Click '+' after the Code node
2. 2Search 'Slack' and select the Slack node
3. 3Set Resource to 'Message'
4. 4Set Operation to 'Send'
5. 5Click 'Credential for Slack API' and select or create your bot credential
6. 6Set Channel to '#pipeline-updates' (or your channel name)
7. 7Set Text to '={{ $json.slackMessage }}'

Workflow Settings > Error Workflow

Add error handling with an Error Trigger

Add a separate Error Trigger workflow to catch failures. In your main workflow, click the three-dot menu in the top right and select 'Settings'. Enable 'Error Workflow' and point it to a separate n8n workflow that sends a Slack DM to the workflow owner if something breaks. Without this, polling failures are silent — you won't know notifications stopped until someone asks why Slack went quiet.

1. 1Click the three-dot menu (⋮) in the top right of the workflow editor
2. 2Click 'Settings'
3. 3Toggle 'Error Workflow' to ON
4. 4Select an existing error-handler workflow or click 'Create New'
5. 5In the error workflow, add a Slack node that DMs the admin with '={{ $json.execution.error.message }}'

Workflow Editor > Active Toggle > Executions Tab

Activate and verify the workflow

Click the 'Inactive' toggle in the top right of the workflow editor to switch it to 'Active'. n8n will now run the Schedule Trigger every 3 minutes. To verify it's working, manually move a deal to a new stage in Copper, then wait up to 5 minutes and check your Slack channel. The notification should appear with the deal name, new stage, and owner. Check the Executions tab to see each run's output and confirm no errors.

1. 1Click the 'Inactive' toggle in the top right — it should turn green and read 'Active'
2. 2Open Copper and manually move a test deal to a different pipeline stage
3. 3Wait 3–5 minutes
4. 4Check your Slack channel for the notification
5. 5Click 'Executions' in the left sidebar to review run logs