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
- Log in to your Make.com account at make.com
- Click Create a new scenario
- Click the + button to add a module
- Search for "Webhooks"
- Select "Custom webhook" as your trigger
Step 2: Create and Copy the Webhook URL
- Click Add to create a new webhook
- Give it a name like "PepoSmart Events"
- Click Save
- Copy the generated webhook URL (looks like:
https://hook.us1.make.com/...)
Step 3: Connect in PepoSmart
- Log in to your PepoSmart account at app.peposmart.com
- Go to Integrations in the sidebar
- Find the Make.com card
- Paste your webhook URL in the input field
- 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
- Back in Make.com, click Run once on your scenario
- Create a test booking in PepoSmart to send sample data
- Make.com will receive and parse the webhook data automatically
- Click OK to confirm the data structure
- 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
Triggers when someone books a meeting with you
Includes: attendee info, event details, time, location, meeting URLTriggers when a booking is cancelled
Includes: original booking details, cancellation timestampTriggers when a booking is rescheduled to a new time
Includes: original and new times, attendee infoMeeting Notes Events (AI Features)
Triggers when AI meeting notes, transcript, and analysis are ready
Includes: transcript, summary, sentiment, buyer intent, topics, action items, recording URLTriggers when AI extracts an action item from a meeting
Includes: type, description, owner, priority, contextFollow-up Email Events
Triggers when AI generates a follow-up email draft
Includes: draft content, action type, meeting analysisTriggers when a follow-up email is sent
Includes: recipient, subject, sent timestampWebhook 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:
| Type | Description |
|---|---|
| SEND_PRICING | Host promised to send pricing or quotes |
| SEND_PROPOSAL | Host promised to send a formal proposal |
| SEND_DEMO_LINK | Host promised to send demo or trial access |
| SCHEDULE_FOLLOWUP | Need to schedule another meeting |
| SEND_RESOURCES | Host promised to send documents or links |
| ANSWER_QUESTION | Host needs to answer a specific question |
| GENERAL_FOLLOWUP | Standard thank you follow-up |
| INTERNAL_TASK | Internal 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. After your webhook trigger, add a Router module
- 2. Create a new route for each event type you want to handle
- 3. Add a filter to each route:
eventequalsbooking.created - 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 / PipedriveTask Management
Create tasks for each action item extracted from meetings
action-item.createdAsana / Trello / Monday.comTeam Notifications
Send messages when follow-up emails are sent to prospects
followup-draft.sentSlack / Microsoft TeamsMeeting Intelligence
Log meeting transcripts and summaries to databases
meeting-notes.completedGoogle Sheets / Airtable / NotionMulti-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 CalendarDisconnecting Make.com
- Go to Integrations in PepoSmart
- Find the Make.com card
- Click Disconnect
- 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?
Additional Resources
- General Troubleshooting Guide
- Frequently Asked Questions
- Zapier Integration (alternative)
- Make.com Webhooks Documentation
Last updated: January 2026. This documentation covers the PepoSmart Make.com webhook integration.