Skip to content

Automations

An automation reacts to an event in a collection, checks conditions and runs actions. It covers notifications, emails, value changes and follow-up tasks without code.

Triggers: A record is created · A record is updated · A property is edited (only the fields you choose) · A date is reached (before, on or after a date field) · A version is created · An integration event arrives (a webhook, for example a confirmed payment) · A record is commented · An email arrives · A WhatsApp message arrives.

Actions: Notify organization users (bell or email) · Send to fixed emails · Send to customer emails · Change values · Create record · Start flow · Comment on the record · Post to a channel · Send request · Webhook (signed JSON POST) · Send WhatsApp (template).

  1. Go to Settings → Collections → the collection → Automations (Automatizaciones) → New automation.
  2. Choose the trigger, add conditions (all must hold) and the actions in order.
  3. Use record variables in texts and subjects (for example {{name}}) and relative dates such as @today+5.
  4. Emails can attach the PDF of one of the collection’s templates.
  5. Turn it on and check its recent runs in the same editor.
  • Up to 30 automations per collection.
  • Editing requires automations:edit; turning on, automations:enable.
  • Comments made by automations, flows and scripts do not fire «A record is commented» (unless you say so), to avoid loops.
  • WhatsApp only sends templates approved by Meta; Meta charges the company’s account.
  • get_automation_guide: triggers, operators, actions and valid examples; with collectionId, that collection’s fields. Read it before creating one.
  • The schema is the recommended path: patch_schema_draft with upsert_automation, then plan_schema_draft and deploy_schema_draft.
  • Outside the schema: create_entity_automation (created disabled), update_entity_automation, delete_entity_automation.