discatch buddy, listeningdiscatch
Get a key

n8n-social-listening

n8n social listening

A catch fires a signed webhook that an n8n workflow receives, so you can route mentions through any n8n automation without writing code.

alertresult

What it does

  1. 1

    Step 1

    Create an n8n workflow that starts with a Webhook node. Copy the production webhook URL that n8n generates for the node. The test URL works for development; switch to the production URL before enabling the catch.
  2. 2

    Step 2

    Register a catch with the webhook destination type. Set the URL to the n8n webhook URL and provide a secret for payload signature verification.
  3. 3

    Step 3

    When the catch fires, discatch sends a signed POST to the n8n webhook URL. The body contains the results array, the suggested_action string, and the quote. The X-Discatch-Signature header carries the HMAC-SHA256 of the body using the secret you set.
  4. 4

    Step 4

    In n8n, parse the JSON body and route it through your workflow. Common downstream nodes: send a message to Slack, create a Notion page, add a row to Google Sheets, post to a CRM, or call another API. n8n handles the orchestration; discatch handles the monitoring.
  5. 5

    Step 5

    Verify the webhook signature in n8n to confirm the payload came from discatch. Use a Code node after the Webhook node to compute the HMAC-SHA256 and compare it with the header value. If they do not match, stop the workflow.
  6. 6

    Step 6

    This playbook ships as a SKILL.md in the dcouple/discatch-playbooks repo so skills.sh and agent skill directories pick it up.

Sources it watches

WWWWebNWSNewsHNHacker News

Common questions

Is there an official n8n node for discatch?

No. There is no native n8n node for discatch. This playbook uses the generic Webhook node that ships with every n8n installation. The webhook receives the standard discatch event payload, which is documented JSON that any HTTP handler can parse. No custom code is needed to receive the payload; only the signature verification step requires a Code node.

Can I use this with Make, Zapier, or another automation tool?

Yes. Any automation tool that accepts an incoming webhook works with the same pattern. The payload is the same signed JSON body regardless of the receiver. Replace the n8n webhook URL with the URL your tool provides. The signature verification step varies by tool but the HMAC-SHA256 algorithm is the same.

What happens if n8n is down when the catch fires?

Delivery retries five times over six hours with exponential backoff. After the last attempt the delivery goes to the dead letter log, visible at /v1/catches/{id}/deliveries. The catch keeps running and delivers normally on the next firing. You can also replay missed deliveries by reading the event log from an earlier cursor with GET /v1/events.

Can I add classify to the workflow?

Yes. Set classify to true on the catch. Each result in the payload will include a classification object with relevance, sentiment, and intent fields. Your n8n workflow can branch on these values: route complaints to one channel, questions to another, and comparisons to a third. This adds one classify unit per result to the cost.

How do I test the workflow before enabling the catch?

Use POST /v1/catches/{id}/test to send a sample payload to the n8n webhook URL. The sample has the same shape as a real delivery. In n8n, open the Webhook node’s test panel to see the incoming data and verify your downstream nodes handle it correctly.

What sources should I monitor?

Start with web, news, and hackernews for broad coverage of blogs, press, and developer discussion. Add discourse if your product has users on Discourse forums, and github if people mention you in issues and discussions. Each source is one entry in the sources array; adding a source does not add a separate catch.

Last reviewed by , founder, dcouple. Copy from docs/playbooks.md.