How to Sync Slack Members to Copper with Power Automate

make.powerautomate.com > + Create > Automated cloud flow

Create a new Automated cloud flow

Go to make.powerautomate.com and sign in with your Microsoft 365 account. Click '+ Create' in the left sidebar, then select 'Automated cloud flow' from the options on screen. Give the flow a name like 'Slack Channel Member → Copper Contact'. You will be prompted to choose a trigger before the canvas opens.

1. 1Click '+ Create' in the left sidebar
2. 2Select 'Automated cloud flow'
3. 3Enter flow name: 'Slack Channel Member → Copper Contact'
4. 4Click 'Skip' on the trigger picker — you will add it manually on canvas

Flow Canvas > Trigger Block > Search: Slack > When a new member joins a channel

Add the Slack 'When a new member joins a channel' trigger

Click the empty trigger block on the canvas. The connector search panel opens on the right side. Type 'Slack' in the search bar and select the Slack connector. Scroll through the trigger list until you see 'When a new member joins a channel' — click it. Power Automate will immediately ask you to create or select a Slack Connection.

1. 1Click the trigger block on the canvas
2. 2Type 'Slack' in the connector search bar
3. 3Select the 'Slack' connector
4. 4Click 'When a new member joins a channel' from the trigger list

Trigger Card > Connection > Sign in > Slack OAuth popup

Connect your Slack workspace

Click 'Sign in' in the Connection field at the top of the trigger card. A browser popup opens asking you to authorize Power Automate in your Slack workspace. Sign in with the Slack account that has access to the target channels. After authorization, the popup closes and the Connection field shows your workspace name.

1. 1Click 'Sign in' in the Connection field
2. 2Log into Slack in the popup window
3. 3Click 'Allow' to grant Power Automate access
4. 4Confirm the popup closes and your workspace name appears in the Connection field

Trigger Card > Channel Name dropdown

Select the target Slack channel

Click the 'Channel Name' dropdown in the trigger card. The list shows every public and private channel your authenticated Slack user belongs to. Select the specific channel you want to monitor — for example, #client-partners. If the channel is private and does not appear, the authorized user needs to be added to that channel first.

