Send webhook

Quin can send an HTTP POST request to any external URL using the Send Webhook tool. This lets you push data from Quin into internal systems, automation platforms like Zapier or Make, or any other service that accepts webhook requests, without needing a separate integration connection.

This tool is general-purpose and works independently of Quin's other integrations. You provide the destination URL and the data to send, and Quin handles the request.

Before you begin

You need the webhook URL from the destination service. Most platforms, including Zapier and Make, generate this URL when you set up a webhook trigger on their end.

How to set it up

1. Decide where you want to use the Send Webhook tool. Most people add it to a workflow so the URL and parameters are already defined and Quin doesn't need them spelled out every time.
2. In your workflow instructions, tell Quin to send a webhook and include the following details.
   • URL - The full destination address, starting with http:// or https://
   • Body - The data you want to send, usually formatted as JSON
   • Content type (optional) - JSON is used by default. You can also specify application/x-www-form-urlencoded, application/xml, or text/plain
   • Headers (optional) - Any custom headers the destination requires, such as an authorization token or API key
3. Save your workflow.

You can also ask Quin to send a webhook directly in chat for a one-off request, but providing the URL and parameters each time is more work than setting it up once in a workflow.

What to expect

When triggered, Quin sends an HTTP POST request to the URL you provided with the data included in the request body. Quin validates the URL and protocol before sending, and the request times out after 30 seconds by default, or up to 60 seconds if you specify a longer timeout. If the destination returns a server error, Quin retries the request up to five times with backoff before giving up. Quin returns a success status, the HTTP status code, and the response from the destination, or an error message if the request didn't go through.

How it works

The Send Webhook tool doesn't require a connected integration. Quin sends requests directly to whatever URL you provide, which makes it a flexible way to connect Quin to any service that accepts webhook requests, whether that's an automation platform like Zapier or Make, an internal system, or your own API endpoint. Quin defaults to sending requests as JSON with a standard user agent, but you can adjust the content type and headers to match what the destination expects.

Troubleshooting

The webhook isn't reaching the destination

• Confirm the URL is correct and starts with http:// or https://
• Check that the destination service is expecting a POST request, not a GET or another method
• Verify the destination URL is still active, especially if it was generated by a temporary or single-use trigger on the receiving platform

The destination receives the request but rejects it

• Check whether the destination requires specific headers, like an API key or authorization token, and confirm they're included
• Confirm the content type matches what the destination expects, such as JSON or form-urlencoded
• Review the body of the data being sent to make sure it matches the format the destination requires

The request times out

• If your destination takes longer than 30 seconds to respond, specify a longer timeout up to 60 seconds
• Check whether the destination service itself is experiencing delays or downtime

Quin keeps asking for the URL or parameters

• Add the Send Webhook instructions to a workflow instead of asking in chat each time, so the URL and parameters are already defined