Description
n8n-nodes-slide-synquic
An n8n community node package for Slide by Synquic. It gives n8n two nodes: a Slide Trigger that starts a workflow in real time when something happens in your Slide account (a contact is created, a WhatsApp or Instagram message arrives, an email is opened, a voice call completes, a task is created or completed, a Shopify order is placed), and a Slide action node that sends messages across WhatsApp, SMS, RCS, Email, and Instagram reads or upserts contacts, and creates, updates, completes and comments on CRM tasks. Triggers are webhook-based, not polled: activating a workflow subscribes an endpoint, deactivating it removes the subscription.
Installation · Credentials · Nodes · How it works · Compatibility
Installation
Follow the community nodes installation guide and enter the package name:
n8n-nodes-slide-synquic
On a self-hosted instance you can instead install it into your n8n custom nodes directory:
npm install n8n-nodes-slide-synquic
What it provides
| Node | Type | Credential | What it does |
|—|—|—|—|
| Slide Trigger (slideTrigger) | Trigger (webhook, POST) | Slide API (slideApi) | Starts a workflow on one or more Slide account events. |
| Slide (slide) | Action | Slide API (slideApi) | Sends messages and manages contacts, tasks and task boards. |
Slide, resources and operations
| Resource | Operation | What it does |
|—|—|—|
| Message | Send | Sends over a chosen channel (WhatsApp, SMS, RCS, Email, Instagram) with optional ordered fallback to another phone-based channel. |
| Message | Send WhatsApp Template | Sends an approved WhatsApp template, with positional body variables and URL or copy-code button variables. |
| Message | Send Email | Sends a transactional email from one of your templates, with template variables, subject override and reply-to. |
| Message | Send SMS | Sends an SMS from a registered sender id, with optional DLT template id and transactional or promotional route. |
| Contact | Search | Finds contacts in your contact list, with a result limit. Search By picks how: any field (name, phone or email contains the text), or an exact email or phone to find one person. |
| Contact | Create or Update | Creates a contact in your contact list, or updates the one that matches. Enter an email, a phone number, or both: a contact is matched by phone first, then by email. Also takes first and last name, company and tags. |
| Task | Create | Creates a task, or a subtask. Title, then optional description, board, stage, priority, assignee, linked contact, start and due date, labels. Without a board it goes on your default board, in the board’s default stage. |
| Task | Get | Gets one task with its subtasks and files. |
| Task | Get Many | Gets tasks, with Return All or a Limit. Filters: board, stage, stage type (To Do, In Progress, Done, Cancelled), assignee (or Unassigned), priority, labels, linked contact, due after and before, overdue only, search text, include subtasks, and the sort. |
| Task | Update | Changes the fields you set. A blank field is never sent, so it never clears a value; list a field under Clear Fields to empty it (assignee, contact, description, start date, due date, labels). Choosing another board moves the task and its subtasks. |
| Task | Complete | Marks a task done (the board’s first done stage), or with Done off reopens it (the board’s default open stage). |
| Task | Delete | Deletes a task with its subtasks, comments and files. Returns how many tasks were deleted. |
| Task | Add Comment | Adds a comment to a task. In the task’s history it shows as written via the API. |
| Task | Get Comments | Gets a task’s comments, oldest first, with Return All or a Limit. |
| Task Board | Get Many | Gets every board with its stages and open task count. |
| Task Board | Get | Gets one board with its stages and members. |
| Task Board | Create | Creates a board from a template (General, Marketing, Software), with an optional description, colour, visibility (Workspace or Private) and members. A name already used by another board is refused. |
Contacts are your contact list. Search and Create or Update both work on the Contacts page of your Slide dashboard, so a contact the node creates is one the node can find. Create or Update returns the contact with created (true for a new contact, false for an update). Tags are added and never removed, a blank field never clears a value, and nothing here changes an unsubscribe. A new contact counts toward your plan’s contact limit. When two workflow runs write the same person at the same moment, Slide can ask for one of them to be sent again: the node does that once by itself, and never repeats a message send.
Tasks are your CRM tasks. The Task and Task Board operations work on the boards of your Slide dashboard, and a task the node creates appears there. An API key acts for the whole workspace, so it sees and changes every board, private ones included. Changes made through the node show in a task’s history as made via the API. Board, stage and assignee are picked from lists loaded live from your account (a stage belongs to one board, so choose the board first to see only its stages), and each also accepts an expression. Dates are ISO 8601: a date without a time (2026-11-20) is midnight UTC, so send a full timestamp with its time zone for a precise time. A task or a comment is never sent twice by the node itself, so a failed Create is safe to look at before you run it again.
Template pickers (email templates, WhatsApp templates) and the SMS sender picker are loaded live from your account, so you select a real template rather than typing an id and discovering the typo at run time. Each also accepts an expression if you need a dynamic value.
Slide Trigger, events and options
The event list is fetched live from your account when you open the node, so events added to Slide later appear without you updating the package. One trigger node can listen to several events at once. Available events include contact created, contact updated, contact lifecycle stage changed, form submitted, inbound WhatsApp, Instagram and SMS messages, WhatsApp message status, completed voice calls, email delivered, opened, clicked, bounced and complained, and task created, updated, completed and deleted, task comments, and Shopify order created and fulfilled.
| Option | Default | Effect |
|—|—|—|
| Verify Signature | on | Rejects deliveries whose HMAC signature does not match. Your webhook URL is not a secret, so this is what stops anyone who learns it from injecting events into your workflow. |
| Raw Payload | off | Emits the full envelope (id, type, createdAt, accountId, livemode, data) instead of flattening the event data to the top level. |
| Include Test Deliveries | on | Runs the workflow for test deliveries sent from the Slide dashboard. Turn off in production so only real account activity triggers it. |
With the default (flattened) output, the event data is spread to the top level and eventId, eventType, occurredAt, accountId, and livemode are added on top, so a payload field named id can never shadow the event id you would use for idempotency downstream.
Credentials
Create an API key in your Slide dashboard under Admin, API Keys, then add a Slide API credential in n8n.
| Field | Notes |
|—|—|
| API Key | Your Slide API key. Stored as a password field and sent as a Bearer token on every request. |
| Base URL | Defaults to the Slide production API. Change it only when pointing at a self-hosted or staging instance. |
The credential’s Test button calls the webhook event catalogue, so it doubles as a scope check: a key that cannot read the catalogue is useless for every trigger in this package, and failing at save time is kinder than a trigger that saves cleanly and never fires.
Required scopes:
| Use | Scope |
|—|—|
| Any trigger | webhooks:read, webhooks:write |
| Send / Send WhatsApp Template | whatsapp:send |
| Send Email | email:send |
| Send SMS | sms:send |
| Contact search | contacts:read |
| Contact create or update | contacts:write |
| Task and Task Board Get, Get Many, Get Comments | tasks:read |
| Task Create, Update, Complete, Add Comment, Task Board Create | tasks:write |
| Task Delete | tasks:delete |
The permissions of an API key cannot be edited. If your key was created before contacts:write existed (for example a key that only has the email list permission), Create or Update is refused until you create a new key that has contacts:write and put it in the credential. The same goes for the task permissions. The node says so in plain words, naming the permission, when that happens.
How it works
Requests. Every call goes through one helper that builds the URL from the credential’s base URL; the Authorization: Bearer header is injected by the credential itself, so it cannot be forgotten by a new request. API errors are wrapped as n8n node errors so the Slide message (for example a missing scope) is shown in the UI instead of a bare status code. The action node honours Continue On Fail, emitting an error item for the failing input row and carrying on with the rest.
Subscription lifecycle. Activating a workflow creates a webhook endpoint on your account pointing at the n8n webhook URL, and stores the returned id and signing secret in the workflow’s static data. The signing secret is returned exactly once at creation, so that is the only moment it can be captured. Before creating, n8n checks whether the stored endpoint still exists and still points at the current webhook URL, so a workflow moved to a new host resubscribes rather than sitting silently attached to a stale URL. Deactivating deletes the endpoint (an already-deleted endpoint is treated as success) and clears the stored id and secret.
Signature verification. Deliveries carry an X-Slide-Signature header holding a timestamp (t=) and one or more HMAC-SHA256 digests (v1=, more than one during a secret rotation). The node computes the HMAC over 401 and never reaches the workflow.
Project layout
| Path | What lives there |
|—|—|
| nodes/Slide/Slide.node.ts | The action node: properties, option loaders, and execute. |
| nodes/Slide/TaskDescription.ts | The Task and Task Board operations and fields. |
| nodes/Slide/TaskFunctions.ts | The requests the Task and Task Board operations send, and their board, stage and assignee pickers. |
| nodes/Slide/SlideTrigger.node.ts | The trigger node: webhook lifecycle and the delivery handler. |
| nodes/Slide/GenericFunctions.ts | Shared API request helper, option loaders, and signature verification. |
| nodes/Slide/*.node.json | Codex metadata (categories, aliases, documentation links). |
| nodes/Slide/slide.svg, slide.dark.svg | Node icons, light and dark variants. |
| credentials/SlideApi.credentials.ts | The Slide API credential, its auth injection and its test request. |
| scripts/copy-icons.js | Validates and copies icons and codex metadata into dist/. |
| test/ | Signature verification tests and their vectors, and the contact and task operation tests. |
| .github/workflows/publish.yml | The npm release workflow. |
Development
npm install
npm run build # tsc, then validate and copy icons and codex metadata into dist/
npm run dev # tsc --watch
npm run lint # eslint-plugin-n8n-nodes-base, n8n's own ruleset
npm run lintfix
npm test # node --test test/*.test.js
npm run build is more than tsc: n8n resolves icons relative to the compiled node file, so scripts/copy-icons.js copies icons and *.node.json into dist/ and refuses to build if an SVG is malformed or the codex metadata uses an unsupported field or an unrecognised category.
Release
prepublishOnly runs build, lint, and test, so a broken package cannot be published by hand. Publishing itself happens in GitHub Actions (.github/workflows/publish.yml), triggered by pushing a v* tag or by running the workflow manually:
npm version patch && git push && git push --tags
The workflow installs with --ignore-scripts, builds, lints, tests, verifies that the tag matches the version in package.json, and publishes with npm provenance using trusted publishing (OIDC), so there is no long-lived npm token stored as a secret. n8n requires community nodes to be published from CI with provenance in order to be verified, which is why local publishing is not used.
Compatibility
Built against the n8n nodes API version 1 and tested against n8n-workflow 1.82. n8n-workflow is a peer dependency supplied by the n8n instance that loads the package.
