Skip to main content
A trigger is the event that starts workflow execution. Arya provides 7 trigger types covering virtually any use case.

​
Trigger types

Fires when a record is created, modified or deleted.Parameters:
  • Object (Deal, Company, Contact, Task, Project, custom…)
  • Event (Created / Updated / Deleted)
  • Optional filters (e.g. only if value > 10000)
Examples: notify sales manager on new deal > €50k; create follow-up task when a contact is added.
Fires when a record’s status changes.Parameters:
  • Object
  • Status field (stage for deal, status for task, etc.)
  • From (any or specific value)
  • To (any or specific value)
Examples: deal → Won → create project; invoice → Paid → send customer thank you.
Fires at regular intervals (cron-like).Parameters:
  • Frequency: hourly, daily at X, weekly, monthly, custom cron
  • Timezone: Europe/Rome default
  • Filters: workflow runs on a set of records (e.g. all open deals)
Examples: weekly team report every Monday 9am; month-end cleanup; automatic overdue invoice reminders.
Fires when Arya receives an HTTP POST call to a unique URL.Parameters:
  • Webhook URL (generated by Arya, e.g. https://api.arya.so/webhooks/abc123)
  • Auth method (token, HMAC signature, none)
  • Payload parse: define expected JSON schema
Examples: Zapier/Make integration; Typeform creating contacts; event from custom system.
Fires when an Arya public form is submitted.Parameters:
  • Form: pick existing form
  • Form fields become available variables
Examples: newsletter signup → add to list; demo request → create deal.
Fires when an email arrives at a monitored address.Parameters:
  • Monitored address: dedicated alias (e.g. leads@arya.so)
  • Filters: sender, subject, keywords
Examples: email to sales@ → create lead; email to support@ → create ticket.
Fires only when you launch it (from app or API).Parameters:
  • Scope: from record (action icon), from list (bulk), from global menu
  • Required inputs: fields the user fills before launching
Examples: bulk email to selected contacts; generate ad-hoc report; data cleanup script.

​
Trigger filters

Besides base parameters, every trigger accepts filters to avoid firing on every record: 
Record created AND
  deal.value > 10000 AND
  deal.stage = "Qualified"
Reduces noise and resource usage.

​
Rate limiting

To protect infrastructure, some triggers have limits:
  • Scheduled: max 1 execution/minute per workflow
  • Webhook: max 100 calls/sec per workspace
  • Email: max 1,000 parsed emails/day (base plans)
Limits raised on Enterprise plans.

​
Trigger debugging

In Run history you see per trigger:
  • When it fired
  • Which record / payload activated it
  • Which branch was taken
  • Final result

​
Frequently asked questions

No, 1 trigger per workflow. For multiple sources, duplicate the workflow or use a generic trigger + conditions.
No, async. Arya responds 200 immediately; execution can take seconds or minutes.
Yes, switch Active/Paused on the workflow.