X
min read
·
Updated
Sat Aug 22 2026 00:00:00 GMT+0000 (Coordinated Universal Time)
A trigger is the moment that starts an Agent. The current template gallery uses paid-order events and repeating schedules, while each template's setup questions supply the values its steps need.
The current business-event trigger is order paid. ProfitJam checks active Agents when a Catalog order is finalized as paid, then starts every matching Agent in that workspace.
This trigger powers the new-order team alert, big-order alert, and order thank-you templates.
A scheduled Agent repeats after a fixed interval. Current templates offer choices such as every 15 minutes, hourly, daily, or weekly, depending on the job. The first run becomes due one full interval after you activate the Agent.
The daily owner digest and Google Drive folder watcher use this pattern. The Drive watcher is a repeating schedule followed by a folder check; it is not a separate trigger type.
The Agent engine can store a starting event from a connected service and optionally narrow it by that service's event name. There is not currently a general connected-service trigger form in the Agents screen, so use only a published template or a Tempo-created draft that confirms the connection is supported.
Conditions are currently part of a template's setup rather than a separate rules builder. Depending on the template, you may be asked for:
These answers are saved into the trigger or its ordered steps when the draft is created.
Important: Agents do not currently provide a visual if/else, AND/OR, or branching editor. The big-order template still sends its generic team alert for every paid order, and the Drive watcher still sends its generic alert after each check even when no new-file result is carried into that later step. Treat those settings as preview behavior until the conditional handoff is completed.
Not in the current Agents screen. Use the setup questions offered by a template. Tempo can create only requests supported by the current trigger and step library.
No. The current in-product business-event trigger is a paid Catalog order. Repeating schedules are also supported, and connected-service events require a supported integration path.
Not in the current big-order template. The threshold is included in the AI instruction, but there is no branch that stops the following generic alert.
The first run is due one selected interval after activation. Pausing disables the schedule; resuming starts a new interval from that point.
The folder watcher starts on a repeating schedule. Checking Drive for new files is its first step.
Support answers in under a business day, and reads your workspace before replying.