Skip to main content
Two launch modes: scheduling (periodic) and incoming webhooks (from external systems).

Scheduled workflows

Cron expression

Arya supports standard cron syntax:
minute hour day month day-of-week

0 9 * * 1      → Every Monday 9:00
0 */4 * * *    → Every 4 hours
30 18 * * 1-5  → Weekdays at 18:30
0 0 1 * *      → 1st of month at midnight

Scope

A scheduled workflow can operate on:
  • The workspace (1 execution per trigger, e.g. “send weekly team report”)
  • A set of records (1 execution per record, e.g. “for every invoice open >30 days send reminder”)
1

Configure

Scheduled trigger type → cron expression + timezone + scope.
2

Test

Click Run now to test without waiting for the next slot.
3

Activate

Toggle Active. Workflow runs automatically.

Practical examples

Every Monday 9:00 → query deal pipeline → generate chart → email to manager.
Every Sunday night → find duplicate contacts → notify HR for merge.
Every day 8:00 → find contacts with today’s birthday → send personalised greeting.
Every day → invoices overdue 7/30/60 days → escalating reminder emails.
Every week → certifications expiring within 30 days → task to HR + employee email.

Incoming webhooks

Allow external systems to trigger Arya workflows by calling an HTTP URL.

Configuration

1

Create webhook trigger

Incoming webhook trigger → Arya generates unique URL:
https://api.arya.so/webhooks/wh_abc123xyz
2

Set authentication

  • None: anyone with URL can trigger (not recommended)
  • Token: X-Webhook-Token: xxx header
  • HMAC: body signature with secret key (most secure)
3

Define payload schema

Specify the expected JSON structure. Arya validates every call.
{
  "contact": {
    "first_name": "string",
    "last_name": "string",
    "email": "string"
  },
  "source": "string"
}
4

Test

Send a test call (Arya provides cURL example).
curl -X POST https://api.arya.so/webhooks/wh_abc123xyz \
  -H "X-Webhook-Token: xxx" \
  -H "Content-Type: application/json" \
  -d '{"contact": {"first_name": "Mario", ...}}'
5

Activate and share URL

Pass URL + schema to the calling system (Zapier, Make, partner, internal).

Webhook use cases

Typeform submits → Arya webhook → create contact + add to list.
Zapier connects N systems → triggers Arya as one endpoint.
ERP notes new order → calls Arya → create deal + update invoice.
External outreach tools call Arya on lead reply → create record + assign to rep.

Error handling

If the workflow fails, Arya responds to the webhook with:
  • 200 OK + body with error if you want the external system to see it
  • 500 Error if you want Zapier/Make to retry
Configurable in Advanced → Error response.

Logging

Every webhook call is logged in Webhook history:
  • Timestamp
  • Source IP
  • Received payload
  • Sent response
  • Triggered workflow (if any)

Difference from exposed webhooks

  • Incoming webhooks (this page): Arya receives from outside
  • Exposed webhooks: Arya notifies outside (outbound)

Frequently asked questions

Yes, Active/Paused toggle. Resumes from next slot on reactivation.
Only if authenticated (token/HMAC). Without auth, it’s public on the network and anyone can trigger.
100 req/sec per workspace rate limit, 500 req/sec on Enterprise. Beyond the limit Arya responds 429 with Retry-After header.