Skip to content

4. A cron workflow

Your first working automation, with no public endpoint to trigger it.

4.0 Why

Before you publish a public endpoint in the next chapter, prove that n8n itself runs. A workflow nothing outside can reach is the cleanest way to do that. A schedule needs no inbound URL: you edit it over the org hostname, and n8n fires it on the box on its own clock. If this run fails, the problem is n8n or your workflow, not an Edgible hostname or auth mode.

Not every workflow needs a public endpoint. The n8n-hooks app exists only for calls that arrive from outside, and this chapter works the same if you never created it. A public hostname or a forwarded port to make a timer fire only widens your attack surface.

Where you run this: the n8n editor in a browser on the org hostname, phone or host browser, either is fine. No shell, no Edgible console.

4.1 The job

You add a Schedule workflow that writes one Executions row. Nothing on the internet calls you. If this fails, the problem is n8n, not Edgible hooks.

Done when

  • The workflow is Active.
  • After the next tick (or Execute workflow once), Executions shows at least one success.
  • You then set the schedule to something sane (or deactivated the workflow) so it does not fire every minute forever.
  • You did not open a port or change Edgible auth.

Need first: 2. n8n editor through Edgible (canvas on the phone or host browser). Chapter 3 can wait, but you will want it before 5.

Not this chapter: Webhook nodes, GitHub, Telegram, OpenClaw.

4.2 Build it

In the n8n editor (org URL):

  1. Add workflow.
  2. Delete the start stub if n8n added a manual trigger you do not want. Add Schedule Trigger (or Schedule).
  3. Interval: every 1 minute for the smoke test (you will change this).
  4. Add Edit Fields / Set. One field, e.g. at = {{ $now }} (or n8n’s current “current date” expression).
  5. Save. Active (toggle on).

Smoke test. Wait up to a minute, or click Execute workflow once to force a run.

Open Executions. You want a green row, not a red error.

Then edit the trigger: every hour, or deactivate it, so a trial VM is not ticking all day.

Verify

  • The workflow is Active.
  • After the next tick (or Execute workflow once), Executions shows at least one success.
  • You then set the schedule to something sane (or deactivated the workflow) so it does not fire every minute forever.
  • You did not open a port or change Edgible auth.

Next

5. A webhook a stranger can hit. Series: README.

Last updated