Pipedream alternative: move your print workflows in time
Pipedream Workflows is shutting down on March 31, 2027. How to pick a Pipedream alternative, move your workflows and keep printing documents automatically.
Обновлено 21 октября 2026 г.
Pipedream is shutting down its Workflows product. If you use it to print invoices, packing slips, labels or email attachments automatically, or planned to, you need a Pipedream alternative by spring 2027. This article sums up what Pipedream announced, what you have to move, which platforms are worth a look and how printing works after the move. The short version: printing is a single HTTP request, and it works the same way on every platform.
Pipedream Workflows is shutting down: what was announced
Pipedream announced the shutdown in its documentation under Workflows and String Are Shutting Down on March 31, 2027. The key points:
- Shutdown on March 31, 2027: "Pipedream Workflows and String will shut down on March 31, 2027."
- No new accounts: Workflows is in maintenance mode. Pipedream writes that "we're no longer accepting signups or subscriptions" and that it won't ship new features for Workflows.
- Existing workflows keep running: "Your existing workflows will keep running normally through March 31, 2027."
- Data is deleted: "All Workflows data will be permanently deleted by April 30, 2027, including the credentials and OAuth tokens."
- Subscriptions: according to Pipedream, subscriptions end on March 31, 2027 with a prorated refund. Monthly subscribers can cancel in their account settings, annual subscribers can contact support.
- Pipedream Connect stays: the API for connecting AI agents to other services is not affected. It is not a workflow builder, though, so it does not replace Workflows.
If you are setting up automatic printing for the first time, don't start on Pipedream Workflows. If you already run workflows there, you have until the end of March 2027, but it pays not to wait until the last week.
What you need to move
Pipedream offers an export tool that downloads the structure of all workflows as JSON, one project at a time (see Export Workflows). The export describes triggers, steps, code, configured values and the flow. You can't import it directly into another platform, though. Treat it as a blueprint for rebuilding your workflows.
Go through each workflow step by step:
- Triggers: a new email with an attachment in Gmail or Outlook, a new file in Google Drive, a new order in Shopify, a schedule or an HTTP webhook. All major platforms have matching triggers for the common services.
- HTTP steps: every request with its method, URL, headers, query parameters and body. These are the easiest to carry over.
- Code steps: Node.js or Python code. The code itself is in the export. Calls to Pipedream helpers such as
$.files,$.flowor$.exporthave to be replaced with what the new platform offers. - Credentials: according to Pipedream, credentials and OAuth tokens are never exported. Reconnect every account on the new platform.
- Environment variables: they are not in the export either. Write down which variables a workflow uses and create them again. That includes secret URLs such as the endpoint URL you print with.
- Data stores, file stores and history: they are not part of the export. Back them up separately if you need them.
- Webhook URLs: if a workflow uses an HTTP trigger, other services send their events to a Pipedream address,
usually under
*.m.pipedream.net. The announcement does not mention these addresses. Assume they stop accepting events at the shutdown, and enter the new webhook address in every sending service in good time.
Pipedream alternatives compared
Three platforms are the obvious candidates for Pipedream users. All three can send a file over HTTP, which is all it takes to print.
| n8n | Make | Zapier | |
|---|---|---|---|
| Hosting | Cloud or self-hosted | Cloud | Cloud |
| Code steps | Code node (JavaScript, Python) | Make Code app (JavaScript, Python, paid plans) | Code by Zapier |
| Free start | Cloud trial, self-hosted Community Edition | Free plan | Free plan, two-step Zaps only |
| Send a file over HTTP | HTTP Request node | HTTP module | Webhooks by Zapier, not on the Free plan |
n8n is the closest match if you write a lot of code. You can use n8n Cloud or run it yourself, for example with Docker Compose. Without a license key, n8n runs as the free Community Edition, which makes it the usual answer when people look for an open-source or self-hosted Pipedream alternative. The cloud version bills by workflow executions and has no permanent free plan, but it offers a trial.
Make is a visual builder with scenarios, routers and filters. It has a Free plan with a monthly allowance of credits. Your own code runs in the Make Code app, which according to Make is available on paid plans.
Zapier has the largest number of ready-made app integrations. The Free plan only allows Zaps with one trigger and one action. For printing you generally need Webhooks by Zapier, and according to its pricing page that is only included in paid plans.
Pipedream vs. Zapier, or n8n vs. Make: check prices and limits on the vendors' sites before you move. They change often.
Printing after the move
For printing, the choice of platform hardly matters. With Sealed Print, the workflow sends the document over HTTP to a secret URL, called an API endpoint. Sealed Print turns it into a print job and delivers it to the printer: through the relay client on a computer or NAS in the office, directly to printers that support IPP INFRA, or over IPP to a printer that is reachable from the internet. The relay client and INFRA printers only make outgoing connections, so you don't need to open any ports on your router.
Prerequisites
- A Sealed Print account with at least one destination, that is, a printer. How to connect a printer in the office is explained in the guide Install the relay client.
- An admin has switched on the inbound channel REST API under Settings → Inbound channels. It is off by default.
- An API endpoint under Sources → API endpoints → New API endpoint, with a Destination or the
Default target. The Endpoint URL looks like
https://www.sealedprint.com/api/print/sp_ep_…. Details are in the guide API endpoints. - The document is a PDF, JPEG or PNG of at most 50 MB.
The URL is the access key. Anyone who knows it can send documents to your printer. Store it on the new platform as an environment variable or secret, not in plain text in every step.
The request
The file is the request body, and the Content-Type is application/pdf, image/jpeg or image/png. The job name
and print options are query parameters:
curl -X POST "https://www.sealedprint.com/api/print/sp_ep_…?name=Invoice%201042&sides=two-sided-long-edge" \
-H "Content-Type: application/pdf" \
--data-binary @invoice-1042.pdf
In a Node.js code step, the same request looks like this. pdf is a Buffer with the document, for example from a
previous step, and PRINT_URL is the endpoint URL:
const url = new URL(process.env.PRINT_URL)
url.searchParams.set("name", "Invoice 1042")
url.searchParams.set("sides", "two-sided-long-edge")
const response = await fetch(url, {
method: "POST",
headers: { "Content-Type": "application/pdf" },
body: pdf,
})
if (response.status !== 201) {
throw new Error(`Sealed Print: HTTP ${response.status} ${await response.text()}`)
}
const job = await response.json()
Alternatively, the endpoint accepts a form with the file field file. In that case Sealed Print reads the options
from the form fields instead of the query parameters.
Sealed Print answers with HTTP 201 and the new job as JSON, including id, number, name and state. The job
shows up in the Queue right away.
Parameters and errors
All parameters are optional: name, copies, sides, colorMode, media, mediaSource, orientation,
quality, pageRanges, scaling and finishings set the job name and print options. targets takes the
identifiers of destinations or destination groups, comma-separated, for example targets=office,warehouse
(destinationId, destinationIds and groupId do the same with IDs). If the request names no target, the
endpoint's target applies, and with Default target your default target. Several destinations and
destination groups are part of the Team plan. The simplest setup is one endpoint per printer.
The most important responses: 400 for an invalid value, 402 for several destinations or a group without the Team
plan, 403 if the inbound channel REST API is switched off, 404 for a wrong or replaced URL, 413 for a file that is
too large and 415 for a wrong or missing Content-Type.
Be careful with automatic retries: every successful request creates a new job. If the connection drops after Sealed Print has already accepted the job, a retry prints the document a second time. When in doubt, check the Queue.
Step by step on the new platform
These articles describe the setup with all parameter tables, examples and how to look up IDs:
- Print automatically from n8n with the HTTP Request node,
- Print automatically from Make,
- Print automatically from Zapier.
If you would rather call the endpoint from your own code, the use case page Print API shows more examples. Sealed Print bills per delivery, one document to one printer; the plans are on the pricing page.
Frequently asked questions
When is Pipedream Workflows shutting down?
On March 31, 2027. Existing workflows keep running normally until then. Pipedream already accepts no new signups or subscriptions. All Workflows data will be deleted by April 30, 2027.
What happens to my webhook URLs?
The announcement does not mention the addresses under *.m.pipedream.net. Since the workflows behind them are shut
down, expect these addresses to stop processing events afterwards. Enter the new platform's webhook address in every
sending service and test it before you turn off the old workflow.
Which Pipedream alternative fits best?
If you write a lot of code or want to keep data in your own infrastructure, n8n is the natural choice, because you can host it yourself. Make suits visual scenarios with branches, Zapier the widest choice of ready-made app integrations. For printing, an HTTP request is enough on all three.
Is there an open-source alternative to Pipedream?
n8n is the best-known option. Its Community Edition can be self-hosted for free, for example with Docker Compose. Its license is a fair-code license rather than a classic open-source license, so check whether its terms suit your use before you build on it.
Can I import my Pipedream workflows automatically?
Not as far as we know. Pipedream's export delivers JSON files with the structure and code of the workflows, but no credentials or environment variables. It serves as a blueprint for rebuilding them.
Do I have to change anything at the printer or in the office?
No. If you already print with Sealed Print, the relay client, destinations and endpoint URL stay the same. Only the workflow that calls the URL moves to the new platform.