Integration: Webhooks

DataMerge Webhooks: The Cleanest Enrichment Payload in B2B Data

Integration webhooks send a clean JSON payload per record. Just the enriched fields, no metadata wrapper. Pipe data directly into your CRM, database, or automation tool without writing a transformer.

Get 20 Free Credits

Two Types of Webhooks

Per-Request Webhooks

Include a webhook_url in your API request. When enrichment completes, the full API response is sent to that URL. This includes metadata like id, success status, endpoint, request parameters, result wrapper, and credits consumed.

Best for: debugging, logging, or when you need the full response context.

Integration Webhooks (Recommended)

Set up a webhook as an integration in the DataMerge app. These send a clean, minimal payload per record with only the enriched entity fields. No wrapper, no metadata, no noise.

Best for: production workflows, CRM syncs, and any system where you want to use the data directly.

Integration Webhook Payload

An integration webhook payload contains exactly three things: object_type, record_id, and the enriched entity fields. Nothing else.

Company payload example

{
  "object_type": "company",
  "record_id": "abc123",
  "legal_name": "Stripe, Inc.",
  "display_name": "Stripe",
  "domain": "stripe.com",
  "industry": "Financial Technology",
  "employee_count": 8000,
  "country": "United States",
  "city": "San Francisco",
  "parent_company": null,
  "ultimate_parent": null
}

Contact payload example

{
  "object_type": "contact",
  "record_id": "def456",
  "full_name": "Jane Smith",
  "email": "jane.smith@stripe.com",
  "email_verified": true,
  "mobile": "+1-555-123-4567",
  "job_title": "VP of Sales",
  "seniority": "VP",
  "department": "Sales"
}

Why the Clean Payload Matters

Most enrichment APIs wrap their webhook payloads in layers of metadata. You get an outer object with id, status, request echo, result wrapper, and the actual data buried inside. Before you can use the data, you need to write transformation logic to extract it.

DataMerge integration webhooks skip all of that. The payload IS the data. You can pipe it directly into:

A CRM's create/update endpoint
A database insert statement
A Make or Pipedream workflow
An n8n webhook trigger
Any custom HTTP endpoint

No transformation code. No JSON path extraction. Just the fields you need, ready to use.

How to Set Up an Integration Webhook

Open the DataMerge app and go to Integrations
Click Add Integration and select Webhook
Enter your webhook URL (this is where DataMerge will POST the clean payload)
Optionally set it as your default integration
Run an enrichment. The clean payload is sent to your URL for every enriched record.

Tools That Work Well with the Webhook

Any tool that can receive an HTTP POST with a JSON body works with DataMerge webhooks. These are especially popular:

Make (Integromat) via webhook trigger module
Pipedream via webhook trigger
n8n via webhook node
Custom HTTP endpoints (Node.js, Python, Go, etc.)
Serverless functions (AWS Lambda, Cloudflare Workers, Vercel)

Frequently Asked Questions

What's the difference between per-request and integration webhooks?

Per-request webhooks are URLs you include in individual API requests. They receive the full API response including metadata. Integration webhooks are configured once in the DataMerge app and receive a clean payload with only the enriched entity fields. Integration webhooks are recommended for most use cases.

What fields are included in the integration webhook payload?

The payload contains object_type (e.g. "company" or "contact"), record_id, and all enriched entity fields such as legal name, display name, domain, industry, employee count, address, hierarchy data, and more. The exact fields depend on the enrichment type.

What fields are NOT included?

Integration webhook payloads do not include id, success, endpoint, request, result, or credits_consumed. These metadata fields are stripped so the payload contains only the data you need.

Can I receive webhooks in Make or Pipedream?

Yes. Set up a webhook trigger in Make or Pipedream and use that URL as your integration webhook in the DataMerge app. The clean payload format works directly with both platforms without transformation.