Question 1

What are lifecycle events in Webiny?

Accepted Answer

Lifecycle events are before and after hooks that fire whenever content changes.

They run on:
Create
Update
Delete
Publish and unpublish
Asset uploads and changes
Tenant-level operations

These events let you attach logic directly to content behavior — not via fragile polling or external glue.

Question 2

What can I do with lifecycle events?

Accepted Answer

Lifecycle events turn content into an active system component.

You can use them to:
Validate or transform data before it’s saved
Trigger background jobs or async processes
Sync content to internal systems
Notify teams via Slack, email, or other channels
Enforce business rules consistently
Propagate or inherit content across tenants

If it should happen because content changed, it belongs here.

Question 3

Can lifecycle events run background or long-running tasks?

Accepted Answer

Yes!

Webiny is designed for enterprise-scale workloads, where not everything should happen synchronously.

Using lifecycle events, you can:
Trigger background jobs
Queue async processing
Handle heavy transformations
Integrate with message queues or workflows
Keep the editorial UI fast and responsive

Editors never wait — automation runs in the background.

Question 4

Do lifecycle events work across apps and tenants?

Accepted Answer

They do.

Lifecycle events can:
Apply globally or per app
Run across tenants or be tenant-specific
Drive content inheritance and propagation
Enforce consistency at scale

This is especially powerful in multi-tenant or multi-brand setups where rules must be applied reliably everywhere.

Question 5

How are lifecycle events built and maintained?

Accepted Answer

Lifecycle logic is written in TypeScript, lives in your codebase, and ships through CI/CD.

That means:
Logic is version-controlled
Changes are reviewable and testable
Deployments are predictable
Rollbacks are straightforward

No admin UI toggles.
No hidden rules.
Just code you own.

Question 6

Who is this feature designed for?

Accepted Answer

Lifecycle events and automation are ideal for teams that:
Integrate content with internal systems
Need deterministic business rules
Operate at scale or across many tenants
Want fewer manual processes
Treat content as part of their application logic

If content drives real workflows, this is essential.

Question 7

Automation without fragility

Accepted Answer

Many systems rely on chains of SaaS tools and external webhooks to move content around.

Webiny keeps automation close to the source of truth:
Fewer moving parts
Less operational risk
More predictable outcomes

Automation becomes infrastructure — not duct tape.

Question 8

How is this different from webhooks?

Accepted Answer

Webhooks fire after the fact and outside your control.

Lifecycle events are different:
They run inside your environment
They can block or modify operations
They are versioned and deployed as code
They don’t depend on external availability
They execute with full context and permissions

This makes them deterministic, debuggable, and safe to rely on for core logic.

Loading...

Lifecycle events that turn content into workflows

Automation without fragility. Many systems rely on chains of SaaS tools and external webhooks to move content around. Webiny keeps automation close to the source of truth.

Frequently Asked Questions

Want to turn content changes into real workflows?