Appearance
n8n integration
n8n is the escape hatch. When a system is not in this catalogue and you do not want to wait for it, an n8n workflow bridges the gap and a playbook step calls it.
What the n8n integration does
| Behaviour | Detail |
|---|---|
| Trigger | A playbook step calls an n8n workflow by its webhook path |
| Payload | Any structured data the playbook has built so far |
| Response | The workflow's response is parsed and available to later steps |
| Timeout | Configurable, thirty seconds by default |
| Failure handling | A failed workflow fails the step, and the playbook's own pause rules apply |
The step targets a Taufinity-operated n8n instance, hosted in the EU. The host is fixed in the step, which is deliberate: no user input decides where a playbook sends its data. Workflows are set up with you rather than by you.
If you already run your own n8n, do not use this step. Use the webhooks integration and point it at your own URL, held as a credential.
What the n8n integration can be used for
n8n can be used for connecting tools not yet in the catalogue, from CRM systems to accounting packages to internal APIs.
n8n can be used for multi-step glue logic that does not belong in a content playbook, keeping the playbook readable.
n8n can be used for staged rollouts of a new integration, proving the flow in a workflow before it is worth building natively.
n8n can be used for fan-out to several systems at once from a single playbook step.
n8n can be used as a queue in front of a slow or rate-limited system, so the playbook is not the thing waiting.
n8n combined with other integrations
| Combination | What it gives you |
|---|---|
| n8n + playbooks | A content or business workflow that reaches systems Studio does not speak natively |
| n8n + webhooks | Inbound and outbound in one loop: a tool calls Studio, Studio calls back through n8n |
| n8n + Slack | Custom routing and escalation logic before a message reaches a channel |
| n8n + company brain | An external system enriched with an answer grounded in your own documents |
Frequently asked
Can I point it at my own n8n instance? Not from this step. Use the webhooks integration for that, which accepts any URL and stores the credential for you.
Where does the managed instance run? In the EU, on Taufinity infrastructure, under the same data governance as the rest of the platform.
Can I add custom nodes? Talk to us. It is an operated instance, so a node that one workflow needs is a conversation rather than a self-service toggle.
What if my workflow takes minutes? Raise the timeout, or have the workflow acknowledge immediately and call Studio back through a share link when it finishes.