Back to Integrations
Trigger

Custom Webhook

The Custom Webhook node allows your workflow to listen for incoming HTTP requests. It instantly triggers your automation sequence the moment a third-party application, server, or custom script sends data to your unique nLink Webhook URL.

Custom Webhook
Core / Trigger
⚠️

What can you do with Custom Webhook?

Instant Execution

Unlike scheduled triggers, Webhooks run in real-time. Your workflow initiates instantly within milliseconds of receiving data, ensuring instantaneous reactions to customer actions.

Universal SaaS Compatibility

Connect natively with any modern SaaS application (like Shopify, Stripe, GitHub, Jira, or Facebook Lead Ads) that supports pushing webhooks or HTTP callbacks to an external URL.

Automatic Payload Parsing

nLink will automatically intercept and parse incoming JSON, form-data, or raw text payloads, instantly converting them into manageable dynamic variables for subsequent routing.

Detailed Usage & Configuration

The Custom Webhook node acts as the universal entry gate for external systems seamlessly feeding data into your nLink automation architecture continuously.

1. Receiving Data Streams

When initialized on the canvas, the system allocates a unique HTTP URL endpoint strictly for this node.

You can configure the Node to listen to any standard HTTP verbs:

  • GET: Commonly used natively by URL callbacks and simple notifications.
  • POST: Ideal for heavy analytical payloads, database entries, and form submissions.
  • ANY: A catch-all net, parsing whatever format external 3rd-party SaaS integrations send.

2. Securing Your Influx (HMAC Validation)

If you're exposing your webhook to high-stakes applications (like financial systems or public clients), you should never rely on obscurity.

The Webhook node natively supports HMAC Signature Security directly integrated. To enable:

  1. Select "HMAC Signature" from the payload security configuration dropdown.
  2. Provide the expected hashing algorithm (SHA-256, SHA-1, MD-5) used by the sender.
  3. Define the exact Header Name (e.g., x-hub-signature-256) and insert your encrypted Secret Token.

The node will autonomously reject any unauthenticated requests instantly, stopping bad actors before they execute any internal workflow logic.

🛡️ Production Requirement: This node only actively triggers in production environments when the workflow is explicitly in the Published state. To successfully publish your workflow to the live execution server, nLink strictly requires the presence of a valid Trigger Node (such as this Webhook node) to ensure the graph can be actively invoked.