How to Send Close Lead Assignments to Slack with Zapier

zapier.com > Dashboard > Create Zap

Create a new Zap in Zapier

Log in to zapier.com and click the orange 'Create Zap' button in the top-left sidebar. You'll land on the Zap editor — a two-column layout with a trigger panel on the left and a canvas on the right. Give your Zap a name at the top: something like 'Close Lead Assigned → Slack Notification'. This name appears in your Zap history and task logs, so make it descriptive.

1. 1Click 'Create Zap' in the left sidebar
2. 2Click the name field at the top and type 'Close Lead Assigned → Slack Notification'
3. 3Click the trigger panel labeled 'Trigger' to open the app search

Zap Editor > Trigger > App & Event

Set Close as the trigger app

In the trigger panel, type 'Close' into the app search bar and select the Close CRM app (it shows the Close logo — a blue circle with a white C). Click 'Choose event' and select 'New or Updated Lead' from the dropdown. This trigger uses Close's webhook infrastructure, so it fires within seconds of a change, not on a polling schedule.

1. 1Type 'Close' in the app search field
2. 2Select 'Close' from the results list
3. 3Click 'Choose event' dropdown
4. 4Select 'New or Updated Lead'

Close > Settings > API Keys

Connect your Close account

Click 'Sign in to Close' — Zapier opens a popup asking for your Close API key. Go to Close > Settings > API Keys, generate a new key, and paste it into Zapier. Give it a label like 'Zapier Integration' so you can identify it later. Zapier will test the connection by making a lightweight API call and show a success state.

1. 1Click 'Sign in to Close' in the Zapier trigger panel
2. 2In a new tab, go to Close > Settings > API Keys
3. 3Click 'Generate API Key', copy the key
4. 4Paste the key into the Zapier popup and click 'Yes, Continue to Close'

Zap Editor > Trigger > Test

Test the Close trigger and pull sample data

Click 'Test trigger' — Zapier pulls the 3 most recently updated leads from your Close account to use as sample data. Scan the returned fields to confirm you see 'assigned_to', 'lead_source', 'company', 'num_employees', and contact details. If your sample leads are missing 'assigned_to', it means those leads were never assigned — go to Close, assign a test lead, then re-run the test.

1. 1Click 'Test trigger'
2. 2Review the returned sample data fields
3. 3Confirm 'assigned_to_id' and 'assigned_to_name' appear in the list
4. 4If missing, assign a lead in Close and click 'Test trigger' again

Zap Editor > + > Filter by Zapier

Add a Filter to catch only assignment changes

Click the '+' button below the trigger step and add a 'Filter by Zapier' action. This step prevents the Zap from firing on every lead update — you only want it to fire when a lead gets assigned or reassigned. Set the filter condition to: 'Assigned To Name' exists (is not empty). If your team also needs to catch reassignments, add a second condition watching for 'Assigned To Name' changed — but 'exists' covers most cases.

1. 1Click the '+' button below the trigger step
2. 2Search for 'Filter by Zapier' and select it
3. 3Set Field to 'Assigned To Name'
4. 4Set Condition to '(Text) Exists'
5. 5Click 'Continue'

Zap Editor > + > Formatter by Zapier > Text > Compose

Add a Formatter step to build the Slack message

Click '+' to add another step and choose 'Formatter by Zapier', then select 'Text' and the 'Compose' transform. This lets you build a clean, multi-line Slack message by combining Close fields into a single text block. You'll reference dynamic fields from the trigger — company name, assigned rep name, lead source, employee count, and primary contact email. This avoids hacking together messy text inside the Slack message template itself.

1. 1Click '+' below the Filter step
2. 2Search for 'Formatter by Zapier' and select it
3. 3Choose 'Text' as the action
4. 4Choose 'Compose' as the transform
5. 5In the 'Input' field, build your message using the template below

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

Zap Editor > + > Slack > Send Channel Message

Connect Slack and choose the Send Channel Message action

Click '+' to add the final action step. Search for 'Slack' and select it. Choose 'Send Channel Message' as the action event — this posts a message to a specific channel rather than a DM. You'll connect your Slack workspace by clicking 'Sign in to Slack' and authorizing Zapier through OAuth. Make sure you authorize with an account that has access to the rep-specific channels you want to post in.

1. 1Click '+' below the Formatter step
2. 2Search for 'Slack' and select it
3. 3Select 'Send Channel Message' as the action event
4. 4Click 'Sign in to Slack'
5. 5Authorize Zapier in the Slack OAuth popup

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

Zap Editor > Slack Action > Configure > Channel

