Articles on: Integrations & automation

The n8n integration: automate SimplyPrint with self-hosted workflows

The n8n integration: automate SimplyPrint with self-hosted workflows


Automate your SimplyPrint print farm with n8n - a source-available workflow automation platform you can self-host. In this guide you'll learn how to install the SimplyPrint community node, connect your account, and build your first automation flow.


The n8n integration is included from the Pro plan and up.


Table of contents

  • What n8n is and why you might use it
  • Installing the SimplyPrint community node
  • Connecting your SimplyPrint account
  • Building your first workflow
  • Available triggers
  • Available actions
  • Custom API call
  • Troubleshooting


What n8n is and why you might use it

n8n is a source-available workflow automation tool - think Zapier, but you can self-host the whole engine on your own server. Because it's fair-code licensed, you can fork the source, run it on your own infrastructure, and keep all your workflow data inside your own network. That makes it a good fit for workshops, schools, bureaus and enterprises with data-residency or compliance needs.


With the SimplyPrint community node, you can trigger n8n workflows from events happening on your print farm (print finished, filament assigned, AI flags a failure, etc.) and call SimplyPrint actions (pause a print, add a file to the queue, send G-code) from any n8n workflow.


If you'd rather have a fully hosted, no-code option, see the Zapier integration. If you want open source with a visual builder, check the Activepieces integration.


Installing the SimplyPrint community node

You need an n8n instance (self-hosted or cloud) where you're a platform admin. The node is published on npm as @simplyprint/n8n-nodes-simplyprint, and you can browse it on the n8n integrations directory.


  1. Open n8n and go to Settings -> Community Nodes.
  2. Click Install a community node.
  3. Enter @simplyprint/n8n-nodes-simplyprint and click Install.
  4. Wait a few seconds for n8n to download and register the node. You may need to refresh the page.


If you're self-hosted, make sure N8N_COMMUNITY_PACKAGES_ENABLED=true is set (it's the default on recent n8n versions).


Connecting your SimplyPrint account

You can connect in one of two ways. OAuth2 is recommended for most setups - it's a one-click connect with nothing to copy. If you prefer a non-interactive setup (e.g. automated CI), use API key.


  1. In any workflow, add a SimplyPrint trigger or action.
  2. Under Credentials, click Create New.
  3. Select SimplyPrint OAuth2 API.
  4. Click Connect. You'll be redirected to SimplyPrint - sign in, pick the account, review the requested permissions, approve.
  5. If your n8n instance isn't one SimplyPrint has seen before (which is almost everyone on first use), the consent screen will show a warning with the callback URL your n8n is running at. Verify it matches your own n8n before ticking I trust this destination and approving.
  6. You're connected.


The token n8n receives is scoped to your user, and you can revoke it at any time by deleting the credential.


Option B: API key

  1. In SimplyPrint, click your avatar and open your account settings -> API (simplyprint.io/panel/user_settings/api). Click Generate token and copy the key.
  2. Your Company ID is shown on the same page, next to the example base URL.
  3. Back in n8n, click Create New credential, select SimplyPrint API.
  4. Paste the API key into API Key and the numeric Company ID into Company ID.
  5. Click Save.


Building your first workflow

As a quick example, let's post a message to Slack every time a print finishes.


  1. Create a new workflow in n8n.
  2. Click + to add a trigger. Search for SimplyPrint Trigger, add it, and pick Print Finished as the event.
  3. Pick your SimplyPrint credential.
  4. Click Listen for test event. In another tab, open your SimplyPrint panel and finish or cancel a print (or, on plans with the Webhooks feature, click Send test on the webhook row under Panel -> Settings -> Webhooks).
  5. You should see the event payload appear in n8n once it's delivered.
  6. Click + to add an action after the trigger. Search for Slack -> Post Message and pick the channel.
  7. Drag the fields you want (printer name, file name, duration) from the trigger output into the message text.
  8. Click Save and toggle the workflow Active. From now on, every print that completes will post to Slack.


Available triggers

The community node ships 60+ webhook-based triggers, one per SimplyPrint event:


  • Prints: print started, paused, resumed, finished, failed, cancelled, bed cleared, objects skipped
  • Queue: item added, approved, denied, pending approval, moved, revived, queue emptied
  • Filament: spool created, updated, assigned, unassigned
  • Printer state: material changed, nozzle size changed, tags assigned or removed, printer marked out of order, AutoPrint state changed
  • AI and maintenance: AI failure detected, false positives, maintenance jobs, schedules, tasks and problems
  • Account and school: spare part stock, quotas, balance and user signup events


Every trigger creates a dedicated per-workflow webhook on your SimplyPrint account when the workflow is activated, and removes it on deactivation. Every delivery is verified with a unique shared secret - forged events are silently dropped. These integration-created webhooks work on any plan that includes the integration - you don't need the manual webhook builder from the Print Farm plan.


Available actions

The main SimplyPrint node exposes over 30 operations grouped by resource:


  • Printer: list, get, pause, resume, cancel, send G-code
  • Print job: start a print from a file or queue item
  • Queue: list items, list groups, add item, update item, move item (including to top or bottom), remove, revive, empty, list pending approval, approve, deny
  • File: list, upload, move
  • Filament: list, get, assign to printer, unassign
  • Organization: get current user, get statistics, list print history, list tags
  • Custom field: list definitions, set values


Most actions expose dynamic dropdowns - pick from a live list of your printers, files, queue items, filaments, or tags without needing to copy IDs by hand.


Custom API call

If the wrapped operations don't cover what you need, use the Custom API Call resource. Pick an HTTP method, enter the endpoint path relative to your account (e.g. printers/Get), and optionally supply query params and a JSON body. The node handles authentication and the account prefix for you.


This is the escape hatch for any SimplyPrint endpoint the node doesn't wrap directly. The full API reference is at apidocs.simplyprint.io.


Troubleshooting

The SimplyPrint node doesn't appear after installing. If you're self-hosted, confirm N8N_COMMUNITY_PACKAGES_ENABLED=true and restart n8n. Refresh the browser.


OAuth redirect fails with "redirect URI mismatch" or similar. Your n8n callback URL must be reachable from the browser (HTTPS, or http://localhost for local dev). Double-check the callback URL shown on the consent screen matches the address your n8n actually runs at.


Trigger activated but nothing fires. On plans with the Webhooks feature (Print Farm and up), check Panel -> Settings -> Webhooks - there should be a row named after your trigger (for example "n8n: Print Finished") with your n8n callback URL. Click the row, then the Logs tab, and see what SimplyPrint saw when it tried to deliver. On the Pro plan, integration-created webhooks show as a banner with a Delete all option only - there are no per-row logs.


Events fire but n8n doesn't process them. This usually means the delivery secret didn't match. Deactivating and reactivating the workflow rotates the secret on both sides.


Leftover webhook rows after testing. The community node tears down its webhook on deactivation automatically. If you see leftover rows under Panel -> Settings -> Webhooks (on plans with the Webhooks feature) after many tests, you can delete them manually - on the Pro plan, use the Delete all option on the integration-webhooks banner.


Updated on: 11/07/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!