Skip to content

Scheduling specific workflows can be a useful organization tool, so PlaidCloud provides the ability to do just that. Using Event Scheduler, you can schedule a workflow to run by month, day of the month, day of the week, hour and minute — in whatever timezone the schedule should be read in.

A scheduled event names one workflow in one project, plus the schedule it runs on. To run several workflows on the same cadence, add one event for each.

The Events Table lists every event in the workspace with the project and workflow it runs, its UTC offset, the status and start and end time of its last run, and when it is next due.

To view events:

  1. Open Analyze
  2. Select “Tools”
  3. Click “Event Scheduler”

This will open the Events Table showing all the current events configured for the workspace.

Scheduleby month · day · hour · minuteread in a chosen timezonefiresworkflow runrunrunrunon the schedule, over time →
Define when — by month, day of the month, day of the week, hour and minute, read in the timezone you choose — and the event fires the workflow automatically at each scheduled time.

To create an event:

  1. Open Analyze
  2. Select “Tools”
  3. Click “Event Scheduler”
  4. Click “Add Scheduled Event”
  5. Complete the Details, Timezone and schedule fields described below
  6. Click “Create”

Name — how the event appears in the Events Table. Required.

Memo — an optional note about what the event is for.

Activate Job and Run on Defined Schedule — ticked by default. Untick it to save the event without letting it run; see Pausing an Event.

Project and Workflow — the workflow this event runs. Choose the project first: the Workflow list is filled from whichever project is selected. Both are required, and both are fixed once the event exists — to move an event to a different workflow, delete it and add a new one.

The schedule is read in this timezone, chosen as an offset from UTC -12 to UTC +14. It defaults to UTC +0, which is read as London time, British Summer Time included.

Most offsets are the local time of a place at that offset, and follow that place’s daylight saving: an event at UTC -5 set to 09:00 runs at 09:00 in New York in summer and in winter, which is 13:00 UTC in summer and 14:00 UTC in winter. The Next Run column and the upcoming-runs calendar show when the event will actually run.

Offset Read as Daylight saving
UTC -12 UTC -12 No
UTC -11 Pago Pago No
UTC -10 Honolulu No
UTC -9 Anchorage Yes
UTC -8 Los Angeles Yes
UTC -7 Denver Yes
UTC -6 Chicago Yes
UTC -5 New York Yes
UTC -4 Puerto Rico No
UTC -3 São Paulo No
UTC -2 South Georgia No
UTC -1 Azores Yes
UTC +0 London Yes
UTC +1 Rome Yes
UTC +2 UTC +2 No
UTC +3 Riyadh No
UTC +4 Dubai No
UTC +5 Karachi No
UTC +6 UTC +6 No
UTC +7 Bangkok No
UTC +8 Singapore No
UTC +9 Tokyo No
UTC +10 Sydney Yes
UTC +11 Guadalcanal No
UTC +12 Auckland Yes
UTC +13 Apia No
UTC +14 Kiritimati No

The schedule is five fields — Months, Hours, Minutes, Days of Month and Days of Week — each a list of tick boxes with an All box at the top. The event runs whenever the current time matches a ticked value in every field at once.

Every field needs something: tick All to match every value, or tick the individual values you want. A field left completely blank stops the event saving, and the message names the field so you can find it.

Some examples:

  • Every day at 06:30 — All under Months, Days of Month and Days of Week; 06 under Hours; 30 under Minutes.
  • The 1st of every month at midnight — All under Months and Days of Week; 01 under Days of Month; 00 under Hours and Minutes.
  • Every weekday at 18:00 — All under Months and Days of Month; Monday to Friday under Days of Week; 18 under Hours; 00 under Minutes.
  • Every 15 minutes — All under Months, Days of Month, Days of Week and Hours; 00, 15, 30 and 45 under Minutes.

Each event carries its own ERP posting mode — Live, Simulate or Off — and every run it starts uses it. An event with no mode set runs Live, and the project’s own posting mode cap still applies on top, so an event can never post more freely than its project allows.

Set the mode through the API or an AI assistant: the erp_write_mode field (live, simulate or off) on PUT /rest/v1/analyze/workflow/scheduled-event, or on the workflow_schedule MCP tool’s upsert. The event keeps it from then on. Editing the event in the Event Scheduler, pausing it or re-enabling it leaves the mode as it was, so a schedule set to Simulate stays simulated every time it fires until you change the mode itself.

To edit an event:

  1. Open Analyze
  2. Select “Tools”
  3. Click “Event Scheduler”
  4. Click the edit icon
  5. Adjust desired fields
  6. Click “Update”

The project and workflow are shown read-only while editing — an event stays attached to the workflow it was created against.

To delete an event:

  1. Open Analyze
  2. Select “Tools”
  3. Click “Event Scheduler”
  4. Click the delete icon
  5. Click delete again

To pause one or more events:

  1. Open Analyze
  2. Select “Tools”
  3. Click “Event Scheduler”
  4. Select the event or events
  5. Click “Disable Selected”

Click Enable Selected to start them running again. A paused event keeps its schedule and its run history — it simply stops firing until it is re-enabled, and its Active icon clears in the Events Table.

You can also pause a single event while editing it: untick Activate Job and Run on Defined Schedule and click Update.

To run an event immediately:

  1. Open Analyze
  2. Select “Tools”
  3. Click “Event Scheduler”
  4. Select the desired event or events
  5. Click “Run Selected Events”