Replying to @triggerdotdev
Many million more monthly runs are coming as Cal expands calendar sync coverage.
Full story:
Trigger.dev
1,435 posts
Trigger.dev
@triggerdotdev
Build and deploy fully‑managed AI agents and workflows.
→ trigger.dev
→ github.com/triggerdotdev
→ trigger.dev/discord
- Replying to @triggerdotdevMorgan on the team's relationship with incidents: "Replays have changed how the team feels about incidents. If something fails, we replay the affected runs in a batch and move on. Nobody is dreading the on-call pager the way they used to."
- Replying to @triggerdotdevThen there's the AI phishing agent. For suspicious bookings, it opens each link in a browser and analyzes it. ~40 seconds per scan, all inside a Trigger workflow. When a link's flagged, the booking is blocked and the account shut down.
- Replying to @triggerdotdevCalendar sync uses concurrency keys + idempotency. A burst of webhooks for one account collapses into a single reconcile pass. That alone has kept them inside Google Calendar's quota.
- Replying to @triggerdotdevEnterprise customers expect sub-second confirmation. None of that fan-out can block the user. The orchestrator regenerates the booking from a small payload and passes an encrypted snapshot to children. The snapshot is optional and stays off the Trigger dashboard.
- Replying to @triggerdotdevThe booking flow is one piece: Cal runs millions of background tasks per month on Trigger: → Booking orchestration → AI phishing detection for suspicious links → Fraud and user-behavior analysis → Google + Microsoft Graph calendar sync
- Every booking on @calcom fans out into webhooks, emails, SMS, calendar APIs, Salesforce events for enterprise, billing, and fraud checks. All of it runs on Trigger. Morgan Vernay from the Foundation team on how it works ↓
- Replying to @triggerdotdevAvailable as a paid add-on. Read more and request a BAA:
- Replying to @triggerdotdevWorkloads this opens up: → Patient communication pipelines → Insurance claim orchestration → Clinical AI agents (durable, no timeouts) → Lab result workflows → Anything touching PHI
- Replying to @triggerdotdevOnce your BAA is signed, we migrate you to our HIPAA infrastructure. Same APIs and durable execution - just compliance-grade infra.
- Replying to @triggerdotdevOur compliance stack: ✓ SOC 2 Type II ✓ GDPR ✓ HIPAA (with BAA) ✓ Regular independent penetration tests All third-party audited.
- Trigger Cloud is now HIPAA-ready. Healthcare and healthtech teams can sign a BAA and run tasks that process Protected Health Information on our managed infrastructure. ↓
- Trigger.dev reposted
one of the problems which we'd run into with looooong running tasks like migrations was that when we do a new deployment, they'd just die used to be on the fence where we'd own compute for durable workflows but after having this solved by @triggerdotdev my mind is changed
