Pabbly Connect Integration Setup
Connect Parsley to Pabbly Connect via webhooks to route leads, intent signals, and conversations to 1,000+ apps with affordable automation.
Connect Parsley to Pabbly Connect via webhooks to route leads, intent signals, and conversations to 1,000+ apps - at a fraction of the cost of other automation tools. This guide walks you through setup, available events, and practical workflow recipes.
Quick Setup
- In Pabbly Connect, create a new workflow with the Webhook trigger
- Copy the webhook URL Pabbly generates for you
- In Parsley, go to Hub > API Keys and create a new webhook subscription
- Paste the Pabbly URL, pick the events you want to receive, and save
- Send a test event from Parsley so Pabbly can capture sample data
- Add an action step in Pabbly and map the Parsley fields
Events now flow from Parsley to your chosen app automatically.
Prerequisites
- A Pabbly Connect account - Pabbly offers lifetime deals and affordable plans. Sign up at pabbly.com/connect if you don't have one.
- A Parsley account - The Profile Viewed event is available on all plans. Business events (conversations, leads, scores, signals) require a Business plan.
- Access to Hub > API Keys in your Parsley dashboard, where you'll create the webhook subscription.
Step 1: Create a Pabbly Workflow with the Webhook Trigger
From your Pabbly Connect dashboard:
- Click Create Workflow
- Name it (e.g. "Parsley Hot Leads to Slack")
- In the trigger application search, select Webhook by Pabbly
- Choose the Catch Webhook trigger event
- Pabbly will display a unique webhook URL - copy it to your 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 Pabbly 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 Pabbly, if your workflow 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 a Business plan.
| 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 workflows.
Step 4: Capture Sample Data in Pabbly
Pabbly's Webhook trigger needs to receive at least one real event before you can map fields in your workflow:
- Back in Pabbly, the Webhook trigger should be showing a "waiting for webhook response" state
- 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 - Pabbly will receive the event and display the payload structure
- You can now reference Parsley fields in subsequent action steps
Step 5: Data Fields
Each event sends a specific set of fields to Pabbly Connect. Use these to map data into your action step.
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: Workflow Recipes
Here are practical examples to get you started with Pabbly Connect.
Slack notification on profile view (Free)
Trigger: Webhook (subscribed to Profile Viewed in Parsley) Action: Slack - Send Channel Message
Map the fields to post a message like: "Your profile was just viewed by a visitor from LinkedIn (referrer: linkedin.com/in/janesmith)"
Great for real-time awareness of who is checking out your profile after outreach.
Google Sheets row for captured leads (Business)
Trigger: Webhook (subscribed to Lead Captured in Parsley) Action: Google Sheets - Add Row
Map data.leadName, data.leadEmail, data.source, and createdAt to columns in your spreadsheet.
Useful for building a lightweight lead list without a full CRM.
Email alert for Hot leads (Business)
Trigger: Webhook (subscribed to Lead Scored in Parsley) Action: Gmail - Send Email (with Pabbly filter)
Add a Pabbly Filter step: only continue when data.leadQuality equals hot. Then send yourself an email with the lead details and MEDDIC signal breakdown.
Never miss a high-intent prospect.
CRM contact creation (Business)
Trigger: Webhook (subscribed to Lead Captured in Parsley) Action: Any CRM (Pipedrive, Zoho, Copper, etc.) - Create Contact
Map data.leadName and data.leadEmail to your CRM's contact fields. Works with any CRM that Pabbly supports - useful if your CRM doesn't have a native Parsley integration.
Notion database entry for conversations (Business)
Trigger: Webhook (subscribed to Conversation Completed in Parsley) Action: Notion - Create Database Item
Map data.profileUsername, data.messageCount, data.topics, and data.duration to a Notion database. Build a searchable log of every chatbot conversation for your team to review.
Create a deal when pain is identified (Business)
Trigger: Webhook (subscribed to Signal Detected in Parsley) Action: Any CRM - Create Deal (with Pabbly filter)
- Add a Pabbly Filter step: only continue when
data.signalTypeequalsidentifyPain - Map the prospect details and set the deal name to include the signal type
- Optionally add a Slack notification as a second action to alert the sales channel
Auto-create pipeline opportunities from real buying signals - no manual data entry.
Why Pabbly Connect?
Pabbly Connect is a cost-effective automation platform that offers lifetime deals and flat-rate pricing - no per-task charges like other platforms. If you are building automations that fire frequently (e.g. every profile view triggers a Slack message), Pabbly keeps costs predictable.
Parsley supports both Pabbly Connect and Zapier. Zapier offers a native Parsley app in its directory, while Pabbly uses its generic Webhook trigger - both deliver the same 5 events with identical data fields.
Troubleshooting
Pabbly is not receiving events
- Verify your webhook subscription in Parsley (Hub > API Keys) is marked as active
- Check that the Pabbly 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 Pabbly workflow is active and not paused
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 Pabbly workflow active?
- Is Pabbly returning a 2xx response?
- Check Pabbly's task history for error details
Business events unavailable
The Conversation Completed, Lead Captured, Lead Scored, and Signal Detected events require a Business plan. The Profile Viewed event works on all plans.
Missing fields in Pabbly
- Ensure you triggered at least one real event so Pabbly could capture the payload structure
- If a field shows as empty, it means that field was not present in the event payload (e.g. no referrer URL if the visitor navigated directly)
- Use the webhook test feature in Parsley to generate complete sample data
What's Next
- See all Parsley integrations - CRM and automation options
- Learn more about Pabbly Connect + Parsley - marketing overview
- Compare with Zapier integration - same events, native app in Zapier directory
- Manage your API keys and webhooks - create, revoke, and monitor usage
Questions? Contact us or email peter@parsley.id.
