n8n
Add a deck to your workflow.
Use the Encelade community node to generate decks from CRM records, form responses, or research. Run it on a schedule, an event, or on demand.
Quickstart
Drop in the node
Add the Encelade node from n8n's community nodes, create an Encelade credential with your API key, and pick an operation. Generation, run status, and project CRUD are all available as node operations.
- Install from Settings → Community Nodes
- Bearer-token credential, self-host base URL supported
- Generate, run status, cancel, get, update, and delete operations
- Chain with any of n8n's 500+ integrations
Settings → Community Nodes → Install
npm package: n8n-nodes-encelade
Credential: Encelade API
API Key: YOUR_API_KEY
Base URL: https://www.encelade.ai (default)
Node: Encelade
Resource: Presentation
Operation: Generate
Brief: {{ $json.title }}: {{ $json.notes }}How it works
From source material to shareable link.
- 01
Install the node
In n8n, go to Settings → Community Nodes and install n8n-nodes-encelade. Self-hosted and cloud instances are both supported.
- 02
Add the credential
Create an Encelade API credential with your API key. The node tests it against your account before saving.
- 03
Build the workflow
Trigger → data → Encelade node → deliver. Drop the node after any trigger, map your data into the Generate operation, then route the returned share link to email, Slack, or storage.
Check the run, then send
The Generate operation returns a run you can poll with the Generation Run → Get operation. Add a wait-and-check loop before the step that sends the deck, so downstream nodes only fire once the presentation is ready.
Use cases
Workflows people automate
Drop the Encelade node after any trigger and turn the data passing through it into a deck. These are the patterns the node is built for.
- Meeting transcript → deck
- Pipe a transcript from your meeting tool into the Generate operation and get a shareable recap deck the moment the call ends.
- CSV / spreadsheet → deck
- Read rows from Google Sheets, Airtable, or a CSV file and hand them to Encelade in the brief to produce a data-backed presentation.
- Scheduled report → deck
- Trigger on a cron schedule, gather the week's metrics, and route the finished deck to email or Slack — a fresh report with no manual work.
Why the node
Native node vs. raw HTTP
You can call the REST API from n8n's HTTP Request node, but the community node removes the boilerplate.
| Capability | n8n-nodes-encelade node | HTTP Request + REST API |
|---|---|---|
| Setup | Install once from Community Nodes; the operation appears in the node picker. | Build and maintain each request, header, and URL by hand. |
| Auth | One Encelade credential, reused across every node and workflow. | Paste the bearer token into each HTTP node or wire up a generic credential. |
| Async generation | A typed Generation Run → Get operation for Wait-node polling, plus an Encelade Trigger that fires the moment the deck is ready. | Hand-build a wait-and-check loop around /generation/runs/{id}, with no built-in completion trigger. |
| Typed fields | Brief, artifact type, and options are labeled inputs with inline help. | Assemble a raw JSON body and keep it in sync with the API by reading the docs. |
| Maintenance | Node updates track API changes; pin or upgrade per release. | You own every breaking change across every workflow that calls the API. |
Questions
n8n
& Encelade.
How do I install the Encelade node?
In n8n, open Settings → Community Nodes, install n8n-nodes-encelade, then add an Encelade API credential with your API key. It works on both n8n Cloud and self-hosted instances.
Can I generate decks on a schedule?
Yes. Put a Schedule (cron) trigger before the Encelade node and it generates on the cadence you set — daily or weekly reports build and deliver themselves with no manual work.
What data sources work?
Anything n8n can read across its 500+ integrations: CRM records, Google Sheets, Airtable, CSV files, form responses, scraped pages, and meeting transcripts. Map that data into the Generate operation.
Do I need code?
No. The native node exposes typed fields — brief, artifact type, and options — so there's no HTTP gluing or JSON body to assemble. Drop it in and map your data.
Is there a ready-made template?
Yes. The GitHub repo ships an importable example workflow (examples/generate-deck.json) that shows the trigger → generate → poll → deliver pattern end to end.