How to Send Daily Close Pipeline Updates 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 your Scenarios dashboard. You'll land on the visual canvas with a single empty module in the center. This canvas is where you'll chain together the Close search, any data transformations, and the Slack post. Give the scenario a name immediately — click the default 'New scenario' text in the top left and type something like 'Daily Close Pipeline → Slack'.

1. 1Click 'Create a new scenario' in the top right
2. 2Click the pencil icon next to 'New scenario' in the top left
3. 3Type a descriptive name like 'Daily Close Pipeline → Slack'
4. 4Press Enter to save the name

Canvas > Empty module > Schedule

Add the Schedule trigger

Click the empty circular module on the canvas to open the module picker. Search for 'Schedule' and select it — this is Make's built-in clock trigger, not an app integration. Set the interval to 'Days' and configure the time to fire at 7:55 AM in your team's timezone. The five-minute buffer before standup matters: Close's API response can take 10-20 seconds for large result sets, and Slack delivery adds another few seconds.

1. 1Click the empty circular module on the canvas
2. 2Type 'Schedule' in the search box
3. 3Select 'Schedule' from the results
4. 4Set 'Run scenario' to 'Every day'
5. 5Set the time to 07:55 and select your team's timezone from the dropdown
6. 6Check the 'Days of the week' boxes for Monday through Friday only

Canvas > + > Close > Search Leads > Add connection

Connect Close and search for active leads

Click the '+' to the right of the Schedule module to add the next module. Search for 'Close' and select it from the app list. Choose the action 'Search Leads'. You'll be prompted to create a Close connection — click 'Add' and paste your Close API key (found in Close under Settings > API Keys). Name this connection something identifiable like 'Close – [Your Company]'. Once connected, configure the search query to pull active leads with open opportunities.

1. 1Click the '+' button to the right of the Schedule module
2. 2Type 'Close' in the search box and select the Close app
3. 3Choose 'Search Leads' as the action
4. 4Click 'Add' next to the Connection field
5. 5Paste your Close API key into the API Key field
6. 6Click 'Save' to establish the connection
7. 7In the 'Query' field, enter: status:"potential" or status:"active"
8. 8Set 'Limit' to 200 to capture full pipeline without pagination issues

Canvas > + > Flow Control > Iterator

Add an Iterator to process each lead

Add a new module after the Close search. Search for 'Flow Control' and select 'Iterator'. In the Array field, map the output array from the Close Search Leads module — it will appear as 'Array of Leads[]' in the variable picker. The Iterator will process each lead one at a time, making it possible to inspect each lead's nested opportunity data. This is required before you can aggregate the data into a single summary.

1. 1Click '+' after the Close Search Leads module
2. 2Search for 'Flow Control' and select it
3. 3Choose 'Iterator'
4. 4Click inside the 'Array' field
5. 5From the variable picker, select the leads array output from the Close module (labeled something like '1. Close – Leads[]')

Canvas > + > Flow Control > Numeric Aggregator

Add an Aggregator to build pipeline metrics

After the Iterator, add a 'Numeric Aggregator' module from Flow Control. This lets you sum opportunity values across all leads. Set the source module to your Iterator, the Aggregate function to 'SUM', and the Value field to the opportunity value path — something like {{item.opportunities[].value_period}}. You'll need one Numeric Aggregator for total pipeline value and a second one for opportunity count. Add the second aggregator as a parallel branch from the Iterator by right-clicking the Iterator and choosing 'Add another route'.

1. 1Click '+' after the Iterator module
2. 2Search for 'Flow Control' and select 'Numeric Aggregator'
3. 3Set 'Source Module' to your Iterator
4. 4Set 'Aggregate function' to 'SUM'
5. 5Map the 'Value' field to the opportunity's value field from Close
6. 6Right-click the Iterator to add a second route for opportunity count
7. 7Add a second Numeric Aggregator set to 'COUNT' on the same opportunity field

Canvas > Schedule module (right-click) > Add another route > Close > Search Activities

Search for overdue tasks in Close

Add another branch from the Schedule trigger — right-click the Schedule module and select 'Add another route'. On this new branch, add a Close module and select 'Search Activities'. Set the query to filter for tasks that are overdue: is_overdue:true type:task. Set Limit to 100. This runs in parallel with the lead search, so both queries fire at the same time and you don't wait for one to finish before starting the other.

1. 1Right-click the Schedule module on the canvas
2. 2Select 'Add another route'
3. 3Click the '+' on the new empty branch
4. 4Select the Close app
5. 5Choose 'Search Activities'
6. 6In the Query field, enter: is_overdue:true type:task
7. 7Set Limit to 100
8. 8Reuse your existing Close connection from the dropdown

Canvas > Schedule module (right-click) > Add another route > Close > Search Activities

Search for tasks due today

Add a third route from the Schedule trigger using the same right-click method. Add another Close Search Activities module. This time, set the query to filter for tasks due today using Close's date filter syntax: type:task date:"{{formatDate(now; 'YYYY-MM-DD')}}". Make's formatDate(now; 'YYYY-MM-DD') formula inserts today's date dynamically each time the scenario runs. Set Limit to 100.

