Pipedream schedules → n8n Schedule Trigger

The n8n Schedule Trigger replaces Pipedream's schedule trigger one to one: both support fixed intervals and cron expressions. The details that bite during a migration are the timezone, the publish step, and making sure the job doesn't run in both systems at once.

Mapping

Pipedream schedule	n8n Schedule Trigger
Every N minutes / hours / days	Trigger Interval: Minutes / Hours / Days with a value
Cron expression	Trigger Interval: Custom (Cron)
Timezone chosen on the trigger	Workflow timezone (Workflow Settings), else instance timezone
Runs once deployed	Runs once published
Default timeout 60 s for cron workflows	Plan- or server-dependent execution limit

Sources: Pipedream triggers, Pipedream limits, n8n Schedule Trigger.

Timezones

Pipedream let you tie a cron expression to any timezone. In n8n the Schedule Trigger uses:

1. the workflow timezone, if set in Workflow Settings, otherwise
2. the instance timezone. Self-hosted n8n defaults to America/New_York unless you set GENERIC_TIMEZONE (docs); n8n Cloud detects the owner's timezone at sign-up (GMT as fallback), and the owner can change it.

So a Pipedream job set to "0 7 * * * Europe/Berlin" should get Europe/Berlin as the workflow timezone in n8n. Otherwise it will run at 7:00 New York time on a default self-hosted install.

Intervals behave slightly differently

Interval schedules count from the moment you publish, not from clock boundaries, and interval changes take effect only after you publish again (common issues). From n8n 2.45.0, self-hosted instances use the new durable scheduler by default; it is opt-in on earlier 2.x versions (durable scheduler). If a job must run exactly on the hour or quarter hour, use a cron expression such as 0,15,30,45 * * * * instead of "every 15 minutes".

Publish, then switch off Pipedream

A schedule in n8n runs only when the workflow is published. The safe order:

1. Import and run the workflow manually in the editor to check the output.
2. Set the workflow timezone.
3. Publish.
4. Turn off the Pipedream workflow right away, before its next run.
5. Check the n8n Executions tab after the first scheduled run.

For jobs that must not run twice (invoices, emails), turn off Pipedream first and publish n8n second, accepting one skipped run, or make the job idempotent.

Long jobs

Pipedream gave cron-triggered workflows a 60 second default timeout, adjustable up to the plan maximum. On n8n Cloud, the maximum execution duration depends on the plan; on self-hosted n8n you set it. Heavy nightly jobs are worth a timed test run before cutover.

Next steps

Our converter maps Pipedream timer triggers to Schedule Trigger nodes with the same interval or cron. The free report lists every scheduled workflow in your export so you can plan the switch-off order. More: migrate Pipedream to n8n, import workflow JSON into n8n.

Not affiliated with Pipedream or n8n.