How to Send Close Lead Assignments to Slack with Make

make.com > Scenarios > Create a new scenario

Create a new Make scenario

Log into Make at make.com and click the blue 'Create a new scenario' button in the top right of the Scenarios dashboard. You'll land on the visual canvas with a single empty module in the center. This is where you'll set the trigger. Name the scenario immediately — click the default name at the top ('New scenario') and type something like 'Close Lead Assignment → Slack'.

1. 1Click 'Create a new scenario' in the top right
2. 2Click the empty circle module on the canvas
3. 3Type 'Close' in the app search bar
4. 4Select 'Close' from the results
5. 5Choose 'Watch Events (Instant)' as the trigger

Close > Settings > API Keys | Make > Close module > Connection > Add

Connect your Close account

In the Close module config panel, click 'Add' next to the Connection field. A dialog will ask for your Close API key. Go to Close at app.close.com, open your profile menu in the bottom left, click 'Settings', then 'API Keys', and generate a new key labeled 'Make Integration'. Paste that key into Make and click Save.

1. 1In the Close module panel, click 'Add' next to Connection
2. 2Open Close in a new tab: app.close.com > Settings > API Keys
3. 3Click 'Generate API Key' and label it 'Make Integration'
4. 4Copy the key immediately — Close only shows it once
5. 5Paste the key into Make's connection dialog and click Save

Make > Close module > Event Type > Lead > Action > updated

Configure the lead assignment event trigger

With the connection set, you now configure which Close event fires the scenario. In the Event Type dropdown, select 'Lead'. In the Object Type dropdown, select 'lead'. In the Action dropdown, select 'updated'. This catches any lead update — you'll filter specifically for assignment changes in the next step. Click OK to save the module.

1. 1Set Event Type to 'Lead'
2. 2Set Object Type to 'lead'
3. 3Set Action to 'updated'
4. 4Leave Webhook Name blank — Make auto-generates it
5. 5Click OK

Close > Settings > Integrations > API > Webhooks > Add Webhook

Register the webhook in Close

Make auto-generated a webhook URL when you saved the trigger. You now need to register it in Close so Close knows to send events to Make. Back in Make, click the Close module and look for the generated webhook URL — it appears in a blue info box at the bottom of the config panel. Copy it. In Close, go to Settings > Integrations > API and find the Webhooks section. Click 'Add Webhook', paste the URL, and select 'lead.updated' as the event type.

1. 1In Make, click the Close module and copy the webhook URL from the blue info box
2. 2In Close, go to Settings > Integrations > API
3. 3Scroll to Webhooks and click 'Add Webhook'
4. 4Paste the Make webhook URL into the URL field
5. 5Select 'lead.updated' from the event type list and click Save

Make > Canvas > Arrow between modules > Filter (wrench icon)

Add a filter for owner assignment changes

Click the small wrench icon on the arrow between the Close module and the next empty module slot. This opens the Filter dialog. You need to filter so the scenario only continues when the assigned_to field actually changed. Set Condition A: Field = 'changed_fields', Operator = 'Contains', Value = 'assigned_to'. This tells Make to only proceed when Close explicitly flags the owner field as modified.

1. 1Click the small wrench icon on the connector arrow after the Close module
2. 2Click 'Add AND condition'
3. 3In Field, type or select 'changed_fields'
4. 4Set Operator to 'Contains'
5. 5Set Value to 'assigned_to'
6. 6Click OK

Make > Canvas > + > Close > Get a Lead

Fetch full lead details from Close

The webhook payload from Close gives you the lead ID and changed fields but not all the rich data you need for the Slack message (company size, lead source, contact phone). Add a second Close module to pull the full lead record. Click the + icon after the filter, search 'Close', and select 'Get a Lead'. Map the Lead ID field to the lead_id value from the webhook trigger output.

1. 1Click the + icon after the filter arrow
2. 2Search for 'Close' and select it
3. 3Choose 'Get a Lead' as the action
4. 4Select the same Close connection from the dropdown
5. 5In the Lead ID field, click the map icon and select 'lead_id' from the trigger output
6. 6Click OK

Make > Canvas > + > Slack > Look Up a User by Email

Look up the assigned rep's Slack user ID

Close stores the assigned rep as a Close user ID (e.g. 'user_abc123'), not a Slack username. You need to resolve this to a Slack user ID to route the message correctly. Add a Slack module: 'Look Up a User by Email'. In Close, the assigned user's email is available via the 'Get a Lead' output under assigned_to_email if you've mapped it, or you can add a 'Get a User' Close module first to resolve the Close user ID to an email, then feed that into the Slack lookup.

