Make.com Integration

Connect PepoSmart to 1,000+ apps with Make.com (formerly Integromat). Build visual automation scenarios that trigger on bookings, meeting notes, follow-up emails, and AI-extracted action items. Create powerful multi-step workflows with Make's intuitive drag-and-drop interface.

Webhook-Based Integration

PepoSmart sends real-time webhook notifications to your Make.com "Custom webhook" trigger. Events are pushed instantly when they occur - no polling or scheduled runs required.

Prerequisites

  • A PepoSmart account
  • A Make.com account (Free or paid plan)
  • Basic understanding of Make.com scenarios

Connecting Make.com

Step 1: Create a Scenario in Make

  1. Log in to your Make.com account at make.com
  2. Click Create a new scenario
  3. Click the + button to add a module
  4. Search for "Webhooks"
  5. Select "Custom webhook" as your trigger

Step 2: Create and Copy the Webhook URL

  1. Click Add to create a new webhook
  2. Give it a name like "PepoSmart Events"
  3. Click Save
  4. Copy the generated webhook URL (looks like: https://hook.us1.make.com/...)

Step 3: Connect in PepoSmart

  1. Log in to your PepoSmart account at app.peposmart.com
  2. Go to Integrations in the sidebar
  3. Find the Make.com card
  4. Paste your webhook URL in the input field
  5. Click Connect to Make.com

Success!

PepoSmart is now connected to Make.com. All events will be sent to your webhook URL automatically when they occur.

Step 4: Determine Data Structure in Make

  1. Back in Make.com, click Run once on your scenario
  2. Create a test booking in PepoSmart to send sample data
  3. Make.com will receive and parse the webhook data automatically
  4. Click OK to confirm the data structure
  5. Continue adding modules to build your automation

Available Triggers

PepoSmart sends webhook notifications for the following events. All events are sent to the same webhook URL - use Make's Router module to handle different events with different actions.

Booking Events

booking.created

Triggers when someone books a meeting with you

Includes: attendee info, event details, time, location, meeting URL
booking.cancelled

Triggers when a booking is cancelled

Includes: original booking details, cancellation timestamp
booking.rescheduled

Triggers when a booking is rescheduled to a new time

Includes: original and new times, attendee info

Meeting Notes Events (AI Features)

meeting-notes.completedNew

Triggers when AI meeting notes, transcript, and analysis are ready

Includes: transcript, summary, sentiment, buyer intent, topics, action items, recording URL
action-item.createdNew

Triggers when AI extracts an action item from a meeting

Includes: type, description, owner, priority, context

Follow-up Email Events

followup-draft.generatedNew

Triggers when AI generates a follow-up email draft

Includes: draft content, action type, meeting analysis
followup-draft.sentNew

Triggers when a follow-up email is sent

Includes: recipient, subject, sent timestamp

Webhook Payload Format

All events are sent as POST requests with the following JSON structure:

{
  "event": "booking.created",
  "timestamp": "2024-01-15T10:30:00.000Z",
  "data": {
    "bookingId": "abc123",
    "eventId": "event456",
    "attendee": {
      "email": "[email protected]",
      "firstName": "John",
      "lastName": "Doe",
      "phone": "+1234567890",
      "company": "Acme Inc"
    },
    "startTime": "2024-01-20T14:00:00.000Z",
    "endTime": "2024-01-20T14:30:00.000Z",
    "timezone": "America/New_York",
    "location": "google-meet",
    "meetingUrl": "https://meet.google.com/abc-defg-hij",
    "eventDetails": {
      "title": "Discovery Call",
      "description": "30-minute introductory call",
      "duration": 30
    }
  }
}

Meeting Notes Completed Payload

{
  "event": "meeting-notes.completed",
  "timestamp": "2024-01-15T15:30:00.000Z",
  "data": {
    "bookingId": "abc123",
    "eventId": "event456",
    "attendee": {
      "email": "[email protected]",
      "name": "John Doe"
    },
    "meetingDate": "2024-01-15T14:00:00.000Z",
    "eventTitle": "Discovery Call",
    "transcript": "Full meeting transcript text...",
    "summary": "AI-generated meeting summary...",
    "analysis": {
      "sentiment": "positive",
      "buyerIntent": "high",
      "topics": ["pricing", "timeline", "implementation"]
    },
    "actionItems": [
      {
        "type": "SEND_PRICING",
        "description": "Send pricing breakdown for enterprise plan",
        "owner": "host",
        "priority": "high"
      }
    ],
    "recordingUrl": "https://recordings.peposmart.com/..."
  }
}

Action Item Types

When AI analyzes your meeting transcripts, it identifies specific action items with predefined types. Use these types in Make.com filters to route different actions:

TypeDescription
SEND_PRICINGHost promised to send pricing or quotes
SEND_PROPOSALHost promised to send a formal proposal
SEND_DEMO_LINKHost promised to send demo or trial access
SCHEDULE_FOLLOWUPNeed to schedule another meeting
SEND_RESOURCESHost promised to send documents or links
ANSWER_QUESTIONHost needs to answer a specific question
GENERAL_FOLLOWUPStandard thank you follow-up
INTERNAL_TASKInternal task (not for invitee)

Using Router to Handle Different Events

Since all events go to the same webhook URL, use Make.com's Router module to create different paths for different event types:

Router Setup

  1. 1. After your webhook trigger, add a Router module
  2. 2. Create a new route for each event type you want to handle
  3. 3. Add a filter to each route: event equals booking.created
  4. 4. Connect your action modules to the appropriate routes

Example Scenarios

Sales Pipeline Automation

When meeting notes are ready with high buyer intent, create a deal in your CRM

meeting-notes.completedHubSpot / Salesforce / Pipedrive

Task Management

Create tasks for each action item extracted from meetings

action-item.createdAsana / Trello / Monday.com

Team Notifications

Send messages when follow-up emails are sent to prospects

followup-draft.sentSlack / Microsoft Teams

Meeting Intelligence

Log meeting transcripts and summaries to databases

meeting-notes.completedGoogle Sheets / Airtable / Notion

Multi-Step Workflow

Chain multiple actions: when a booking is created, update CRM, send Slack notification, and create a calendar follow-up reminder - all in one scenario

booking.createdCRM + Slack + Google Calendar

Disconnecting Make.com

  1. Go to Integrations in PepoSmart
  2. Find the Make.com card
  3. Click Disconnect
  4. Confirm the disconnection

Before Disconnecting

Your Make.com scenarios will stop receiving data from PepoSmart. Remember to also turn off the affected scenarios in Make.com to avoid errors.

Troubleshooting

Webhook Not Receiving Data

  • Verify the webhook URL is correctly pasted in PepoSmart
  • Check that the integration shows as "Connected" in PepoSmart
  • Ensure your scenario is turned ON in Make.com
  • Test by creating a new booking - it should trigger immediately
  • Check Make.com's execution history for any errors

Missing Meeting Notes Events

  • Meeting notes events require the AI Meeting Notes feature to be enabled
  • Ensure the meeting bot joined and recorded the meeting
  • Events are sent after the meeting ends and AI processing completes

Data Structure Issues

  • Click "Run once" and trigger a test event to refresh the data structure
  • Make.com may need to re-determine the data structure after updates
  • Delete and recreate the webhook if structure doesn't update

Support & Contact

Need help with your Make.com integration?

Email Support

For technical issues and questions

[email protected]

Make.com Help

For Make.com-specific issues

Make.com Help Center

Additional Resources


Last updated: January 2026. This documentation covers the PepoSmart Make.com webhook integration.