How to Send Daily Close Pipeline Updates to Slack with Power Automate

make.powerautomate.com > My flows > + New flow > Scheduled cloud flow

Open Power Automate and Create a Scheduled Flow

Go to make.powerautomate.com and sign in. In the left sidebar, click 'My flows', then click '+ New flow' at the top. Select 'Scheduled cloud flow' from the dropdown — this is the trigger type that fires on a timer, not on an event. You'll immediately see a dialog asking for flow name, start date, and recurrence. Name it something like 'Daily Close Pipeline Digest'.

1. 1Click 'My flows' in the left sidebar
2. 2Click '+ New flow' in the top-right area
3. 3Select 'Scheduled cloud flow' from the dropdown
4. 4Enter a flow name: 'Daily Close Pipeline Digest'
5. 5Set recurrence to every 1 Day, starting at 9:00 AM in your team's timezone

Flow editor > + New step > Search 'HTTP' > HTTP action

Connect to Close CRM via HTTP Action

Close does not have a native Power Automate connector, so you'll use the built-in 'HTTP' action to call Close's REST API directly. Click '+ New step', search for 'HTTP', and select the 'HTTP' action (not 'HTTP webhook'). Close's API base URL is https://api.close.com/api/v1/. You'll authenticate using Basic Auth — your Close API key goes in the Username field, and the Password field stays blank.

1. 1Click '+ New step' below the Recurrence trigger
2. 2Type 'HTTP' in the search bar and select the 'HTTP' action
3. 3Set Method to 'GET'
4. 4Set URI to 'https://api.close.com/api/v1/opportunity/?_limit=100&_order_by=date_updated&status_type=active'
5. 5Expand 'Show advanced options', set Authentication to 'Basic', enter your Close API key as Username, leave Password blank

Flow editor > + New step > Search 'Parse JSON' > Data Operation: Parse JSON

Parse the Close API Response

The HTTP action returns a raw JSON string. You need to extract fields like deal name, value, status, and assigned user before you can format the message. Add a 'Parse JSON' action immediately after the HTTP step. In the Content field, reference the HTTP action's Body output using dynamic content. For the Schema, paste in the JSON structure from Close's opportunity response — the key fields are id, display_name, value, status_label, lead_name, assigned_to_name, and date_updated.

1. 1Click '+ New step' and search for 'Parse JSON'
2. 2Select 'Parse JSON' under 'Data Operation'
3. 3In the Content field, click 'Add dynamic content' and select 'Body' from the HTTP step
4. 4Click 'Generate from sample', paste a sample Close opportunity API response, and click 'Done'
5. 5Confirm the schema shows 'data' as an array containing opportunity objects

Flow editor > + New step > HTTP action (second instance)

Query Overdue Activities from Close

A useful pipeline digest includes overdue tasks, not just open deals. Add a second HTTP action to query Close's activity endpoint. You'll filter for tasks that are past due by using Close's date_done__lt parameter set to today's date. Use a Power Automate expression to generate today's date dynamically: utcNow('yyyy-MM-dd'). This second HTTP call runs in parallel with the first, keeping the flow fast.

1. 1Click '+ New step' and add another HTTP action
2. 2Set Method to 'GET'
3. 3Set URI to: concat('https://api.close.com/api/v1/task/?is_complete=false&date__lt=', utcNow('yyyy-MM-dd'), '&_limit=50')
4. 4Type the URI directly in the field and use the 'Expression' tab in dynamic content to insert utcNow('yyyy-MM-dd') inline
5. 5Apply the same Basic Auth as Step 2

Flow editor > + New step > Parse JSON (second instance)

Parse the Overdue Tasks Response

Add a second 'Parse JSON' action to handle the task query response. Follow the same process as Step 3 — set Content to the Body of the second HTTP action, and generate the schema from a sample task object. Key fields to capture are id, assigned_to_name, text (the task description), due_date, and lead_name. Rename this action 'Parse Overdue Tasks' to keep the canvas readable.

1. 1Add a 'Parse JSON' action after the second HTTP step
2. 2Set Content to the Body output of the overdue tasks HTTP action
3. 3Click 'Generate from sample' and paste a sample Close task object
4. 4Rename the action to 'Parse Overdue Tasks' by clicking the three-dot menu > Rename

Flow editor > + New step > Data Operation > Compose

Calculate Pipeline Summary Metrics

Before posting to Slack, compute aggregate numbers: total open pipeline value and count of overdue tasks. Add a 'Compose' action for each metric. For total pipeline value, use the expression: sum(body('Parse_JSON')?['data'], 'value'). For overdue task count: length(body('Parse_Overdue_Tasks')?['data']). These Compose outputs give you single values you can drop into the Slack message without looping.

1. 1Add a 'Compose' action and name it 'Total Pipeline Value'
2. 2In Inputs, paste expression: div(sum(body('Parse_JSON')?['data'], 'value'), 100) — Close stores value in cents
3. 3Add a second 'Compose' action named 'Overdue Task Count'
4. 4In Inputs, paste expression: length(body('Parse_Overdue_Tasks')?['data'])

Flow editor > + New step > Control > Apply to each

Build the Slack Message with Apply to Each

Now format the digest. Add an 'Apply to each' action (found under 'Control') and set its input to the data array from the opportunities Parse JSON step. Inside the loop, add a 'Compose' action that builds one line per deal using dynamic content fields: display_name, assigned_to_name, status_label, and the value field. Use a simple format like: '• [display_name] — [assigned_to_name] — $[value] — [status_label]'. This produces a line-item list you'll join into a single string before posting.

