n8n

Automate on your terms. Connect Quackback to your n8n instance to trigger workflows when feedback is submitted, statuses change, or comments are added. Keep your automation pipelines on infrastructure you control.

Note: On Quackback Cloud, integrations are available on the Business and Enterprise plans. Self-hosted installs include every integration.

Overview

The n8n integration enables:

• Trigger workflows: trigger n8n workflows when feedback is submitted, statuses change, or comments are added
• Automation you control: keep your automation pipelines on your own n8n instance

Prerequisites

• The Owner or Admin role in Quackback
• An n8n instance (self-hosted or n8n cloud)
• A webhook node set up in n8n

Setup

1. Create a webhook in n8n

1. Open n8n and create a new workflow
2. Add a Webhook node as the trigger
3. Set the HTTP method to POST
4. Copy the webhook URL (production URL, not the test URL)

Tip: Use the production webhook URL from n8n, not the test URL. The test URL only works when n8n is in listening mode, while the production URL works whenever the workflow is active.

2. Connect in Quackback

1. Go to Admin > Settings > Integrations > n8n
2. Paste the n8n webhook URL into n8n Webhook URL. It must start with https://.
3. Click Save

When you connect, Quackback sends a test request to the URL. If n8n does not return a success status, Quackback shows the HTTP status so you can fix the URL or the workflow.

3. Configure events

Choose which events trigger your n8n workflow:

4. Test the connection

1. Activate your n8n workflow
2. Submit test feedback in Quackback
3. Check the n8n execution history to verify the webhook was received
4. Use the received data to configure the rest of your workflow

Payload format

Quackback sends a JSON payload to your n8n webhook. Each payload has an event name (for example post.created), a timestamp, and the portal_url. It includes a post object with the id, title, board, URL, and author's name and email. Status changes add a status_change object with the previous and new status. Comments add a comment object. Use n8n's expression editor to map fields to downstream nodes.

Example workflows

Feedback to a database

1. Trigger: Quackback webhook (new post)
2. Action: Postgres/MySQL node > Insert row
3. Map fields: title, description, author email, board name

Slack alert for bug reports

1. Trigger: Quackback webhook (new post)
2. Filter: IF node checking board name equals "Bug Reports"
3. Action: Slack node > Send message

Sync to Airtable

1. Trigger: Quackback webhook (all events)
2. Action: Airtable node > Create/Update record
3. Map fields and use the event type to determine the action

Manage the integration

Pause

Temporarily stop sending events:

1. Go to Admin > Settings > Integrations > n8n
2. Turn off Webhook enabled
3. Events stop, but the webhook URL is preserved

Disconnect

To fully remove the integration:

1. Go to Admin > Settings > Integrations > n8n
2. Click Disconnect
3. Confirm the action

Note: Disconnecting in Quackback does not affect your n8n workflow. You can deactivate or delete it separately in n8n.

Troubleshooting

Events not arriving in n8n

1. Check integration status: look for errors in Quackback settings
2. Verify webhook URL: ensure the URL is HTTPS
3. Check workflow status: ensure the n8n workflow is active (not just saved)
4. Check n8n logs: review execution history for errors

Using a test URL

If you pasted the n8n test URL (contains /webhook-test/), events will only arrive when n8n is in listening mode. Switch to the production URL (contains /webhook/) for reliable delivery.

Self-hosted n8n not reachable

Your n8n instance must be reachable from the internet for Quackback to send webhooks. If n8n runs behind a firewall, expose the webhook endpoint through a reverse proxy or tunnel.

Related articles

• Make: Make automation integration
• Zapier: Zapier automation integration
• Webhooks: Build custom integrations
• Integrations overview: All integrations