Start with one real question and leave with a next step.
Start with the question in front of you, then use the guide to make the next decision easier.
Try saying
“I am trying to make this decision. What should I look at first?”
Start with context
Bring the smallest useful example.
Look for the signal
Separate what is known from what is assumed.
Take one step
Choose an action you can review.
n8n Integration
What this connection is for
Connect a self-hosted or cloud n8n workflow to Specky and automate the handoffs around product work.
How your data reaches Specky
It does not — n8n is outbound only. There is nothing to ingest and no sync. This connection is here so Specky can deliver an approved update through n8n.
Before you start
- n8n instance URL (Required) — The public HTTPS URL of your n8n instance, without /api/v1.
- n8n API key (optional) (Optional) — Add an API key to validate the instance and let Specky list workflows. Webhook-only mode does not require one.
- Workflow webhook URL (Required) — Use an n8n Webhook trigger URL from the workflow that should receive Specky events.
- Workflow ID (optional) (Optional) — Optional metadata used to identify the workflow in the integration card and event payloads.
Setup
Open Settings → Integrations, find n8n, and click Connect. The form will tell you what to paste and where to find it.
- Create a workflow with an n8n Webhook trigger and copy its production URL.
- Paste the n8n instance URL and the workflow webhook URL here.
- Add an n8n API key if you want Specky to validate the instance and list the workflow.
- Activate the workflow before sending production events.
Specky posts JSON to the workflow webhook for approved tickets and expert-panel reviews. It also provides a private Specky capture URL so another n8n workflow can send normalized feedback back as a graph signal.
After connecting
n8n appears wherever Specky sends stakeholder updates. It does not add anything to your Product Graph because it has nothing to read.
Troubleshooting
- Connected, but nothing appears. That's expected — n8n sends, it doesn't ingest.
- "Upgrade to connect". Your plan caps how many integrations you can connect at once, and a few providers are Scale-only. Settings → Usage shows where you stand.
- Credentials stopped working. Tokens expire and get revoked. Reconnect with a fresh one — your existing signals are kept.
See the n8n integration page for what it's for and the questions people usually ask first, or the Integrations Overview for how integrations work in general.
Ready to apply this?
Start with your own product and keep the first read grounded. You can create an account after you see the result.