n8n-nodes-conduyt
Community node for Conduyt CRM in n8n. Create and update contacts, companies, deals, tasks and notes, send SMS or email to a contact, and start workflows from CRM events with a webhook trigger.
Installation · Credentials · Operations · Trigger · Compatibility · Resources
Installation
Follow the community nodes installation guide. Package name: n8n-nodes-conduyt.
Credentials
- In Conduyt, open Settings > API & Webhooks and create an API key (it starts with
cdy_). Give it the scopes you need: contacts, companies, deals, tasks, notes, messages, tags, and webhooks for the trigger.
- 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.
Operations
| Resource | Operations |
|---|
| Contact | Create, Get, Get Many, Search (by email or text), Update, Add Tags |
| Company | Create, Get, Get Many, Update |
| Deal | Create (with pipeline and stage pickers), Get, Get Many, Update |
| Task | Create, Get, Get Many, Update |
| Note | Create (on a contact or deal), Get Many |
| Message | Send (SMS or email to a contact), Get Many |
| Tag | Create, Get Many |
Tags on Create / Update Contact must already exist in your account. Custom fields are passed as a JSON object.
Message > Send gives every item its own idempotency key and keeps the evaluated request with it, so Retry On Fail and a manual Retry of a failed execution resend the same request under the same key rather than resend a request Conduyt already confirmed. An SMS whose delivery Conduyt could not confirm is reported on the item instead, flagged deliveryUnconfirmed, and is never retried by this node within the same saved run; the provider may already have delivered it, and you decide whether to send it again. That protection lives only in the run n8n saves after the report: if the worker crashes before n8n saves it, the retry has no record of the report, and Conduyt still allows another dispatch under the same key, caller-supplied or generated, so it can be sent again. Check the conversation (or your own log) before retrying a Message > Send node you cannot rule a crash out of. For email Conduyt keeps the key for 24 hours: a retry within 24 hours never sends twice, a retry after 24 hours sends the email again. Set Idempotency Key to supply your own, such as a record or event ID from the upstream item, sent exactly as given (SMS: 8 to 200 characters; email: up to 255): the key survives a worker crash between Conduyt accepting the request and n8n saving the run, which the generated key cannot, but the saved request snapshot does not survive that crash, so give the same key the same item data every time. Each key must belong to one item, with no leading or trailing whitespace; reusing it for a different item or node is rejected. Left empty, the node generates a key, snapshot included, for retries of the same execution.
Trigger
Conduyt Trigger registers a webhook in your Conduyt account when the workflow is activated and removes it when deactivated. Pick one or more events, for example contact.created, deal.won, form.submitted, message.received, appointment.booked. Deliveries are verified against the X-Conduyt-Signature HMAC header using the secret Conduyt returns when the webhook is created.
The payload is { event, accountId, timestamp, data } where data is the record that changed.
Compatibility
Built and tested with n8n 1.x (n8n-workflow 1.48+). Node.js 18 or newer.
Resources
License
MIT
