Question 1

How do I trigger a NoClick workflow from an external app?

Accepted Answer

Add a Webhook trigger to your workflow and NoClick generates a unique URL for it. Configure the external app to send an HTTP request to that URL, and the workflow runs each time a request arrives. The request body, headers, and query parameters become available to the nodes that follow.

Question 2

Where do I find the webhook URL?

Accepted Answer

The URL is shown directly on the Webhook trigger node and is copyable with one click. It is generated automatically when you add the node, so there is nothing to register or configure by hand.

Question 3

Can I secure the webhook so only trusted requests run the workflow?

Accepted Answer

Yes. Set a secret on the trigger and NoClick verifies each incoming request using an HMAC-SHA256 signature. Requests without a valid signature are rejected, so only the system that knows the secret can start the workflow. If you leave the secret empty, no verification is performed.

Question 4

What data does the webhook pass into the workflow?

Accepted Answer

Downstream nodes can read the HTTP request body along with its headers and query parameters. That lets you branch, transform, or store the payload exactly as it was sent by the calling application.

Question 5

When should I use a webhook instead of a schedule?

Accepted Answer

Use a webhook when the workflow should respond to an event the moment it happens, such as a new order or a code push. Choose a schedule instead when the workflow simply needs to run at fixed times regardless of outside events.

Webhook Integration

What you can automate with Webhook

Webhook Operations

Execute

Frequently asked questions

Ready to build with Webhook?