How to Share Close Prospects to Slack with Pipedream

pipedream.com > Workflows > New Workflow

Create a new Pipedream Workflow

Go to pipedream.com and log in. Click 'New Workflow' in the top-right corner of the dashboard. You'll land on the workflow builder canvas with an empty trigger slot at the top. Give the workflow a name like 'Close → Slack Prospect Research Brief' so it's easy to find later.

1. 1Click 'New Workflow' in the top-right of the Pipedream dashboard
2. 2Click the trigger slot labeled 'Add a trigger'
3. 3Type 'Close' in the search box
4. 4Select 'Close (CRM)' from the app list

Trigger Step > Close CRM > Opportunity Status Changed

Configure the Close trigger event

In the Close trigger panel, choose 'New Activity' or 'Opportunity Status Changed' as your event — use 'Opportunity Status Changed' for stage-based research briefs. Connect your Close account via Connected Accounts by clicking 'Connect Close CRM' and entering your Close API key. Set the Status filter to the stage that signals a call is coming, such as 'Demo Scheduled' or 'Negotiating'.

1. 1Select 'Opportunity Status Changed' from the Close event dropdown
2. 2Click 'Connect Close CRM' and paste your Close API key into the dialog
3. 3Click 'Save' to confirm the connection
4. 4Set the 'Status' filter field to your target stage, e.g. 'Demo Scheduled'
5. 5Click 'Test Trigger' to pull a sample event

Workflow Canvas > + Add Step > Node.js Code

Add a Node.js step to fetch full opportunity details

The trigger payload gives you the opportunity ID and basic fields, but it won't include the full contact list, all custom fields, or conversation history. Add a Node.js code step immediately after the trigger to call the Close REST API and pull the complete opportunity record. This ensures the Slack message has everything the team needs without a second manual lookup.

1. 1Click the '+' button below the trigger step
2. 2Select 'Run Node.js code' from the step menu
3. 3Rename the step to 'fetch_opportunity_details' using the step name field at the top

Workflow Canvas > fetch_opportunity_details > Code Editor

Write the Close API fetch logic

Paste your Node.js code into the code step to hit Close's opportunity endpoint and activity endpoint. Use your Close API key stored as a Pipedream environment variable — never hardcode it in the step. The code should return a structured object with company name, deal value, assigned user, contact emails, and the last 3 activity summaries. Click 'Test' to verify the API call returns real data.

1. 1Open Pipedream Settings > Environment Variables and add CLOSE_API_KEY
2. 2Paste the fetch code into the Node.js editor (see pro tip below)
3. 3Click 'Test' to run the step against the sample trigger payload
4. 4Verify the returned object contains company_name, deal_value, and activities array

Workflow Canvas > + Add Step > Node.js Code

Add a step to resolve the assigned user name

The Close opportunity record stores assigned_to as a user ID like 'user_abc123', not a display name. Add a second Node.js step to call Close's /user/{id} endpoint and resolve it to a readable name before it appears in the Slack message. Skipping this step means teammates see an opaque ID in the 'AE' field of the Slack post.

1. 1Click '+' below the fetch_opportunity_details step
2. 2Select 'Run Node.js code'
3. 3Rename the step to 'resolve_user_name'
4. 4Use steps.fetch_opportunity_details.$return_value.assigned_to as the user ID input
5. 5Call GET https://api.close.com/api/v1/user/{id}/ and return the display_name

Paste this code into a Node.js step named 'fetch_opportunity_details' placed immediately after the Close trigger. It calls the Close opportunity endpoint, resolves the assigned user's display name in the same step, and returns a clean object ready to reference in your Slack Block Kit payload — no separate user-resolution step needed.

