Skip to main content
Helm automations watch your tables and act for you — update records, send emails and notifications, call webhooks, or hand work to an AI agent. Each automation pairs one trigger with up to 10 actions and can be switched on and off at any time.

​
Triggers

​
Actions

Actions are grouped into Records, Notify, and Integrations: Text settings support tokens like {{trigger.fieldName}} that fill in values from the triggering record. Payment triggers expose tokens such as {{trigger.amount}}, {{trigger.currency}}, and {{trigger.customerEmail}}.

​
Testing and run history

  • Test run executes the automation against the table’s most recent matching record so you can check the wiring before enabling it.
  • New automations start off; flip the switch in the editor header when you’re ready.
  • The Run history drawer shows each run’s status (success, failed, or skipped), what triggered it, how long it took, and a step-by-step log of every action.
Automations don’t chain: an action that updates a record will not fire other automations, so loops can’t happen. Scheduled automations process up to 50 records per run.