Map the Slack channel dynamically by rep name

In the 'Channel' field of the Slack action, you have two options: hardcode a single channel like #new-leads, or route to rep-specific channels like #leads-sarah or #leads-marcus. For rep-specific routing, type the channel prefix '#leads-' and then insert the 'Assigned To Name' dynamic field from Close. Zapier will concatenate these into a channel name like '#leads-sarah'. Your Slack channels must already exist and follow the exact naming convention — Zapier will throw an error if the channel doesn't exist.

1. 1Click into the 'Channel' field
2. 2Type '#leads-' as a static prefix
3. 3Click the '+' icon to insert a dynamic field
4. 4Select 'Assigned To Name' from the Close trigger data
5. 5Verify the preview shows '#leads-[rep name]'

Zap Editor > Slack Action > Configure > Message Text

Configure the Slack message content

In the 'Message Text' field, insert the composed message output from your Formatter step. Add a Bot Name like 'LeadBot' and upload a small icon emoji (🎯 works well) under 'Bot Icon'. Set 'Send as Bot' to true — this prevents the message from showing as your personal Zapier account name. Leave 'Link Names' set to true so @mentions in the message resolve to actual Slack users if you include them.

1. 1Click into 'Message Text' and insert the Formatter output field
2. 2Set 'Bot Name' to 'LeadBot'
3. 3Set 'Bot Icon' to ':dart:'
4. 4Set 'Send as Bot?' to 'True'
5. 5Set 'Link Names?' to 'True'

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

Zap Editor > Slack Action > Test

Test the full Zap end-to-end

Click 'Test action' — Zapier will post a real message to the Slack channel using your sample Close data. Go to Slack immediately and confirm the message arrived in the correct channel with the right formatting. Check that the company name, lead source, employee count, and contact email all display correctly. If the channel lookup fails, you'll see a specific error message like 'channel_not_found' — go back to step 8 and verify the channel name format.

1. 1Click 'Test action'
2. 2Open Slack and navigate to the channel that should have received the message
3. 3Confirm all fields display correctly
4. 4If you see 'channel_not_found', go back to the Channel field and fix the naming

Zap Editor > Publish

Turn on the Zap

Click 'Publish' in the top-right corner of the Zap editor. Zapier will run a final validation check and then activate the Zap. The status indicator at the top will turn from gray to green. From this point, every time a lead is assigned in Close, the filter evaluates it and the Slack message fires within 60-90 seconds. Monitor the Zap's task history for the first 24 hours to catch any channel name mismatches from real lead assignments.

1. 1Click the 'Publish' button in the top-right
2. 2Confirm the Zap status turns green
3. 3Navigate to 'Zap History' in the left sidebar
4. 4Assign a test lead in Close and watch for a new task to appear in history within 2 minutes

This Code by Zapier step replaces the Formatter step entirely. It builds the Slack message, constructs the Close lead URL from the lead ID, handles empty fields with fallbacks, and normalizes the rep name into a valid Slack channel slug. Paste this into a 'Code by Zapier' action (JavaScript) inserted between the Filter step and the Slack action. Map inputData fields to the corresponding Close trigger output fields in the input section.

const {
  assigned_to_name = '',
  display_name = 'Unknown Company',

const {
  assigned_to_name = '',
  display_name = 'Unknown Company',
  lead_source = 'Unknown',
  num_employees = 'Unknown',
  contact_email = '',
  contact_phone = '',
  status_label = 'Unknown',
  lead_id = ''
} = inputData;

// Build a valid Slack channel slug from rep name
// e.g. 'Sarah Kim' -> 'sarah-kim'
const repSlug = assigned_to_name
  .toLowerCase()
  .trim()
  .replace(/\s+/g, '-')
  .replace(/[^a-z0-9-]/g, '');

// Build direct Close lead URL
const leadUrl = lead_id
  ? `https://app.close.com/lead/${lead_id}/`
  : 'URL unavailable';

// Compose the Slack message with fallbacks for every field
const message = [
  `*\ud83c\udfaf New Lead Assigned: ${display_name}*`,
  `*Rep:* ${assigned_to_name || 'Unassigned'}`,
  `*Contact:* ${contact_email || 'No email'} | ${contact_phone || 'No phone'}`,
  `*Source:* ${lead_source} | *Employees:* ${num_employees}`,
  `*Status:* ${status_label}`,
  `*Close Record:* ${leadUrl}`
].join('\n');

output = [
  {
    slack_channel: `#leads-${repSlug}`,
    slack_message: message,
    lead_url: leadUrl,
    rep_slug: repSlug
  }
];