Schedulers & Webhook Triggers

Put your business playbooks on autopilot. Aigenzey Cowork enables background execution through two powerful automation primitives: time-based recurring Schedulers and event-driven Webhook Triggers.

Automations Overview

Automations run autonomously in dedicated worker processes without requiring you to keep a browser tab open. When an automation fires, Cowork executes the associated skill or task prompt, attaches necessary user credentials, records the run in the audit log, and delivers the finished artifact or notification.

Scheduled Tasks & Cron

You can schedule tasks directly from the chat interface or from Automations → Schedulers.

Creating a Scheduled Task via Chat

Simply instruct the agent with your desired recurrence:

• "Schedule a weekly task for every Monday at 8:30 AM: Scan Salesforce for new Enterprise opportunities and post an alert to #sales-team."
• "Every weekday at 6:00 PM, summarize unread VIP emails from Gmail and send me a daily digest notification."

Scheduler Architecture & High Availability

• Atomic Task Leases: Background worker daemons use PostgreSQL advisory locks to guarantee that recurring tasks execute exactly once, even across multi-instance clusters.
• Timezone Alignment: Tasks are calculated relative to each user's local timezone configured in their profile.
• Error Backoff: If a scheduled run fails due to external API outages, the scheduler logs the failure and alerts the user with an in-app error notification.

Webhook Triggers (/hooks)

Webhook triggers allow third-party systems to invoke Cowork skills whenever external business events occur.

Creating a Webhook Trigger

1. Navigate to Automations → Triggers → New Trigger.
2. Select the target Skill to execute.
3. Cowork generates a unique webhook endpoint URL:

POST https://cowork.aigenzey.com/hooks/trg_8f29d1c04ba24e93

Security & HMAC Authentication

Webhook endpoints can be secured using HMAC SHA-256 signatures:

• Specify a secret token when defining the trigger.
• Configure the calling system (e.g. GitHub or Stripe) to include the signature header (e.g. X-Hub-Signature-256 or X-Signature).
• The Cowork ingestion gateway verifies the signature before dispatching the execution to background workers.

Payload Ingestion & Parameters

Inbound JSON payload data is automatically passed to the target skill as execution parameters:

{
  "event": "charge.failed",
  "customer_email": "jane@acme-corp.com",
  "amount_cents": 250000,
  "failure_reason": "card_declined"
}

The agent receives the payload in its initial turn context, pulls the customer's CRM profile from HubSpot, checks recent support tickets in Zendesk, and drafts an account recovery email for review.

Notifications & Result Delivery

When an automation finishes, results can be routed across several channels:

• In-App Notification Center: Unread count badge with full execution summary and direct link to the run trace.
• Email Summaries: Direct email dispatch containing the markdown report or spreadsheet attachment.
• Chat Channels: Instant notifications posted directly to Slack, Microsoft Teams, or Discord channels via authenticated connectors.