# What are events?
Events trigger workflow executions. The event that triggers your workflow depends on the trigger you select for your workflow:
HTTP triggers execute your workflow on HTTP requests.
Cron triggers execute your workflow on a time schedule (e.g., on an interval).
Email triggers execute your workflow on inbound emails.
# Event format
When you send an event to your workflow, we take the trigger data — for example, the HTTP payload, headers, etc. — and add our own Pipedream metadata to it.
When you click on an event in the Inspector, we show you the contents of
steps.trigger.event directly under your trigger step.
The specific shape of
event varies with the trigger type:
| ||A string or object representation of the HTTP payload|
| ||IP address of the client that made the request|
| ||HTTP headers, represented as an object|
| ||For example, |
| ||HTTP method|
| ||Request host + path|
# Cron Scheduler
| ||String representation of the schedule|
| ||The epoch timestamp when the workflow ran|
We use Amazon SES to receive emails for the email trigger. You can find the shape of the event in the SES docs.
In addition to the formatted object we expose in
event, you have access to the raw, protocol-specific data from the event, as well.
You can access this data in
steps.trigger.raw_event. The contents also vary with the trigger type:
- HTTP : scheme, URI, and base64-encoded raw payload.
- Cron Scheduler : same as
- Email : same as
# Event observability
Pipedream provides observability for the event that triggered your workflow, including into the trigger event and step-level workflow execution. Just select an event from the inspector to view its contents.