Make (Integromat)
LiveWebhookAutomation
Overview
Build powerful, multi-step automations with Make (formerly Integromat). ClearView sends real-time webhook events to your Make scenarios, letting you orchestrate complex workflows across hundreds of apps. Route data, transform payloads, branch on conditions, and connect to tools like Google Sheets, Slack, HubSpot, Salesforce, and more with Make's visual scenario builder.
What Gets Synced
- Full company profiles - Name, domain, industry, size, revenue, and location
- Lead scoring data - Score, grade, and status for each identified visitor
- Visitor engagement - Session count, page views, and engagement timeline
Supported Events
| Event | Description |
|---|---|
company.identified | Fires when a new company is identified visiting your site |
lead.hot | Fires when a visitor is classified as a hot lead |
visitor.returning | Fires when a previously identified company returns to your site |
Prerequisites
- A Make account (free tier includes 1,000 operations/month)
- ClearView tracking script installed on your site
Setup Guide
Create a new scenario in Make
Log into Make and click "Create a new scenario". This opens the visual scenario builder.
Add a Custom Webhook module
Click the "+" icon to add a module. Search for "Webhooks" and select "Custom webhook". Click "Add" to create a new webhook and give it a name like "ClearView Events".
Copy the webhook URL
Make will generate a unique webhook URL. Click "Copy address to clipboard" to grab it.
Webhook URL format
https://hook.make.com/xxxxxxxxxxxxxxxxxxxxConfigure in ClearView
Go to ClearView Dashboard > Integrations > Make. Paste the webhook URL into the webhookUrl field and select your desired events.
Determine the data structure
Click the Test button in ClearView, then go back to Make and click "Redetermine data structure". Make will parse the sample payload and auto-create the data structure for your scenario.
Build your scenario
Add action modules after the webhook trigger. Use routers to branch logic, filters to conditionally process events, and any of Make's 1,000+ app modules as destinations.
Configuration Fields
| Field | Type | Description |
|---|---|---|
webhookUrl | URL | Your Make Custom Webhook URL. Generated when you create a webhook module in your scenario. |
Data Mapping
| ClearView Field | Webhook Path | Type |
|---|---|---|
| Company Name | company.name | string |
| Domain | company.domain | string |
| Industry | company.industry | string |
| Employee Count | company.employees | number |
| Lead Score | lead.score | number |
| Lead Grade | lead.grade | string |
| Event Type | event.type | string |
| Page URL | event.pageUrl | string |
| Timestamp | event.timestamp | ISO 8601 |
| Visitor Country | visitor.country | string |
Example Payload
The webhook delivers the same structured payload for all events:
{ "event": { "type": "company.identified", "timestamp": "2026-03-25T14:32:00.000Z", "pageUrl": "https://yoursite.com/pricing" }, "company": { "id": "comp_abc123", "name": "Acme Corp", "domain": "acme.com", "industry": "Technology", "employees": 250, "annualRevenue": "$10M-$50M", "city": "San Francisco", "state": "CA", "country": "US" }, "lead": { "score": 87, "grade": "A", "status": "hot" }, "visitor": { "sessionCount": 3, "pageViews": 12, "firstSeen": "2026-03-20T08:15:00.000Z", "lastSeen": "2026-03-25T14:32:00.000Z", "country": "US", "city": "San Francisco" }}Use Make routers for event-based branching
event.type to send company.identified events to your CRM and lead.hot events to Slack.Troubleshooting
Scenario not running
Check that your scenario is active (toggled on) in Make. Inactive scenarios will not process incoming webhooks. Also verify the webhook URL in ClearView matches the one shown in your Make module.
Data structure not recognized
If Make cannot parse the webhook data, click "Redetermine data structure" on the webhook module and send a fresh test event from ClearView. This regenerates the field mapping.
Operations quota exceeded
Free Make accounts have a 1,000 operations/month limit. Each module in your scenario counts as one operation per execution. Simplify scenarios or upgrade your plan for high-traffic sites.