Make Integration Setup
Connect Parsley to Make (formerly Integromat) via webhooks to route leads, intent signals, and conversations into 1,500+ apps with visual scenarios.
Connect Parsley to Make (formerly Integromat) via webhooks to route leads, intent signals, and conversations into 1,500+ apps using Make's visual scenario builder. This guide walks you through setup, available events, and practical scenario recipes.
Quick Setup
- In Make, create a new scenario with the Custom webhook trigger
- Copy the webhook URL Make generates for you
- In Parsley, go to Hub > API Keys and create a new webhook subscription
- Paste the Make URL, pick the events you want to receive, and save
- Send a test event from Parsley so Make can capture sample data
- Add a module after the webhook in Make and map the Parsley fields
Events now flow from Parsley into your Make scenario automatically.
Prerequisites
- A Make account - Make offers a generous free tier (1,000 operations/month) and affordable paid plans. Sign up at make.com if you don't have one.
- A Parsley account - The Profile Viewed event is available on all plans. The four high-signal events (conversations, leads, scores, signals) require conversation balance. View pricing.
- Access to Hub > API Keys in your Parsley dashboard, where you'll create the webhook subscription.
Step 1: Create a Make Scenario with the Custom Webhook Trigger
From your Make dashboard:
- Click Create a new scenario
- Click the large + button in the canvas to add the first module
- Search for Webhooks and select it
- Choose Custom webhook as the trigger
- Click Add to create a new webhook, give it a name (e.g. "Parsley Hot Leads"), and click Save
- Make will display a unique webhook URL - click Copy address to clipboard
You will paste this URL into Parsley in the next step.
Step 2: Create a Webhook Subscription in Parsley
From your Parsley dashboard:
- Go to Hub in the left sidebar
- Click API Keys
- Scroll to the Webhooks section
- Click Create Webhook
- Paste the Make webhook URL into the URL field
- Select which events you want to subscribe to (see Step 3 below)
- Click Create
Parsley will generate a signing secret you can use to verify incoming webhooks in Make, if your scenario needs to validate request authenticity.
Step 3: Choose Your Events
Parsley fires 5 webhook events. The Profile Viewed event is available on all plans. The remaining four require conversation balance.
| Event | Description | Plan |
|---|---|---|
| Profile Viewed | Someone views your Parsley profile | Free |
| Conversation Completed | A chatbot conversation ends on your profile | Business |
| Lead Captured | A visitor shares their contact details via chatbot or form | Business |
| Lead Scored | A lead receives a Hot, Warm, or Cold quality score | Business |
| Signal Detected | A MEDDIC buying signal is identified during conversation | Business |
You can subscribe to multiple events with a single webhook, or create separate webhooks for different scenarios.
Step 4: Capture Sample Data in Make
Make's Custom webhook trigger needs to receive at least one real event before you can map fields in your scenario:
- Back in Make, the Custom webhook module should be in a "Listening" state - if not, click Re-determine data structure
- Trigger an event in Parsley - for example, view your own profile (for
profile.viewed) or use the webhook test feature in Hub > API Keys to send a test payload - Make will receive the event, automatically detect the payload structure, and confirm with "Successfully determined"
- You can now reference Parsley fields in subsequent modules
Step 5: Data Fields
Each event sends a specific set of fields to Make. Use these to map data into your action modules.
Profile Viewed
| Field | Description | Example |
|---|---|---|
id | Event ID | evt_abc123 |
type | Event type | profile.viewed |
createdAt | Timestamp (ISO 8601) | 2026-03-20T14:30:00Z |
data.profileUserId | Your Parsley user ID | user_abc123 |
data.profileUsername | Your Parsley username | janesmith |
data.visitorId | Unique visitor identifier | vis_def456 |
data.source | Traffic source | linkedin |
data.referer | Full referrer URL | https://www.linkedin.com/in/janesmith |
Conversation Completed
| Field | Description | Example |
|---|---|---|
id | Event ID | evt_abc123 |
type | Event type | chatbot.conversation.completed |
createdAt | Timestamp (ISO 8601) | 2026-03-20T14:30:00Z |
data.conversationId | Conversation ID | conv_abc123 |
data.profileUserId | Your Parsley user ID | user_abc123 |
data.profileUsername | Your Parsley username | janesmith |
data.visitorId | Unique visitor identifier | vis_def456 |
data.messageCount | Total messages exchanged | 8 |
data.topics | Topics discussed (array) | ["pricing", "enterprise features"] |
data.duration | Duration in seconds | 245 |
Lead Captured
| Field | Description | Example |
|---|---|---|
id | Event ID | evt_abc123 |
type | Event type | lead.captured |
createdAt | Timestamp (ISO 8601) | 2026-03-20T14:30:00Z |
data.conversationId | Conversation ID | conv_abc123 |
data.profileUserId | Your Parsley user ID | user_abc123 |
data.profileUsername | Your Parsley username | janesmith |
data.visitorId | Unique visitor identifier | vis_def456 |
data.leadEmail | Lead's email address | buyer@acmecorp.com |
data.leadName | Lead's name | Alex Johnson |
data.source | Capture source | chatbot |
Lead Scored
| Field | Description | Example |
|---|---|---|
id | Event ID | evt_abc123 |
type | Event type | lead.scored |
createdAt | Timestamp (ISO 8601) | 2026-03-20T14:30:00Z |
data.conversationId | Conversation ID | conv_abc123 |
data.profileUserId | Your Parsley user ID | user_abc123 |
data.profileUsername | Your Parsley username | janesmith |
data.visitorId | Unique visitor identifier | vis_def456 |
data.leadQuality | Lead temperature | hot |
data.intentScore | Intent score (1-5) | 5 |
data.intentSignal | Intent classification | high_intent |
data.meddic.metrics | Metrics signal detected | true |
data.meddic.economicBuyer | Economic Buyer detected | true |
data.meddic.decisionCriteria | Decision Criteria detected | true |
data.meddic.decisionProcess | Decision Process detected | false |
data.meddic.identifyPain | Identify Pain detected | true |
data.meddic.champion | Champion detected | false |
Signal Detected
| Field | Description | Example |
|---|---|---|
id | Event ID | evt_abc123 |
type | Event type | signal.detected |
createdAt | Timestamp (ISO 8601) | 2026-03-20T14:30:00Z |
data.conversationId | Conversation ID | conv_abc123 |
data.profileUserId | Your Parsley user ID | user_abc123 |
data.profileUsername | Your Parsley username | janesmith |
data.visitorId | Unique visitor identifier | vis_def456 |
data.signalType | MEDDIC signal type | identifyPain |
data.quote | Verbatim quote from conversation | "We are losing deals because..." |
data.confidence | Confidence level | high |
Step 6: Scenario Recipes
Here are practical examples to get you started with Make.
Google Sheets log of every lead (Business)
Trigger: Custom webhook (subscribed to Lead Captured in Parsley) Action: Google Sheets - Add a Row
Map data.leadName, data.leadEmail, data.source, and createdAt to columns in your spreadsheet. A lightweight lead list with no CRM required.
Slack ping when a Hot lead appears (Business)
Trigger: Custom webhook (subscribed to Lead Scored in Parsley) Action: Slack - Create a Message
Add a Make Filter between the webhook and Slack: only continue when data.leadQuality equals hot. Your sales channel hears about every Hot lead in real time.
Profile-view alert from a specific source (Free)
Trigger: Custom webhook (subscribed to Profile Viewed in Parsley) Action: Email - Send an Email
Add a Filter: only continue when data.source contains linkedin. Get notified whenever someone you sent an InMail to actually opens your profile.
Auto-create a Notion page for each conversation (Business)
Trigger: Custom webhook (subscribed to Conversation Completed in Parsley) Action: Notion - Create a Database Item
Map data.profileUsername, data.messageCount, data.topics, and data.duration into a Notion database. Build a searchable conversation log without leaving your team's existing workspace.
Branch on MEDDIC signal type (Business)
Trigger: Custom webhook (subscribed to Signal Detected in Parsley) Action: Make Router - branches per signal type
Use Make's Router module to fork on data.signalType. Send identifyPain signals to your CRM as new deals, send champion signals to a "Warm Champions" Google Sheet, and send everything else to a Slack thread for review.
Multi-step lead enrichment (Business)
Trigger: Custom webhook (subscribed to Lead Captured in Parsley) Actions: HTTP module → CRM module
- Use Make's HTTP module to call a free enrichment API (Clearbit, Apollo, or similar) with
data.leadEmail - Pipe the enriched company data plus the original Parsley lead into your CRM (HubSpot, Pipedrive, Zoho - whichever you use)
Give your reps a fully enriched contact record before they ever pick up the phone.
Why Make?
Make's visual canvas is the easiest way to prototype multi-step automations without code. Operations-based pricing (rather than per-task) makes it cost-effective for high-volume Parsley users firing many profile.viewed events. The free tier handles most solo workflows.
Parsley supports Make alongside Zapier, Pabbly Connect, and n8n - all four deliver the same 5 events with identical data fields. Pick whichever automation tool your team already uses.
Troubleshooting
Make is not receiving events
- Verify your webhook subscription in Parsley (Hub > API Keys) is marked as active
- Check that the Make webhook URL was copied correctly (no trailing spaces)
- Use the webhook test feature in Parsley to send a sample payload
- Check the Parsley webhook delivery log for failed attempts
- Confirm your Make scenario is turned on (toggle in the bottom-left of the editor)
Webhook delivery failing
Parsley retries webhook deliveries up to 3 times with exponential backoff (1 second, 5 seconds, 30 seconds). If all attempts fail, check:
- Is your Make scenario active?
- Is Make returning a 2xx response?
- Check Make's execution history for error details
Business events unavailable
The Conversation Completed, Lead Captured, Lead Scored, and Signal Detected events require conversation balance. View pricing. The Profile Viewed event works on all plans.
Missing fields in Make
- Ensure you triggered at least one real event so Make could detect the payload structure
- If a field shows as empty, that field was not present in the event payload (e.g. no referrer URL if the visitor navigated directly)
- Click Re-determine data structure on the webhook module after sending fresh sample data
What's Next
- See all Parsley integrations - CRM and automation options
- Compare with Pabbly Connect - cheaper alternative for high-volume flat-rate use
- Compare with Zapier - native app in the Zapier directory
- Compare with n8n - self-hosted, dev-friendly automation
- Manage your API keys and webhooks - create, revoke, and monitor usage
Questions? Contact us or email peter@parsley.id.
