> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nrev.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Listen to Webhook Node

> Trigger your workflows instantly when new data arrives — perfect for real-time lead capture, alerts, and event-driven automation.

## What It Does

* Instantly triggers a workflow when a webhook sends data
* Captures incoming payloads from forms, CRMs, or tools like HubSpot,etc.
* Converts webhook content into clean, usable table columns
* Keeps your RevOps data live, synced, and ready to act on

***

## 🏁 Getting Started

<Frame>
  <img src="https://mintcdn.com/nurturev/mHCimB8YAP--VMGj/images/Listen%20to%20Webhook%20Node%20config%20screenshot.png?fit=max&auto=format&n=mHCimB8YAP--VMGj&q=85&s=71b56dc7f4e578012211382da4b3cded" alt="Listen to Webhook Node config screenshot" style={{ borderRadius: '0.5rem', width: '100%', margin: '1.5rem 0' }} width="1178" height="1664" data-path="images/Listen to Webhook Node config screenshot.png" />
</Frame>

<Steps>
  <Step title="Add the node">Drag **Listen to Webhook** into your workflow as the first step.</Step>
  <Step title="Copy the webhook URL">Each node generates a unique URL automatically — copy it from the config panel.</Step>
  <Step title="Send test data">Use any tool or form to send a webhook POST to that URL to verify your setup.</Step>
</Steps>

***

## Inputs

### 🛠️ Required Fields

* **Webhook URL (✅)**\
  Automatically generated by Nrev when you add the node.\
  *Why it matters:* This is your connection point — any tool that can send a webhook can trigger your workflow instantly.

### 🎯 Optional Fields

* **Source Name (⚪️)**\
  Label the webhook’s origin (e.g., “HubSpot”, “Web Form”, “Zapier”).\
  *Why it matters:* Makes it easier to filter, group, or audit incoming data later.

***

## Output

When the webhook fires, the node adds new columns to your dataset:

| Column                | Description                                             |
| --------------------- | ------------------------------------------------------- |
| `webhook_received_at` | Timestamp when the webhook was received                 |
| `webhook_source`      | The tool or system that sent the webhook                |
| `webhook_event_type`  | Type of event (if available)                            |
| `data_*`              | Flattened data columns created from the webhook payload |

<Note>
  ✨ If your table already includes these column names, Nrev automatically renames them (e.g., `data_user_id_1`).
</Note>

***

## How It Works

1. A webhook call hits your unique node URL
2. The node captures and timestamps the payload
3. Structured data is flattened into columns with `data_` prefixes
4. Nested or complex objects are stored as JSON strings
5. The workflow continues automatically using the received data

***

## 🚀 Example Use Cases & Prompts

| Use Case                  | Setup Example                                              |
| ------------------------- | ---------------------------------------------------------- |
| Capture new demo requests | Send form data directly from Typeform or HubSpot Forms     |
| Sync CRM updates          | Trigger when a new lead or deal is created                 |
| Process event alerts      | Fire workflow when product usage or intent data is updated |
| Route inbound leads       | Use webhook data to match and assign in real time          |

***

## ✨ Pro Tips

<Tip>
  * Use clear **Source Names** for tracking where leads come from
  * Test with a sample payload before going live to confirm column structure
  * Chain this node with **Enrichment** or **Scoring** nodes for instant lead qualification
</Tip>

***

## ⚠️ Important Considerations

<Warning>
  * Very large or deeply nested payloads may appear as JSON strings under `data_` columns
  * If no payload arrives, the workflow won’t start — always test once during setup
  * Ensure your webhook sender supports HTTPS for security and reliability
</Warning>

***

## 🛠 Troubleshooting & Gotchas

| Symptom                        | Likely Cause                  | Quick Fix                             |
| ------------------------------ | ----------------------------- | ------------------------------------- |
| Workflow doesn’t trigger       | No data reaching the webhook  | Test with a simple JSON payload       |
| Missing columns                | Payload missing expected keys | Check that your tool sends all fields |
| Duplicate columns (`_1`, `_2`) | Column name conflict          | Rename output or adjust mapping       |

***

## 📝 FAQ

<AccordionGroup>
  <Accordion title="Can I use multiple webhook nodes?">
    ✅ Yes — each node has its own unique URL. You can listen to multiple tools or events in one workflow.
  </Accordion>

  <Accordion title="Can I preview what data came in?">
    Yes — use **Test Mode** to send sample data and preview your flattened columns before going live.
  </Accordion>

  <Accordion title="What happens with nested data?">
    Complex objects are converted to JSON strings and stored as `data_metadata` or similar fields.
  </Accordion>
</AccordionGroup>

***

## 💰 Pricing

| Mode             | Credits / Run |
| ---------------- | ------------- |
| Trigger received | **1 credit**  |

<Note>
  Each webhook trigger costs **1 credit**. Downstream nodes consume additional credits as usual.
</Note>

***

<p style={{ fontSize: '1rem', fontWeight: 'bold', marginTop: '1.5rem' }}>
  Drop this node into your flow to automate real-time actions from any tool that can send a webhook — your pipeline just got faster. 🚀
</p>