Action triggers and placeholders
Found this helpful? Share it:
Found this helpful? Share it:
A trigger decides when an Action runs. This page covers the three kinds, the conditions that narrow an event trigger, and the placeholders that put event data into the prompt.
Pick how often: every day, every week, every month, and the time. The Action fires on that pattern in your time zone. You can also write a cron expression when you need something the picker does not offer.
Choose an event source, such as a note being created or a file being uploaded. The Action fires after the write commits, once per event.
A condition is a field, an operator, and a value. Only events that match every condition reach the agent, so a noisy source can be narrowed to the case you care about. An empty condition row is dropped rather than rejected.
Debounce collapses a burst of events into one run. A long import that creates forty notes becomes a single run instead of forty.
The prompt can include data from the event. Write a placeholder in double braces and the value is substituted before the agent sees the prompt:
Summarise the new note titled {{event.payload.note.title}}.The placeholder menu under the prompt lists what the chosen source actually
sends, including a suggested field such as
event.payload.note.title. Dot paths reach into the event
body; a whole object is substituted as JSON, not as a placeholder.
A placeholder that never resolves stays exactly as written. The test step names every unresolved placeholder, because those literal braces would reach the agent otherwise.
A webhook trigger gives you a URL and a secret: anything that can send an HTTP request can start the Action. Every Action can also be run by hand from its page, which is the fastest way to check a prompt.
Related articles
Was this helpful?
Summarise the new note titled {{event.payload.note.title}}.Summarise the new note titled {{event.payload.note.title}}.