n8n and Conduyt
Conduyt has its own n8n node, n8n-nodes-conduyt. A Conduyt event such as a new contact, a won deal, a submitted form or an incoming message can start a workflow, and the node can create, read and update contacts, companies, deals and tasks, add notes and tags, and send a contact an SMS or email. n8n approved it as a verified node on October 6, 2026. It is pending the next n8n release, and until then it installs as a community node by package name.
What makes it different
Conduyt events start workflows
The Conduyt Trigger registers a webhook in your Conduyt account when the workflow is activated and removes it when the workflow is deactivated. Pick one or more events, for example contact.created, deal.won, form.submitted, message.received or appointment.booked.
One node for your CRM records
Contacts, companies, deals, tasks, notes, messages and tags each have their own operations in the Conduyt node, including contact search by email or text, Add Tags on a contact, and deal creation with pipeline and stage pickers.
Send SMS or email to a contact
Message, then Send texts or emails a contact through Conduyt. Every item gets its own idempotency key, so Retry On Fail and a manual retry of a failed execution resend the same request under the same key.
Signed deliveries
Each delivery is verified against the X-Conduyt-Signature HMAC header, using the secret Conduyt returns when the webhook is created. The payload carries the event, the account ID, a timestamp and the record that changed.
What you need in place first
What moves, and which way
| Direction | What moves | Notes |
|---|---|---|
| Conduyt to n8n | Trigger deliveries for the events you pick, shaped as event, accountId, timestamp and data, where data is the record that changed. | Each delivery is verified against the X-Conduyt-Signature HMAC header. |
| n8n to Conduyt | Creates and updates for contacts, companies, deals and tasks; notes on a contact or deal; tags; and SMS or email to a contact. | Operations as listed in the n8n-nodes-conduyt 0.1.6 README on npm, checked October 6, 2026. |
| Conduyt to n8n | Reads: Get and Get Many for contacts, companies, deals and tasks, contact search by email or text, notes, messages and tags. | Reads use the same API key and stay within its scopes. |
| n8n to Conduyt | Webhook registration when a workflow with the Conduyt Trigger is activated, and removal when it is deactivated. | Conduyt returns the signing secret when the webhook is created. |
4 steps, about ten minutes
Create a Conduyt API key
In Conduyt, open Settings, then API and Webhooks, and create a key with the scopes you need: contacts, companies, deals, tasks, notes, messages and tags, plus webhooks for the trigger.
Add the Conduyt node
On n8n Cloud, search for Conduyt on the canvas and drag the node into your workflow. On self-hosted n8n, an Owner or Admin opens Settings, then Community Nodes, selects Install, enters the package name n8n-nodes-conduyt and confirms.
Add the credentials
In n8n, create Conduyt API credentials and paste the key. Leave Base URL as https://conduyt.app/api/v1 unless you run Conduyt on a custom domain.
Build the workflow
Add the Conduyt Trigger to start from a Conduyt event, or the Conduyt node to read and write records, then activate the workflow. Activation registers the webhook in Conduyt and deactivation removes it.
n8n verified n8n-nodes-conduyt and published it on n8n Cloud on October 7, 2026. A dedicated page in the n8n integrations directory follows on the n8n schedule. New npm versions are picked up by n8n after a review.
What it does not do
The details
Common questions
Is Conduyt a verified node in n8n?
Yes. n8n verified n8n-nodes-conduyt and published it on n8n Cloud on October 7, 2026, so it can be added straight from the canvas. Self-hosted instances can still install it by package name.
How do I install the Conduyt node today?
On n8n Cloud, search for Conduyt on the canvas and add the node; if it does not appear, enable Verified Community Nodes in the Admin Panel. On self-hosted n8n, an Owner or Admin opens Settings, then Community Nodes, selects Install and enters n8n-nodes-conduyt. Then create Conduyt API credentials in n8n and paste your API key.
Which API key scopes does the node need?
Only the ones your workflow uses: contacts, companies, deals, tasks, notes, messages and tags, plus webhooks for the Conduyt Trigger. Keys start with cdy_ and are created in Conduyt under Settings, then API and Webhooks.
Can a retry send the same message twice?
Message, then Send gives each item its own idempotency key, so a retry in the same saved run resends the same request under the same key. An email retry within 24 hours never sends twice. An SMS whose delivery could not be confirmed is flagged deliveryUnconfirmed and not retried by the node, but a worker crash before n8n saves the run can allow a second send.
What does the trigger send to n8n?
Each delivery carries the event, the account ID, a timestamp and the record that changed, and is verified against the X-Conduyt-Signature HMAC header using the secret Conduyt returns when the webhook is created.
Ready to try Conduyt?
20-day free trial. No credit card required.