How to Log Slack Messages to Copper CRM with Make

make.com > Scenarios > Create a new scenario

Create a new scenario in Make

Log into make.com and click the blue 'Create a new scenario' button in the top-right of your dashboard. You will land on the visual scenario builder — a blank canvas with a large plus icon in the center. This is where you add your first module. Give the scenario a name right away by clicking the default title at the top; name it something like 'Slack → Copper: Log Customer Messages' so it's immediately identifiable in your scenario list.

1. 1Click 'Create a new scenario' in the top-right
2. 2Click the large plus icon on the canvas to open the app picker
3. 3Type 'Slack' in the search bar
4. 4Select 'Slack' from the results

Scenario Canvas > Slack Module > Watch Messages

Configure the Slack trigger: Watch Messages

From the Slack module list, select 'Watch Messages' as your trigger — this fires instantly when a new message is posted in a channel you specify. You will be prompted to connect your Slack workspace if you haven't already; click 'Add' and follow the OAuth flow. Once connected, set the Channel field to the specific customer-facing channel you want to monitor, such as #customer-acme or a channel group pattern. Set the trigger to watch 'New Messages' only, not thread replies, unless you want replies logged too.

1. 1Select 'Watch Messages' from the Slack trigger list
2. 2Click 'Add' next to the Connection field to authenticate with Slack
3. 3Authorize Make in the Slack OAuth popup
4. 4Set the Channel dropdown to your target customer channel
5. 5Set 'Message type' to 'Messages' (not replies) unless you need both

📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}

Scenario Canvas > Add Module > Slack > Get User Info

Add a Text Parser to extract contact email

Most Slack messages won't contain the customer email directly, but Slack user profiles often do. Add a 'Tools > Get a Variable' module or, more practically, add the Slack 'Get User Info' module to resolve the message sender's Slack user ID into a real name and email address. Connect it immediately after the trigger. Map the 'User' field from the Watch Messages output (it returns a user ID like U04XKPL2B) into the 'User ID' field of Get User Info. This email is what you will use to look up the matching Copper contact in the next step.

1. 1Click the right edge of the Slack trigger module to add a new module
2. 2Search for 'Slack' and select it
3. 3Choose 'Get User Info' from the action list
4. 4Map the 'User' output from the Watch Messages trigger into the 'User ID' field
5. 5Save the module

Scenario Canvas > Add Module > Copper > Search Contacts

Search Copper for the matching contact

Add a Copper module and choose 'Search Contacts'. Connect your Copper account via OAuth — Make uses Copper's v1 REST API, and you will need your Copper API key plus the email address associated with your Copper account for authentication. In the search filter, map the email from the Slack Get User Info output (profile.email) into the Email search field. This locates the Copper contact record that matches the person who sent the Slack message. If no match is found, you can route the scenario differently using a Router in the next step.

1. 1Click the plus icon after the Get User Info module
2. 2Search for 'Copper' and select it
3. 3Choose 'Search Contacts' from the action list
4. 4Click 'Add' to connect Copper — enter your Copper API key and account email
5. 5Map 'profile.email' from the Slack module into the Email filter field

Scenario Canvas > Connection Line > Add Router

Add a Router to handle missing contacts

Not every Slack user will have a matching Copper contact — internal team members, bots, and new prospects won't be found. Add a Router module after the Search Contacts step. This splits your scenario into two paths: one for when a contact is found, one for when it isn't. The Router in Make is added by clicking the small wrench icon on the connection line between modules and selecting 'Add a router'. You will set conditions on each path in the next step.

1. 1Right-click the connection line after the Copper Search Contacts module
2. 2Select 'Add a router' from the context menu
3. 3Two output paths appear from the Router node
4. 4Label Path 1 'Contact Found' and Path 2 'No Contact — Skip'

Scenario Canvas > Router > Filter Icon

Set filter conditions on each Router path

Click the filter icon on Path 1 and set the condition: the Copper Search Contacts result ID field 'Exists' (is not empty). This means a contact was found. On Path 2, set the opposite condition: ID 'Does not exist'. For Path 2, you can simply add a Slack module to post a message to a private admin channel like #crm-alerts saying a Slack message had no matching Copper contact — giving your team a chance to create the contact manually. This prevents silent data loss.

1. 1Click the filter icon on the first Router path
2. 2Set Field to the Copper contact ID output token
3. 3Set Condition to 'Exists'
4. 4Click the filter icon on the second path
5. 5Set the same field with condition 'Does not exist'

Scenario Canvas > Router Path 1 > Copper > Create Activity

Add Copper 'Create Activity' on the matched-contact path

