Replace Pipedream’s delay step before Workflows shuts down.

Pipedream’s documentation states that Workflows and String shut down on March 31, 2027. Workflows is in maintenance mode and no longer accepts signups or new subscriptions. All Workflows data, connected-account credentials included, is to be deleted by April 30, 2027. Pipedream Connect is not affected. The docs offer a JSON export of workflow structure, one project at a time, but no replacement product.

We checked this on pipedream.com/docs/workflows on October 24, 2026. Read the notice there for anything that changes after that date.

Pipedream offers two ways to pause: $.flow.delay in a Node.js code step and the built-in Delay action. Both pause the execution for anywhere from a millisecond to a year, and both return a cancel_url that stops that execution and a resume_url that continues it early.

That covers a common need: “do this in three days unless something happens first.” A trial reminder that should not go out after an upgrade, a dunning email that should not go out after payment, a follow-up that should not go out after a reply.

The real change is structural. A Pipedream delay resumes the same execution with its earlier step results. A scheduled webhook calls a URL later, so the steps after the delay move behind an endpoint, and anything they need travels in body. Have that endpoint re-read the current state (has the order been paid?) before it acts.

// Pipedream Node.js step
export default defineComponent({
  async run({ steps, $ }) {
    const { cancel_url } = $.flow.delay(3 * 24 * 60 * 60 * 1000);
    // save cancel_url to cancel if the customer pays first
    // ...steps that run three days later
  },
});

// Wherever the workflow starts (your API, a job, a no-code HTTP step)
const res = await fetch('https://webhookscheduler.com/api/v1/schedule', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.WEBHOOK_SCHEDULER_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    url: 'https://api.example.com/hooks/payment-follow-up',
    runAt: new Date(Date.now() + 3 * 24 * 60 * 60 * 1000).toISOString(),
    reference: `order:${order.id}`,
    body: { orderId: order.id, email: order.email },
  }),
});
const { id } = await res.json(); // keep it, or rely on the reference

// Later, if the customer pays first
await fetch(`https://webhookscheduler.com/api/v1/jobs/${id}/cancel`, {
  method: 'POST',
  headers: { Authorization: `Bearer ${process.env.WEBHOOK_SCHEDULER_KEY}` },
});

If you would rather not store the id, set a reference such as order:ord_1042. When the customer pays, list the open jobs with GET /api/v1/jobs?reference=order:ord_1042&state=open and cancel each one.

It is not a workflow engine. It does not run your code, host triggers, or connect to apps. If the rest of your Pipedream workflow needs a new home, move it to your own backend or a tool such as Make or n8n, and use Webhook Scheduler only for the delay. The target must be a public HTTPS URL. Free plans schedule up to 7 days ahead. Delays longer than that, up to 365 days, need a paid plan, and there are no recurring schedules.

Comparing other options for the delay itself? See delayed webhook services compared, with max delay, cancel, retries and free tiers side by side.