00
Automations

When targets are hit,rewards happen automatically.

Define a trigger, set conditions, choose an action. Wudd handles the rest. Gifts, points, badges, nudges, and budget allocations fire without anyone lifting a finger.

01
How It Works

Three building blocks. Infinite combinations.

Every automation follows the same pattern: when something happens, check who qualifies, then do something for them.

Trigger
When this happens

An event fires or a schedule ticks. The engine wakes up.

  • +Badge earned by an employee
  • +Cron schedule (daily, weekly)
  • +KPI threshold crossed
Condition
Who qualifies

Filter the audience by role, tenure, department, or custom criteria.

  • +Role is employee or team leader
  • +Tenure over 90 days
  • +Department matches target
Action
Then do this

Send an in-app notification or allocate a SAR budget. Two action primitives that compose into rich workflows.

  • +Send in-app notification
  • +Email an employee with a manager-suggested action
  • +Allocate SAR budget
02
Use Cases

Automations that run your culture.

Real scenarios that organisations set up in minutes.

Top performer celebration

When an employee earns 10 badges in a quarter, allocate a 500 SAR celebration budget for the team and notify their manager.

Birthday celebration

On each employee's birthday, send a personalised nudge to their manager with a reminder to recognise them.

Work anniversary celebration

At 1, 3, and 5 year milestones, allocate a celebration budget and trigger a company-wide recognition nudge.

KPI target hit

When a team hits their quarterly OKR target, trigger a budget allocation for a team celebration.

Wellness day suggestion

When an employee maintains a recognition streak for 30 consecutive days, the system sends a wellness-day suggestion to the employee and their manager. The team arranges the timing off-platform.

Onboarding quest complete

New hires who finish their onboarding quest within 14 days trigger a welcome budget allocation and a manager nudge to grant the welcome badge.

03
Guardrails

Automations that stay safely in bounds.

Every automation has built-in safety limits. No runaway spending, no notification spam, and absolutely no duplicate rewards.

  1. 01
    Budget cap (SAR/month)
    Set a maximum monthly spend per automation. The system pauses execution when the limit is reached and alerts you.
  2. 02
    Frequency cap (days)
    Prevent the same employee from being targeted more than once within a set time frame to eliminate notification fatigue.
  3. 03
    Audience cap
    Limit the number of users affected per run. This protects against accidentally misconfigured conditions that match too many people.
  4. 04
    Duplicate Prevention
    A strict tracking system prevents the exact same automation from firing twice for the same person in the same time window. Zero duplicates.
  5. 05
    Dry run mode
    Test any automation without executing it. See the full audience, actions, and budget impact before going live.
04
Full Audit Trail

Every action is recorded.

Historical tracking, execution logs, budget usage, and audience records. Nothing happens in the dark.

Versions
Permanent history

Every change to an automation creates a locked, new version. Previous versions are securely preserved for accountability.

Runs
Execution history

Track the exact start time, end time, total people reached, actions sent, and budget consumed for every single run.

Budget
Spend tracking

Monthly budget reservations are strictly recorded per automation and aggregated for easy finance reporting.

Decisions
Why it fired or did not

Safety blocks, prevented duplicates, and exact audiences reached are all fully logged so you always know what happened.

Next step

Set it once. Let it run.

Automations that reward, nudge, and celebrate without manual intervention. Built-in guardrails keep things on track.