1. 1Right-click the Schedule module and select 'Add another route'
2. 2Add a Close Search Activities module
3. 3In the Query field, type: type:task date:"
4. 4Click the formula icon and insert: formatDate(now; 'YYYY-MM-DD')
5. 5Close the quote: type:task date:"{{formatDate(now; 'YYYY-MM-DD')}}"
6. 6Set Limit to 100

Canvas > + > Tools > Set Multiple Variables

Add a Tools > Set Variable module to build the message

Now converge all three branches into a single message. Add a 'Tools' module and select 'Set Multiple Variables'. Map each variable from your three branches: total pipeline value (from Aggregator 1), total deal count (from Aggregator 2), overdue task count (from the overdue activities search), and today's task count. Use Make's formula bar to format the pipeline value with currency formatting. Name your variables clearly — pipeline_value, deal_count, overdue_tasks, tasks_today — because you'll reference them by name in the Slack message.

1. 1Add a new module after your three branches converge
2. 2Search for 'Tools' and select 'Set Multiple Variables'
3. 3Add variable: Name = pipeline_value, Value = {{divide(3.result; 100)}} (adjust module number to match your Aggregator)
4. 4Add variable: Name = deal_count, Value = {{4.result}}
5. 5Add variable: Name = overdue_tasks, Value = {{length(5.array)}}
6. 6Add variable: Name = tasks_today, Value = {{length(6.array)}}

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

Canvas > + > Slack > Create a Message

Format the Slack message with Block Kit

Add a Slack module and select 'Create a Message'. Connect your Slack workspace using OAuth — click 'Add' next to Connection, then authenticate with a Slack account that has permission to post to your target channel. Set the Channel field to your sales channel name (e.g., #sales-pipeline). For the message text, use Slack Block Kit JSON in the 'Blocks' field for a structured, scannable format. Use the variables you defined in the previous step to populate the metrics.

1. 1Add a Slack module after the Set Multiple Variables module
2. 2Select 'Create a Message'
3. 3Click 'Add' next to Connection and authenticate with Slack via OAuth
4. 4Set Channel to #sales-pipeline (or your target channel name)
5. 5Toggle on 'Use Blocks' if available, or paste Block Kit JSON into the Blocks field
6. 6Set the fallback Text field to: Daily Pipeline Update – {{formatDate(now; 'MMM D, YYYY')}}

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

Canvas > Right-click any module > Add error handler

Add an error handler for API failures

Right-click the Close Search Leads module and select 'Add error handler'. Choose 'Ignore' for non-critical paths, but for the Slack module, choose 'Rollback' so you don't get a partial message posted without all data. Alternatively, add a separate Slack module on the error path that posts to a #automation-alerts channel with the error message. This gives you visibility when Close's API is slow or returns an unexpected schema.

1. 1Right-click the Close Search Leads module
2. 2Select 'Add error handler'
3. 3Choose 'Break' to pause execution and log the error
4. 4Add a Slack module on the error handler path
5. 5Set the channel to #automation-alerts
6. 6Set the message to: ⚠️ Daily pipeline scenario failed. Error: {{error.message}}

Canvas > Toggle (bottom left) > ON | Canvas > Run once

Activate the scenario and verify the first run

Click the toggle in the bottom left of the canvas to turn the scenario ON. The toggle turns blue. Make will run the scenario at your next scheduled time, but you can also click 'Run once' to test immediately. After a successful run, check your Slack channel for the message and verify the numbers match what you see in Close's pipeline view. Check the scenario's execution log (History tab) to confirm all modules returned 'success' status with green checkmarks.

1. 1Click 'Run once' to trigger an immediate test run
2. 2Wait 15-30 seconds for all Close API calls to complete
3. 3Open your Slack channel and confirm the message posted correctly
4. 4Click the 'History' tab in Make to review the execution log
5. 5Confirm all modules show green status
6. 6Click the ON/OFF toggle to activate the scheduled scenario

Paste this into a Make 'Tools > Set Multiple Variables' module's value field for the pipeline_value variable. It formats the raw Close cents value as a dollar string with commas — e.g., 1850000 becomes $18,500. Replace `3.result` with the actual output number of your Numeric Aggregator module.

{{if(
  divide(3.result; 100) >= 1000000;
  concat(

{{if(
  divide(3.result; 100) >= 1000000;
  concat(
    "$";
    toString(floor(divide(3.result; 100000000)));
    ".";
    substring(toString(round(divide(3.result; 100))); -2);
    "M"
  );
  if(
    divide(3.result; 100) >= 1000;
    concat(
      "$";
      toString(floor(divide(3.result; 100000)));
      ",";
      padStart(toString(mod(floor(divide(3.result; 100)); 1000)); 3; "0")
    );
    concat(
      "$";
      toString(divide(3.result; 100))
    )
  )
)}}