1. 1Click the 'Channel Name' dropdown
2. 2Scroll or type to find your target channel
3. 3Select the channel (e.g., #client-partners)
4. 4Confirm the channel name populates in the field

Flow Canvas > + New step > Search: Slack > Get user profile

Add a 'Get user profile' Slack action

Click '+ New step' below the trigger. Search for 'Slack' again and this time select the 'Get user profile' action. The trigger only passes a User ID — not a name or email. This action takes that User ID and returns the full profile including display name, real name, email, and title. Map the 'User ID' field using the dynamic content picker: select 'User' from the trigger's output tokens.

1. 1Click '+ New step'
2. 2Search for 'Slack' in the action picker
3. 3Select 'Get user profile'
4. 4Click the 'User ID' field
5. 5Select 'User' from the dynamic content panel (this is the member ID from the trigger)

Flow Canvas > + New step > Control > Condition

Add a Condition to filter out bots and guest accounts

Click '+ New step' and add a 'Condition' control action. Set the left side to 'Is Bot' from the 'Get user profile' dynamic outputs. Set the operator to 'is equal to' and the right side to 'false'. This prevents bot accounts (like Zapier bots or GitHub notification bots) from being created as contacts in Copper. In the 'No' branch, all subsequent steps will run; leave the 'Yes' branch empty.

1. 1Click '+ New step'
2. 2Select 'Control' from the connector list
3. 3Click 'Condition'
4. 4Set left field to 'Is Bot' from dynamic content
5. 5Set operator to 'is equal to'
6. 6Set right field value to 'false'
7. 7Place all remaining steps inside the 'No' (If false) branch

If No Branch > + Add an action > HTTP

Add an HTTP action to check for duplicate contacts in Copper

Inside the 'If no' branch, click '+ Add an action' and search for 'HTTP'. Select the built-in 'HTTP' action. Copper does not have a native Power Automate connector, so you will call Copper's REST API directly. Set Method to POST, URI to 'https://api.copper.com/developer_api/v1/people/search', and add the required headers and a JSON body to search by email before creating a new contact. This prevents duplicates.

1. 1Click '+ Add an action' inside the 'If no' branch
2. 2Search for 'HTTP' and select the HTTP action
3. 3Set Method to 'POST'
4. 4Set URI to 'https://api.copper.com/developer_api/v1/people/search'
5. 5Add Header: 'X-PW-AccessToken' = your Copper API key
6. 6Add Header: 'X-PW-Application' = 'developer_api'
7. 7Add Header: 'X-PW-UserEmail' = your Copper account email
8. 8Add Header: 'Content-Type' = 'application/json'
9. 9Set Body to: {"emails": [{"email": "<Profile Email from dynamic content>"}]}

If No Branch > + Add an action > Control > Condition

Add a second Condition to skip if contact already exists

Add another 'Condition' control action directly after the HTTP search step. Use the expression editor to check if the HTTP response body is an empty array. Set the left field expression to: 'length(body('HTTP'))' and the operator to 'is equal to' and the value to 0. In the 'If yes' branch (length is 0, meaning no existing contact), place the Copper create action. Leave the 'If no' branch empty.

1. 1Click '+ Add an action' after the HTTP step
2. 2Select 'Control' > 'Condition'
3. 3Click the left field and switch to 'Expression' tab
4. 4Enter: length(body('HTTP'))
5. 5Set operator to 'is equal to'
6. 6Set right value to 0
7. 7Place the Copper HTTP create action in the 'If yes' branch

If Yes Branch > + Add an action > HTTP

Add an HTTP action to create the Copper contact

Inside the second condition's 'If yes' branch, add another HTTP action. This one POSTs to Copper's people endpoint to create the contact. Set Method to POST and URI to 'https://api.copper.com/developer_api/v1/people'. Use the same three headers from Step 7. Build the JSON body using dynamic content from the 'Get user profile' action, mapping real_name to name and profile_email to the emails array.

1. 1Click '+ Add an action' inside the 'If yes' branch
2. 2Select HTTP action
3. 3Set Method to 'POST'
4. 4Set URI to 'https://api.copper.com/developer_api/v1/people'
5. 5Add the same three headers as Step 7
6. 6Set Body using the template in the pro tip section below

HTTP Create Action > ... > Configure run after > + Add action > Data Operation > Compose

Add error handling with a Compose action for logging

After the create HTTP action, add a 'Configure run after' setting by clicking the three dots on the action. Enable it to run on 'has failed' as well as 'is successful'. Then add a 'Compose' action that captures the HTTP status code and body for logging purposes. This gives you a visible record when a Copper API call fails without stopping the flow entirely.

1. 1Click the '...' menu on the Copper create HTTP action
2. 2Select 'Configure run after'
3. 3Check both 'is successful' and 'has failed'
4. 4Click '+ Add an action' after the HTTP create step
5. 5Search for 'Compose' under Data Operations
6. 6Set Inputs to: {"status": "@{outputs('HTTP_2')['statusCode']}", "body": "@{body('HTTP_2')}"}

make.powerautomate.com > My flows > [Flow Name] > Run history

Test the flow end-to-end

Save the flow by clicking 'Save' in the top right. Then open Slack and add a test user (a real person, not a bot) to your monitored channel. Return to the flow's run history page in Power Automate — refresh after 60-90 seconds. You should see a new run appear. Click into it to inspect each action's inputs and outputs. Verify the Copper contact was created by checking Copper's People list.

1. 1Click 'Save' in the top right of the canvas
2. 2Open Slack and add a test user to the monitored channel
3. 3Wait 60-90 seconds
4. 4Return to make.powerautomate.com > My flows > select your flow
5. 5Click 'Run history' and refresh
6. 6Click the latest run to inspect each step's output
7. 7Open Copper > People to confirm the new contact appears

Paste this into the 'Body' field of the Copper create HTTP action (Step 9). It uses Power Automate expressions to build the full Copper API payload, handle null values gracefully, and stamp the source tag. Switch to 'Expression' mode in the Body field, or paste into a Compose action first and reference that output.

{
  "name": "@{body('Get_user_profile')?['real_name']}",
  "emails": [

{
  "name": "@{body('Get_user_profile')?['real_name']}",
  "emails": [
    {
      "email": "@{body('Get_user_profile')?['profile']?['email']}",
      "category": "work"
    }
  ],
  "title": "@{if(empty(body('Get_user_profile')?['profile']?['title']), null, body('Get_user_profile')?['profile']?['title'])}",
  "phone_numbers": [
    {
      "number": "@{body('Get_user_profile')?['profile']?['phone']}",
      "category": "work"
    }
  ],
  "tags": [
    "Slack-Onboarded",
    "@{triggerBody()?['channel']}"
  ],
  "custom_fields": [
    {
      "custom_field_definition_id": 123456,
      "value": "@{body('Get_user_profile')?['id']}"
    }
  ]
}