Get Slack alerts for new Close CRM leads, won deals, or call activity from your sales team. Set up this automation with Make.com, Zapier, n8n, or Pabbly Connect — no coding required.
When a new record is created in Close CRM, automatically trigger an action in Slack
Sync data between Close CRM and Slack in real time without manual exports
Send notifications to Slack when important events happen in Close CRM
Create or update Slack records based on activity in Close CRM
Build multi-step workflows that start in Close CRM and flow through Slack
Choose the platform you want to use. All four support this Close CRM + Slack integration.
Log into Make.com and click "Create a new scenario."
Click the + button, search for "Close CRM", and select it as your trigger module.
Connect your Close CRM account using your API key or OAuth credentials.
Configure the trigger: choose what to watch (new records, updates, or specific events) and set any filters.
Click + to add a new module, search for "Slack", and select the action you want to perform.
Connect your Slack account and use Make's data mapper to link fields from the Close CRM trigger to the Slack action.
Click "Run once" to test the scenario with real data. Fix any mapping errors highlighted in red.
Set a schedule (e.g., every 15 minutes) and toggle the scenario to ON. Your automation is live.
Log into Zapier and click "Create Zap."
Choose Close CRM as your Trigger app and select the trigger event (e.g., "New Record", "New Contact").
Connect your Close CRM account and click "Continue." Zapier will test the connection and fetch sample data.
Click "Continue" past the test step once sample data appears.
Add Slack as your Action app and select the action event (e.g., "Send Message", "Create Record").
Connect your Slack account and map the fields from your Close CRM trigger data to the Slack action fields.
Click "Test action" to confirm the action runs correctly with the sample data.
Name your Zap, click "Publish," and turn it on. Zapier will now run this automatically.
Open n8n and click "New Workflow."
Add a Close CRM node as your trigger. Search for it in the node panel and drag it onto the canvas.
Click the node, select "Create New Credential," and enter your Close CRM API key or OAuth details.
Choose the operation to watch (e.g., "On New Record") and configure any filters.
Click + to add a Slack node and connect it to the Close CRM node's output pin.
Configure the Slack node: select credentials, choose the action, and use expressions ({{ $json.fieldName }}) to map data from Close CRM.
Click "Execute Workflow" to run a manual test. Check the output panel to confirm the data flows correctly.
Click "Activate" to enable the workflow. n8n will now run it on the configured trigger or schedule.
Sales CRM with built-in calling, SMS, and email for inside sales teams
Team messaging and collaboration platform with channels and integrations
Choose a platform to connect Close CRM and Slack. All options below support this integration.
The market leader — 8,000+ integrations
No. Make.com, Zapier, n8n (cloud), and Pabbly Connect are all no-code or low-code tools. You configure connections through visual interfaces. n8n offers optional JavaScript nodes for advanced logic, but the basic Close CRM+Slack setup requires no code.
Pabbly Connect offers a lifetime deal with unlimited automations, making it the lowest long-term cost for high-volume workflows. Make.com's free plan includes 1,000 operations/month. Zapier's free plan is limited to 100 tasks/month. n8n is free to self-host.
It depends on the platform and plan. Make.com runs scenarios on a schedule you set (minimum 1 minute on paid plans, 15 minutes on free). Zapier polls triggers every 1–15 minutes depending on your plan. n8n can be triggered instantly via webhooks. Pabbly runs instantly when triggered.
All four platforms send email alerts when a workflow fails. Make.com shows error details in the scenario history. Zapier shows failed tasks in the Task History tab. n8n logs errors in the execution log. Pabbly shows error details in the workflow run history.