import axios from 'axios';
export default defineComponent({
  async run({ steps, $ }) {

import axios from 'axios';

export default defineComponent({
  async run({ steps, $ }) {
    const apiKey = process.env.CLOSE_API_KEY;
    const opportunityId = steps.trigger.event.data.id;
    const baseURL = 'https://api.close.com/api/v1';
    const auth = { username: apiKey, password: '' };

    // Fetch full opportunity record
    const oppResponse = await axios.get(`${baseURL}/opportunity/${opportunityId}/`, { auth });
    const opp = oppResponse.data;

    // Resolve assigned user to display name
    let assignedName = 'Unassigned';
    if (opp.assigned_to) {
      try {
        const userResponse = await axios.get(`${baseURL}/user/${opp.assigned_to}/`, { auth });
        assignedName = userResponse.data.display_name || 'Unassigned';
      } catch (e) {
        console.log(`Could not resolve user ${opp.assigned_to}: ${e.message}`);
      }
    }

    // Fetch last 3 activities for this lead
    const activityResponse = await axios.get(`${baseURL}/activity/`, {
      auth,
      params: {
        lead_id: opp.lead_id,
        _limit: 3,
        _order: '-date_created',
      },
    });

    const activities = activityResponse.data.data.map((a) => ({
      type: a._type,
      subject: a.subject || a.direction || 'Activity',
      preview: (a.body_preview || a.note || '').substring(0, 280),
      date: a.date_created,
    }));

    // Build Close opportunity URL
    const closeUrl = `https://app.close.com/opportunity/${opportunityId}/`;

    return {
      company_name: opp.lead_name,
      deal_value: opp.value ? `$${Number(opp.value).toLocaleString()}` : 'Not set',
      status: opp.status_label,
      assigned_to_name: assignedName,
      contact_name: opp.contacts?.[0]?.display_name || 'Unknown contact',
      contact_email: opp.contacts?.[0]?.emails?.[0]?.email || 'No email on file',
      expected_date: opp.expected_date || 'Not set',
      lead_source: opp.lead?.source || 'Unknown',
      activities,
      close_url: closeUrl,
    };
  },
});

Workflow Canvas > + Add Step > Slack > Send Message to Channel

Add a Slack step and connect your workspace

Click '+' below the user resolution step and search for 'Slack'. Select the 'Send a Message to a Channel' action. Click 'Connect Slack' — this opens an OAuth flow where you authorize Pipedream to post to your workspace. You'll need to be a Slack admin or have permission to install apps. Select the target channel (e.g. #deal-research) from the dropdown.

1. 1Click '+' and search for 'Slack'
2. 2Select 'Send a Message to a Channel'
3. 3Click 'Connect Slack' and complete the OAuth authorization
4. 4Select your target channel from the Channel dropdown, e.g. '#deal-research'
5. 5Leave the message body blank for now — you'll fill it in the next step

Workflow Canvas > Slack Step > Blocks Field

Build the Slack Block Kit message

In the Slack step's 'Blocks' field, build a structured Block Kit payload that organizes the prospect data into readable sections. Use Slack's Block Kit Builder (app.slack.com/block-kit-builder) to prototype your layout first, then paste the JSON into Pipedream's Blocks field. Reference upstream step outputs using Pipedream's double-brace syntax: {{steps.fetch_opportunity_details.$return_value.company_name}}. Include a header block with the company name, a section block for deal value and assigned AE, a divider, and a context block with the last 3 activity snippets.

1. 1Click into the 'Blocks' field in the Slack step
2. 2Paste your Block Kit JSON structure
3. 3Replace static values with Pipedream variable references like {{steps.fetch_opportunity_details.$return_value.company_name}}
4. 4Add a 'Reply in thread' or button block pointing to the Close opportunity URL
5. 5Click 'Test' to send a real message to your channel

Workflow Canvas > Step Settings (···) > Error Handling

Add error handling with a fallback notification

Add a final Node.js step after the Slack step configured to run on error. In Pipedream, click the step settings (three dots) on any step and toggle 'Continue on error' if you want the workflow to proceed even when Close is slow. Alternatively, add a separate error handler step that pings a #alerts channel with the failure reason. This prevents silent failures where a deal moves to 'Demo Scheduled' but no research brief appears in Slack.

1. 1Click the '···' menu on the fetch_opportunity_details step
2. 2Toggle 'Continue workflow on error' if you want non-blocking behavior
3. 3Add a new Node.js step at the end labeled 'error_alert'
4. 4Use $.send.http or the Slack step to post to #alerts if any upstream step fails
5. 5Reference the error object via process.env or the workflow's error context

Workflow Canvas > Event History

Test end-to-end with a real Close opportunity

In Close, manually move a real test opportunity to your target stage. In Pipedream, click 'Event History' on the workflow to watch for the incoming event. Confirm all three steps executed: the opportunity fetch returned data, the user name resolved correctly, and the Slack message posted with the right company and deal value. Check the Slack channel directly to verify formatting looks correct on desktop and mobile.

1. 1Move a test opportunity to your target stage in Close
2. 2Open Pipedream > Workflows > [your workflow] > Event History
3. 3Click the incoming event to expand the step-by-step execution log
4. 4Verify each step shows a green checkmark and populated output
5. 5Check #deal-research in Slack to confirm the message arrived and is formatted correctly

Workflow Builder > Deploy > Settings > Concurrency

Deploy the workflow and set concurrency settings

Click 'Deploy' in the top-right corner of the workflow builder. Pipedream will activate the webhook listener for Close events. Before finishing, go to the workflow's Settings tab and configure the concurrency limit. For this use case, 1 concurrent execution is enough — if two deals change stage simultaneously, Pipedream will queue the second event rather than running both at once and potentially hitting Close rate limits.

1. 1Click the blue 'Deploy' button in the top-right
2. 2Navigate to the workflow's Settings tab
3. 3Set 'Max concurrent executions' to 1 or 2
4. 4Confirm the workflow status shows 'Active' in the workflow list