Package Information
Documentation
Syncon One for n8n
A community node package over the Syncon One public API (/api/v1). A workflow signs in with an
API key from Settings, API; what the key may read or write is decided by the API, not by the node.
What it offers
- Syncon One node, 10 resources and 50+ operations: Customer, Company, Lead and Deal (create,
update, get, get many, archive); Task (create, update, complete, delete, get many); Note (create,
update, delete, get, get many); Ticket (create, update, get, get many); Meeting (schedule, update,
cancel, delete, get, get many); Conversation, the live chat inbox (get many, get, get messages,
join, reply, hand back to AI, update, add and list internal notes); Teammate (get many). It can
be used as a tool by an n8n AI agent. - Syncon One Trigger node, instant, 19 events: New and Updated for customers, companies, leads
and deals; Deal Won, Lost and Stage Changed; New Conversation, Visitor Message Received and Human
Requested; Meeting Booked; New Task and Task Completed; New Note; Record Deleted.
The trigger subscribes a webhook when the workflow is activated and removes it when it is
deactivated. A delivery carries only ids, so the trigger reads the record with the credential's own
key: a record that key cannot see produces nothing. When n8n hands over the raw body, a delivery
whose signature does not verify is dropped. A workspace can hold 100 webhook subscriptions.
Owner, assignee, stage and pipeline are pick-lists loaded from your workspace. Scheduling a meeting
puts it on the owner's calendar and invites the attendees unless Notify is off. Replying in the
inbox needs a key with the live chat scopes, acts as the key's creator, and the conversation must be
joined first. Fields come from nodes/SynconOne/fields.json, built from the API's own OpenAPI
document. There is no credential test button on purpose: every endpoint needs a scope, so a good key
limited to other things would fail any one test call.
Work on it
cd integrations/n8n
npm install
npm test # the nodes against a stand-in API
npm run build # compiles to dist/ and copies the icon
cp ../zapier/generated/fields.json nodes/SynconOne/fields.json # after the fields are regenerated
Publish it
n8n community nodes are npm packages named n8n-nodes-* with the n8n-community-node-package
keyword (set). The package is public, carries the brand mark as its icon, and is published asn8n-nodes-syncon-one from the SynconAI npm account with npm publish (prepublishOnly builds and
tests first). A self-hosted n8n installs it from Settings, Community Nodes by that name. To appear in
n8n Cloud and its verified list, the package goes through n8n's own verification, which this package
has not been through.
The nodes are type-checked and tested against a stand-in API. They have not been loaded into a
running n8n; do that on a self-hosted n8n before relying on them.