How to connect Shoptet to n8n: API, webhooks and order automation
An overview of what a Shoptet–n8n integration consists of, which scenarios it enables and when a ready-made add-on is the better choice.
On the n8n side there are two building blocks: the Webhook node receives events, and the HTTP Request node sends or reads data from any service with a REST API. On the Shoptet side, the starting point is the Shoptet API, which external developers use to connect with other services.
Shoptet states that custom implementation is available to Shoptet Premium clients with private access to the REST API. Check directly with Shoptet what access you have. If a ready-made feature is enough for you, an add-on may be all you need.
What the Shoptet API is and who uses it
An API is an interface through which two programs exchange data without a human. Shoptet describes it as a tool that lets developers build new services for e-shop owners. The documentation is intended for external developers who build integrations with other services and extend the system's functions. Source: Shoptet – developer support.
Add-ons are also integrated through this API. They are offered on the add-ons site for rent or, in some cases, one-time purchase. According to Shoptet, custom implementation is possible for Shoptet Premium clients with private access to the REST API (source).
Before planning your own integration, check with Shoptet what API access you have and under what conditions.
Webhook in n8n: how n8n receives an event
A webhook is an address to which one service sends a message when something happens. The Webhook node in n8n is a trigger node, meaning it can start a workflow (an automated process). This lets services connect to n8n and start a workflow (n8n documentation).
- It supports the DELETE, GET, HEAD, PATCH, POST and PUT methods.
- The maximum payload size (the content of the message) is 16 MB.
- Authentication: Basic auth, Header auth, JWT auth, n8n User Auth (OAuth2) or none.
- n8n provides separate URLs for testing and for production.
The test URL is registered when you choose Listen for Test Event or Execute workflow while the workflow is inactive. The production URL is registered once the workflow is published. I recommend not mixing the two up and using the production URL only after testing.
I recommend securing the webhook with authentication, so that the workflow can't be triggered by anyone who knows the address.
HTTP Request node: reading and writing data
The HTTP Request node is one of the most versatile nodes in n8n. It lets you send requests to any application or service with a REST API and supports the DELETE, GET, HEAD, OPTIONS, PATCH, POST and PUT methods.
When connecting services to n8n you usually need an API key, token or similar credentials. n8n states this for the Shopify integration; with Shoptet it will usually be similar, but the exact procedure for obtaining access is determined by Shoptet.
Which scenarios make sense
The following areas follow from what Shoptet describes. They are directions, not ready-made solutions.
Orders and shipments
Exports are used to hand shipment data over to carriers so that addresses aren't entered manually. An n8n workflow can process such data and pass it on.
Documents and stock
According to Shoptet, exports are used to synchronize documents with accounting and warehouse systems.
Editing data in the shop
For example, the Cenový automat add-on uses the API to write prices, flags, discounts and gifts.
For more examples and a look at WooCommerce, see the article E-shop automation with n8n.
How to approach your first integration
- Pick one process, for example processing shipment data.
- Check with Shoptet what API access you have and what credentials you need.
- Create a Webhook node and try it on the test URL.
- Add an HTTP Request node if you need to fetch more data from Shoptet or write data back.
- Publish the workflow so the production webhook URL is registered.
- Check the result after it runs and make sure nothing is missing.
Ready-made add-on or custom workflow
| Add-on | Custom workflow in n8n | |
|---|---|---|
| Principle | ready-made feature via the Shoptet API | a custom process built on your rules |
| Payment | rent or one-time purchase | depends on the scope of work |
| In my opinion suitable for | a standard need | a specific process or multiple systems |
Example add-on price: the Cenový automat license starts at €39.60 per month, can be tried for 14 days, and training is included. It handles repricing based on competitors on Heureka, Zboží and other comparison sites. The price is valid according to the add-on page as of 2 November 2026 and may change.
My work starts from €390; a more detailed breakdown is in the article How much AI automation costs.
When it is not worth building the integration
- A ready-made add-on already does exactly what you need.
- The process rarely repeats and takes only a few minutes by hand.
- You haven't clarified your API access, which would allow a custom integration.
- The process isn't clearly defined. Write it down first, then automate.
- You have nobody to monitor the workflow if something changes.
Automate what repeats and what you can describe in steps. Leave the rest to manual work or an add-on.
To help you choose a process, see What to automate first in your company.
Frequently asked questions
Can Shoptet be connected to n8n?
n8n has a Webhook node and an HTTP Request node that works with any service with a REST API. On the Shoptet side, the starting point is the Shoptet API. Shoptet states custom implementation via private access to the REST API for Shoptet Premium clients; check your own access with Shoptet.
What is a webhook in n8n for?
A webhook is an address to which another service sends data when an event occurs. The Webhook node is a trigger, so a message received this way starts a workflow. The maximum payload size is 16 MB.
Why does n8n have two webhook URLs?
One is for testing and the other for production. The test URL is registered with Listen for Test Event or Execute workflow, the production URL once the workflow is published.
Can I secure a webhook?
Yes. The Webhook node supports Basic auth, Header auth, JWT auth and n8n User Auth (OAuth2), or no authentication at all. I recommend turning on one of them.
Should I use an add-on or a custom workflow?
In my opinion, an add-on makes sense if it does exactly what you need. I recommend considering a custom workflow for a specific process or when connecting multiple systems.
Sources
- Podpora pre vývojárov - Shoptet.sk — checked 2 November 2026
- Chcete vytvárať vlastné doplnky? — checked 2 November 2026
- Shopify integrations | Workflow automation with n8n — checked 2 November 2026
- Webhook | Nodes — checked 2 November 2026
- HTTP Request | Nodes — checked 2 November 2026
- Cenový automat - Shoptet Doplnky — checked 2 November 2026
Related services
Related articles
Wondering what could be automated in your e-shop?
Describe the process that slows you down. Together we'll find out whether a ready-made add-on is enough or a custom integration makes sense.
I want a consultation →