How to Share Notion Meeting Notes to Slack with Pipedream

pipedream.com > Workflows > New Workflow

Create a new Pipedream workflow

Go to pipedream.com and sign in. Click 'New Workflow' in the top-right corner of the dashboard. You'll land on the workflow canvas with an empty trigger slot at the top. Give the workflow a name like 'Notion → Slack Meeting Notes' using the pencil icon next to the default title — this saves confusion when you have multiple workflows later.

1. 1Click 'New Workflow' in the top-right
2. 2Click the pencil icon next to the default workflow title
3. 3Type 'Notion → Slack Meeting Notes' and press Enter

Workflow Canvas > Add a trigger > Notion > New Page in Database

Add the Notion 'New Page in Database' trigger

Click the 'Add a trigger' block on the canvas. Search for 'Notion' in the app search bar and select it. Choose the trigger called 'New Page in Database' — this polls your chosen Notion database every 15 minutes for newly created pages. You'll be prompted to connect your Notion account via Pipedream's Connected Accounts.

1. 1Click 'Add a trigger'
2. 2Type 'Notion' in the search bar and select the Notion app
3. 3Select 'New Page in Database' from the trigger list
4. 4Click 'Connect a new Notion account' and complete the OAuth flow

Trigger Config > Database ID dropdown

Select your Meeting Notes database

With Notion connected, a 'Database ID' dropdown appears in the trigger configuration panel. Click it to see the databases you granted access to. Select the database where meeting notes are created — for example, 'Meeting Notes 2024.' If you don't see it, your Notion OAuth grant didn't include that database. Set the polling interval to 15 minutes (the default) unless you need faster delivery, in which case 5 minutes is the minimum.

1. 1Click the 'Database ID' dropdown
2. 2Select your meeting notes database from the list
3. 3Leave polling interval at 15 minutes or change to 5 minutes for faster delivery
4. 4Click 'Save and continue'

Workflow Canvas > Trigger Step > Output panel (right side)

Inspect the trigger output

After generating a test event, click the trigger step to expand its output panel on the right. You'll see the raw Notion page object in JSON. Locate the fields you'll need: 'properties.Name.title[0].plain_text' for the page title, 'created_by.name' for the creator, and 'url' for the direct Notion link. These are the paths you'll reference in later steps. Take note of any custom properties in your database — meeting type, project tag, or assigned team — that you might want to include in the Slack message.

1. 1Click on the trigger step block to expand the output
2. 2Look for 'properties.Name.title[0].plain_text' in the JSON tree
3. 3Look for 'created_by.name'
4. 4Look for 'url'

Workflow Canvas > + Add Step > Run Node.js code

Add a Node.js code step to build the Slack message

Click the '+' button below the trigger to add a new step. Choose 'Run Node.js code' from the step type list. This step will extract the relevant fields from the Notion page object and format them into a clean Slack message. Using a code step here instead of going directly to the Slack action gives you control over the message format and lets you add conditional logic — for example, only notifying if the page has a specific tag or was created by a specific team.

1. 1Click the '+' button below the trigger block
2. 2Select 'Run Node.js code' from the step list
3. 3Rename the step to 'Format Slack Message' using the step title field

Paste this into the 'Run Node.js code' step (step 5 on the canvas). It reads directly from the Notion trigger output at 'steps.trigger.event', formats a Block Kit message with a header, metadata section, and link button, and returns the blocks array for the Slack action to consume.