On Path 1, add a Copper module and select 'Create Activity'. This is where the Slack message gets written to the contact's timeline in Copper. Set the 'Parent Type' to 'contact' and map the Copper contact ID from the Search Contacts output into the 'Parent ID' field. Set the Activity Type to 'Note' — Copper supports custom activity types too, but Note is universally available. In the Details field, you will build a formatted string combining the Slack message text, sender name, channel name, and timestamp.

1. 1Click the plus icon on Path 1 of the Router
2. 2Search for and select 'Copper'
3. 3Choose 'Create Activity'
4. 4Set 'Parent Type' to 'contact'
5. 5Map the Copper contact ID into 'Parent ID'
6. 6Set 'Activity Type' to 'Note'

Scenario Canvas > Copper Create Activity > Details Field

Build the activity detail field with formatted message content

Click into the 'Details' field of the Create Activity module. Use Make's text editor to compose the note body. Type a label, then insert dynamic tokens from the previous modules. A good format is: '[Slack] #channel-name | Sender: display_name | Date: timestamp\n\n message_text'. Use Make's built-in formatDate() function to convert the Slack Unix timestamp (it comes as seconds since epoch) into a readable format. The formatDate() call wraps the timestamp token like this: formatDate(timestamp * 1000; "YYYY-MM-DD HH:mm"). Without the * 1000, Make misreads the Unix timestamp as milliseconds.

1. 1Click into the Details field in the Copper Create Activity module
2. 2Type '[Slack] #' then click the token picker and select the Slack channel name
3. 3Add ' | Sender: ' then map the Slack user display name
4. 4Add ' | Date: ' then insert formatDate(ts * 1000; "YYYY-MM-DD HH:mm")
5. 5Press Enter twice, then map the Slack message text field

📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}

Scenario Canvas > Copper Create Activity > All Fields

Map remaining activity fields

Still in the Create Activity module, fill in the optional but useful fields. Set 'Activity Date' to the formatted date from the previous step — Copper uses ISO 8601 format (YYYY-MM-DD) for this field, separate from the note details text. If your Copper account has custom activity categories, match the closest one. Leave 'User ID' blank unless you want to attribute the activity to a specific Copper user rather than the API key owner. Check that the 'Parent ID' correctly references the Copper contact ID, not the person ID from Slack.

1. 1Set 'Activity Date' to formatDate(ts * 1000; "YYYY-MM-DD")
2. 2Leave 'User ID' blank unless attributing to a specific rep
3. 3Confirm 'Parent Type' is 'contact' not 'lead' or 'opportunity'
4. 4Save the module

Scenario Canvas > Run Once (bottom toolbar)

Activate the scenario and test with a real message

Click 'Run once' in the bottom-left of the scenario builder to fire a test. Go to your Slack workspace and post a test message in the target channel from an account that has a matching Copper contact. Return to Make and watch the execution flow animate across the modules — green checkmarks mean data passed through, orange badges show the record count per module. Click any module to inspect the exact data it received and output. Confirm the Copper contact now shows the new activity in its timeline.

1. 1Click 'Run once' in the bottom-left toolbar
2. 2Post a test Slack message in the target channel
3. 3Watch the execution animation in Make
4. 4Click the Copper Create Activity module bubble to inspect the output
5. 5Open Copper and find the contact — check the Activity tab for the new note

📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}

Scenario Canvas > Toggle (bottom-left) > Scenario Settings

Schedule and activate the scenario

Once the test passes, click the toggle in the bottom-left of the scenario builder to switch from 'Off' to 'On'. Because this uses Slack's event-based trigger via Make's webhook infrastructure, the scenario fires within seconds of each new Slack message — you do not need to set a polling interval. Set the maximum number of cycles per execution to 1 (the default) since each Slack message fires its own trigger. In the scenario settings, enable 'Auto-commit' so partial runs don't leave incomplete data in Copper.

1. 1Click the toggle at the bottom-left to set the scenario to 'On'
2. 2Click the clock icon to open scheduling settings
3. 3Confirm the scenario is set to respond to webhooks, not a timed interval
4. 4Open Scenario Settings and enable 'Auto-commit'
5. 5Save settings

This formula goes in the Details field of the Copper Create Activity module. It conditionally appends a '[URGENT]' tag to the note if the Slack message contains certain keywords, so your team can filter high-priority interactions in Copper's activity feed.

if(
  or(
    contains(lower(text); "urgent"),

if(
  or(
    contains(lower(text); "urgent"),
    contains(lower(text); "escalate"),
    contains(lower(text); "cancel"),
    contains(lower(text); "refund")
  );
  "[URGENT] [Slack] #" + channel_name + " | Sender: " + profile.display_name + " | Date: " + formatDate(ts * 1000; "YYYY-MM-DD HH:mm") + "\n\n" + text;
  "[Slack] #" + channel_name + " | Sender: " + profile.display_name + " | Date: " + formatDate(ts * 1000; "YYYY-MM-DD HH:mm") + "\n\n" + text
)