1. 1Click '+ New step', go to 'Control', and select 'Apply to each'
2. 2Set the 'Select an output from previous steps' field to body('Parse_JSON')?['data']
3. 3Inside the loop, add a 'Compose' action
4. 4Build the message line using dynamic content: concat('• ', items('Apply_to_each')?['display_name'], ' — ', items('Apply_to_each')?['assigned_to_name'], ' — $', string(div(items('Apply_to_each')?['value'], 100)), ' — ', items('Apply_to_each')?['status_label'])
5. 5Name this inner Compose 'Format Deal Line'

Flow editor > + New step > Data Operation > Join

Join Deal Lines into One String

After the Apply to each loop, the formatted deal lines are stored as an array of Compose outputs. You need to join them into a single block of text for the Slack message. Add a 'Join' action (under Data Operation) after the loop. Set the 'From' field to the outputs of the Format Deal Line Compose action using the expression: outputs('Format_Deal_Line'). Set the Join With field to a newline character using the expression: decodeUriComponent('%0A').

1. 1Add a 'Join' action after the Apply to each loop
2. 2In the 'From' field, use expression: outputs('Format_Deal_Line')
3. 3In 'Join With', use expression: decodeUriComponent('%0A') to insert newlines between each deal line
4. 4Name this action 'Join Deal Lines'

Flow editor > + New step > Search 'Slack' > Post message in a chat or channel

Connect Slack and Configure the Channel

Add a 'Post message in a chat or channel' action from the Slack connector. Search for 'Slack' in the action picker — Power Automate has a native Slack connector. When you add it for the first time, it will prompt you to sign in to Slack and authorize the Power Automate app. Make sure you authorize it in the correct Slack workspace. Set Post As to 'Flow bot', select your channel name (e.g., #sales-pipeline), and leave the message body empty for now.

1. 1Click '+ New step' and search for 'Slack'
2. 2Select 'Post message in a chat or channel'
3. 3Click 'Sign in' to create a new Slack connection — authorize in the browser popup
4. 4Set 'Post As' to 'Flow bot'
5. 5Set 'Channel Name' to your target channel, e.g. #sales-pipeline

Flow editor > Slack action > Message Text field

Compose the Full Slack Message

Now build the final message text inside the Slack action's Message Text field. Combine the pipeline header, the joined deal list, and the overdue task count into one formatted block. Use dynamic content and expressions to pull from the Compose actions created in Steps 6 and 8. Structure the message with a header line, total pipeline value, number of overdue tasks, and the full deal list beneath.

1. 1Click inside the 'Message Text' field of the Slack action
2. 2Type a header: '*📊 Daily Pipeline Report — ' then use expression formatDateTime(utcNow(), 'MMMM d, yyyy') to append today's date, then close with '*'
3. 3Add a newline then: '*Total Open Pipeline:* $' followed by dynamic content from the 'Total Pipeline Value' Compose
4. 4Add another line: '*Overdue Tasks:* ' followed by dynamic content from 'Overdue Task Count' Compose
5. 5Add a blank line then paste the output of 'Join Deal Lines' to list all deals

Flow editor > Test (top right) > Manually > Run flow

Test and Activate the Flow

Before turning the flow on, run a manual test. Click 'Test' in the top-right toolbar, select 'Manually' and then 'Run flow'. Watch the run history panel on the right — each action card will show a green checkmark or red X. Check that the Slack message appears in your channel with correct data and formatting. Once the test passes, click 'Save' and confirm the flow is toggled to 'On' in My flows.

1. 1Click 'Test' in the top-right corner of the flow editor
2. 2Select 'Manually' and click 'Run flow'
3. 3Watch each action card turn green as the run progresses
4. 4Open your Slack channel to verify the message arrived and looks correct
5. 5Click 'Save' and then navigate to 'My flows' to confirm the flow status shows 'On'

Paste this into a 'Compose' action placed right after the two Parse JSON steps. It builds a complete formatted Slack Block Kit message as a JSON string using Power Automate expressions, giving you bold headers, dividers, and color-coded sections instead of plain text. Reference the output of this Compose action in the Slack 'Post message' action's 'Blocks' field (not the Message Text field).

{
  "blocks": [
    {

{
  "blocks": [
    {
      "type": "header",
      "text": {
        "type": "plain_text",
        "text": "@{concat('📊 Daily Pipeline Report — ', formatDateTime(utcNow(), 'MMMM d, yyyy'))}"
      }
    },
    {
      "type": "section",
      "fields": [
        {
          "type": "mrkdwn",
          "text": "@{concat('*Total Open Pipeline:*\n$', string(outputs('Total_Pipeline_Value')))}"
        },
        {
          "type": "mrkdwn",
          "text": "@{concat('*Overdue Tasks:*\n', string(outputs('Overdue_Task_Count')), ' tasks past due')}"
        }
      ]
    },
    {
      "type": "divider"
    },
    {
      "type": "section",
      "text": {
        "type": "mrkdwn",
        "text": "@{concat('*Open Deals:*\n', outputs('Join_Deal_Lines'))}"
      }
    },
    {
      "type": "context",
      "elements": [
        {
          "type": "mrkdwn",
          "text": "@{concat('Generated at ', formatDateTime(utcNow(), 'h:mm tt'), ' UTC · Data from Close CRM')}"
        }
      ]
    }
  ]
}