export default defineComponent({
  async run({ steps, $ }) {
    // Pull fields from Notion trigger output

export default defineComponent({
  async run({ steps, $ }) {
    // Pull fields from Notion trigger output
    const page = steps.trigger.event;

    // Safe title extraction with fallback
    const title =
      page?.properties?.Name?.title?.[0]?.plain_text ||
      "Untitled Meeting Notes";

    const createdBy = page?.created_by?.name || "Unknown";
    const pageUrl = page?.url || "";

    // Format the creation timestamp to something human-readable
    const rawDate = page?.created_time;
    const formattedDate = rawDate
      ? new Date(rawDate).toLocaleString("en-US", {
          month: "short",
          day: "numeric",
          year: "numeric",
          hour: "numeric",
          minute: "2-digit",
          timeZone: "America/New_York",
        })
      : "Unknown time";

    // Optional: extract a custom 'MeetingType' select property if it exists
    const meetingType =
      page?.properties?.MeetingType?.select?.name || null;

    const typeLabel = meetingType ? ` · ${meetingType}` : "";

    // Build Slack Block Kit payload
    const blocks = [
      {
        type: "header",
        text: {
          type: "plain_text",
          text: `📝 ${title}`,
          emoji: true,
        },
      },
      {
        type: "section",
        text: {
          type: "mrkdwn",
          text: `*Posted by:* ${createdBy}${typeLabel}\n*Created:* ${formattedDate}`,
        },
      },
      {
        type: "actions",
        elements: [
          {
            type: "button",
            text: {
              type: "plain_text",
              text: "View Notes in Notion",
              emoji: true,
            },
            url: pageUrl,
            style: "primary",
          },
        ],
      },
      {
        type: "divider",
      },
    ];

    // Return blocks for the next Slack step to consume
    return { blocks, title, createdBy, formattedDate, pageUrl };
  },
});

Workflow Canvas > Format Slack Message step > Code editor

Write the message formatting code

Paste the code from the Pro Tip section into the code editor, replacing the default content. This code reads from the Notion trigger output and builds a structured Slack Block Kit message with the page title, creator, creation time, and a link button. After pasting, click 'Test' to run the step against your test event and confirm the output object contains a formatted 'blocks' array ready for Slack.

1. 1Select all default code in the editor and delete it
2. 2Paste the Pro Tip code
3. 3Click 'Test' in the step toolbar
4. 4Expand the output panel and confirm 'blocks' is populated

Paste this into the 'Run Node.js code' step (step 5 on the canvas). It reads directly from the Notion trigger output at 'steps.trigger.event', formats a Block Kit message with a header, metadata section, and link button, and returns the blocks array for the Slack action to consume.

export default defineComponent({
  async run({ steps, $ }) {
    // Pull fields from Notion trigger output

export default defineComponent({
  async run({ steps, $ }) {
    // Pull fields from Notion trigger output
    const page = steps.trigger.event;

    // Safe title extraction with fallback
    const title =
      page?.properties?.Name?.title?.[0]?.plain_text ||
      "Untitled Meeting Notes";

    const createdBy = page?.created_by?.name || "Unknown";
    const pageUrl = page?.url || "";

    // Format the creation timestamp to something human-readable
    const rawDate = page?.created_time;
    const formattedDate = rawDate
      ? new Date(rawDate).toLocaleString("en-US", {
          month: "short",
          day: "numeric",
          year: "numeric",
          hour: "numeric",
          minute: "2-digit",
          timeZone: "America/New_York",
        })
      : "Unknown time";

    // Optional: extract a custom 'MeetingType' select property if it exists
    const meetingType =
      page?.properties?.MeetingType?.select?.name || null;

    const typeLabel = meetingType ? ` · ${meetingType}` : "";

    // Build Slack Block Kit payload
    const blocks = [
      {
        type: "header",
        text: {
          type: "plain_text",
          text: `📝 ${title}`,
          emoji: true,
        },
      },
      {
        type: "section",
        text: {
          type: "mrkdwn",
          text: `*Posted by:* ${createdBy}${typeLabel}\n*Created:* ${formattedDate}`,
        },
      },
      {
        type: "actions",
        elements: [
          {
            type: "button",
            text: {
              type: "plain_text",
              text: "View Notes in Notion",
              emoji: true,
            },
            url: pageUrl,
            style: "primary",
          },
        ],
      },
      {
        type: "divider",
      },
    ];

    // Return blocks for the next Slack step to consume
    return { blocks, title, createdBy, formattedDate, pageUrl };
  },
});

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

Add the Slack 'Send Message' action

Click '+' below the code step and add a new step. Search for 'Slack' and select the action 'Send Message to a Channel.' Connect your Slack workspace via Connected Accounts — you'll need a Slack app with 'chat:write' scope or the standard Pipedream Slack OAuth app. In the 'Channel' field, type the exact channel name where meeting notes should be posted, such as '#product-updates'. For the message body, you'll pass the Block Kit blocks from the previous step.

1. 1Click '+' below the code step
2. 2Search 'Slack' and select 'Send Message to a Channel'
3. 3Click 'Connect a new Slack account' and authorize via OAuth
4. 4Set the 'Channel' field to your target channel name, e.g. '#product-updates'
5. 5Set 'Blocks' to reference the code step output: '{{steps.Format_Slack_Message.$return_value.blocks}}'

Workflow Canvas > Test Workflow button (top toolbar)

Test the full workflow end-to-end

Click 'Test Workflow' at the top of the canvas. Pipedream will run the trigger's test event through every step in sequence. Watch each step turn green as it passes. Check your target Slack channel — you should see the formatted message appear within a few seconds. If any step shows a red error badge, click it to read the error message in the output panel.

1. 1Click 'Test Workflow' in the top toolbar
2. 2Watch each step block — they should turn green in sequence
3. 3Open Slack and navigate to your target channel
4. 4Confirm the meeting notes message appears with the correct title and link

Workflow Canvas > Settings (gear icon) > Error Handling

Add an error notification step

Add one more step after the Slack action: another Slack 'Send Message' action, but this time targeted at a private ops channel or your own DMs. Wrap the entire workflow's error path by clicking the 'Error' tab in the workflow settings — Pipedream lets you define a separate error workflow. Alternatively, add a try/catch in the code step so failures post a plain-text alert to a #workflow-errors channel instead of silently dying.

1. 1Click the gear icon in the top-right of the workflow canvas
2. 2Select 'Error Handling'
3. 3Set 'On error, trigger workflow' to a separate error-notification workflow, or
4. 4In the Node.js code step, wrap the main logic in a try/catch that calls $.send.http or a Slack message on failure

Workflow Canvas > Deploy button (top right)

Deploy and activate the workflow

Click 'Deploy' in the top-right of the canvas. Pipedream will activate the workflow and begin polling your Notion database on the schedule you set. The workflow status changes from 'Development' to 'Active' — you'll see this in your workflow list on the Pipedream dashboard. Create a test page in your Notion meeting notes database and wait up to 15 minutes (or 5 minutes if you set the shorter interval) for the Slack notification to appear.

1. 1Click the 'Deploy' button in the top-right corner
2. 2Confirm the modal asking you to deploy to production
3. 3Navigate to pipedream.com > Workflows and confirm status shows 'Active'
4. 4Create a new test page in your Notion database
5. 5Wait up to 15 minutes and confirm the Slack message arrives