Triggers & Webhooks

Agents that run when something happens.

Inbound webhooks and cron schedules start your agents automatically. An order comes in, a ticket is opened, it's Monday 8:00: the agent takes over, and nobody has to press a button.

Add your first trigger Talk to an expert
  • Inbound webhooks
  • Cron schedules
  • Chat triggers
order-handler
Idle Running Idle
Triggers
  • Webhook POST /hooks/order-created from the shop backend
  • Schedule 0 8 * * 1 weekly-report · Mondays 08:00
  • Webhook POST /hooks/support-ticket from the helpdesk
Activity
  1. 09:14:02 Webhook received order-created · 202 Accepted
  2. 09:14:03 Agent woke up 1 vCPU · microVM resumed
  3. 09:14:41 Run finished invoice #2041 sent
  4. 09:14:42 Back to idle waiting for the next event
  5. Mon 08:00 Schedule fired weekly-report started
Any event source

If it can send an HTTP request, it can wake an agent.

Anything with a webhook

Shop backends, helpdesks, CI systems, payment providers, and chat apps all post to the same kind of endpoint. No adapter needed.

From event to result

Automate in three steps.

  1. 01

    Create a trigger

    Add a webhook endpoint or a cron schedule to an agent. Each webhook gets its own URL and secret.

  2. 02

    Point the source at it

    Paste the URL into your shop, helpdesk, CI, or CRM. The payload is handed to the agent as the task context.

  3. 03

    Watch it run

    The agent starts, does the job, and hands off the result. Every run, its duration, and its output are in the activity log.

What you get

Event-driven agents without a scheduler to babysit.

Triggers replace the cron box, the queue worker, and the reminder to run the script by hand.

  • Inbound webhooks

    Each trigger is an HTTPS endpoint with its own secret. Payloads are verified and passed to the agent as context.

  • Cron schedules

    Run an agent every Monday at 08:00, hourly, or on any cron expression.

  • Integrations without glue code

    Shop, helpdesk, CI, and CRM talk to the agent through plain webhooks. No adapter, no middleware service to maintain.

  • Persistent workspace

    Files, notes, and state survive between runs, so the Monday report can build on last Monday's.

  • Chat triggers

    Messages in Microsoft Teams or Slack can start a run too, so a trigger can be as simple as asking.

  • Full activity log

    Every event, wake-up, run, and result is recorded with timestamps, so you can see exactly what happened and when.

EU hosting and self-hosting

Hosted in the EU. Or on your infrastructure.

Webhook endpoints and schedules run on our managed European infrastructure, or inside your own network when the event sources live there.

Discuss your deployment
Managed by zwrm

zwrm Cloud

Public webhook endpoints and the scheduler run on managed infrastructure in European data centers.

  • Hosted in European data centers
  • Managed operations and updates
  • Isolated microVMs for every run
Managed by you

Your infrastructure

Run zwrm in your own data center or private cloud so internal systems can trigger agents without leaving your network.

  • On-premises or private cloud
  • Internal event sources stay internal
  • Your security and compliance policies
Questions, answered

Before you automate.

What can trigger an agent?

Inbound webhooks from any system that can send an HTTP request, cron schedules, and messages in Microsoft Teams or Slack. You can also start a run by hand from the dashboard.

Can one trigger automate a workflow across several systems?

Yes. A webhook from the shop starts the agent, which looks up the customer in the CRM through MCP, creates the invoice, and posts the result to Teams — one trigger, one run, several systems.

How fast does an agent wake up?

The microVM resumes in seconds. The webhook is acknowledged immediately and the run starts right after.

Are webhooks secured?

Every webhook has its own URL and secret. Requests are verified before the agent sees the payload, and endpoints can be rotated at any time.

Can one agent have several triggers?

Yes. Combine webhooks and schedules on one agent, for example an order webhook plus a weekly summary schedule.

What happens if a run fails?

The run is marked as failed in the activity log with its output, and you can retry it or let the next event start a fresh run.

Your next task can run itself

Let events do the scheduling.

Add a trigger in minutes, or talk with us about your event sources and security requirements.

Add your first trigger Talk to an expert