HTTP triggers
Call a function over HTTP — the direct public URL, whose protection you choose when you publish it, and the shared platform invoke path, which requires a token by default.
Scheduled triggers (cron)
Fire a function on a cron schedule — exactly what arrives at your handler, retries, execution-policy surprises, and a complete worked example.
Pub/Sub triggers
Push every message on a topic to a function — subscription wiring, what your handler receives, retries and dead-lettering, and a complete worked example.
ObjectStore triggers (bucket events)
Fire a function when new objects land in an S3-compatible bucket — the body is the object itself, poll latency, after_read retirement, the credentials secret, and a complete worked example.