1. 1Click the + icon after the 'Get a Lead' module
2. 2Search 'Slack' and select it
3. 3Choose 'Look Up a User by Email'
4. 4Connect your Slack workspace (OAuth popup will appear)
5. 5In the Email field, map the assigned rep's email from the Close 'Get a Lead' output
6. 6Click OK

Make > Slack module > Connection > Add > OAuth

Connect your Slack workspace

If you didn't authenticate Slack in the previous step, click the Slack module, then click 'Add' next to Connection. Make opens an OAuth window — sign into your Slack workspace and authorize the Make app. Make needs the chat:write and users:read.email scopes at minimum for this workflow. These are granted automatically during the OAuth flow if your Slack admin has approved the Make app.

1. 1Click 'Add' next to the Connection field in the Slack module
2. 2Click 'Sign in with Slack' in the popup
3. 3Select your workspace from the dropdown
4. 4Review and click 'Allow' on the permissions screen
5. 5Return to Make — the connection should auto-populate

Make > Canvas > + > Slack > Send a Message

Add the Slack 'Send a Message' module

Add one more Slack module after the user lookup: 'Send a Message'. For the Channel field, use the Slack user ID from the previous step prefixed with nothing — when you pass a Slack user ID (U0XXXXXXX) as the channel, Slack sends the message as a direct message to that user. Alternatively, if your team uses named per-rep channels (like #rep-jordan), you can use a text formula to build the channel name dynamically from the rep's display name.

1. 1Click the + icon after the 'Look Up a User by Email' module
2. 2Select 'Slack' > 'Send a Message'
3. 3In the Channel field, map the Slack user ID from the lookup module output
4. 4Build the message text using the fields in the next step
5. 5Click OK after completing the message body

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

Make > Slack 'Send a Message' module > Text field

Build the Slack message with lead details

In the 'Send a Message' module, click into the Text field and build the message. Use Make's variable mapper to pull in fields from the 'Get a Lead' output. A good format includes: lead name, company, lead source, number of employees, primary contact name, phone, and email. Use Make's if() formula to handle null fields gracefully — for example, if company size isn't filled in, show 'Unknown' instead of a blank.

1. 1Click into the Text field of the 'Send a Message' module
2. 2Type the message structure and use the variable picker (click the map icon) to insert dynamic fields
3. 3Map: Lead Name from 'Get a Lead' > display_name
4. 4Map: Lead Source from 'Get a Lead' > lead_source
5. 5Map: Company Size from 'Get a Lead' > custom fields or num_employees
6. 6Map: Contact Name, Email, Phone from 'Get a Lead' > contacts[0]
7. 7Wrap optional fields in if() formulas to avoid blank lines

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

Make > Canvas > Run once button > Toggle (bottom of canvas)

Test and activate the scenario

Click 'Run once' at the bottom left of the canvas. In Close, open any lead and change its assigned owner — this fires the webhook. Return to Make and watch the execution bubble animate across each module. Click each module bubble to inspect the data it processed. Confirm the Slack message arrived in the correct channel. Once the test passes, click the toggle at the bottom of the canvas from OFF to ON to activate the scenario.

1. 1Click 'Run once' at the bottom left of the canvas
2. 2In Close, open any test lead and change the assigned owner
3. 3Return to Make and watch the execution complete
4. 4Click each module bubble to verify output data is correct
5. 5Check Slack to confirm the message arrived in the right channel
6. 6Click the ON/OFF toggle to activate the scenario

Paste this formula into the Text field of the Slack 'Send a Message' module in Make. It handles null fields for company size, phone, and lead source so your Slack messages never have empty bullet points. Replace the contacts[1] references with the actual array index Make resolves during mapping.

{{if(1.display_name; 1.display_name; 'Unnamed Lead')}}
*Source:* {{if(1.lead_source; 1.lead_source; 'Not specified')}}
*Company Size:* {{if(1.num_employees; toString(1.num_employees) + ' employees'; 'Unknown')}}

{{if(1.display_name; 1.display_name; 'Unnamed Lead')}}

*Source:* {{if(1.lead_source; 1.lead_source; 'Not specified')}}
*Company Size:* {{if(1.num_employees; toString(1.num_employees) + ' employees'; 'Unknown')}}
*Status:* {{if(1.status_label; 1.status_label; 'No status set')}}

*Primary Contact*
Name: {{if(2.contacts[].name; 2.contacts[].name; 'No contact name')}}
Email: {{if(2.contacts[].emails[].email; 2.contacts[].emails[].email; 'No email on file')}}
Phone: {{if(2.contacts[].phones[].phone; 2.contacts[].phones[].phone; 'No phone on file')}}

*Assigned to:* {{3.profile.real_name}}
<{{concat('https://app.close.com/lead/'; 1.lead_id; '/')}}|View in Close →>