There has been a security incident at Trigger.
We have emailed the owners of all impacted accounts.
We’ll be providing more information but for now the focus is on giving the impacted account owners what they need to mitigate.
https://t.co/ubw9DoA5Ka
There has been a security incident at Trigger.
We have emailed the owners of all impacted accounts.
We’ll be providing more information but for now the focus is on giving the impacted account owners what they need to mitigate.
https://t.co/ubw9DoA5Ka
We upgraded our Bun runtime to Bun 1.4 and took Node.js out of the image entirely.
Memory per container dropped 41%, cold starts are 18% faster and the image is 25% smaller.
@jarredsumner and the @bunjavascript team are still cooking.
https://t.co/Y6ZfBEFgDU
Most of the time AI agents need someone to manually prompt them to get started.
With webhooks on @triggerdotdev, you can trigger and resume agents off of real events:
• GitHub PR opened → agent reviews diff & writes tests
• Sentry error spikes → agent diagnoses & drafts a fix
• Stripe refund requested → agent flags it & waits for Slack approval
No need to manually tell the agent what to do!
Your AI agents can now be triggered by webhooks from services like Stripe, GitHub, Slack, Shopify, Supabase, ElevenLabs and Resend.
@jacksbridger built an agent which drafts a reply to every Resend email and waits for your OK in Slack.
Here are 7 ideas for agents you can build with Trigger webhooks👇
https://t.co/38BOzcLfu5
Every webhook is stored before we reply 200 OK. Retries match on the provider's event ID, so they don't start a second run. Filtered events use no compute.
Provider not listed? Custom sources take an HMAC, a shared secret, a URL secret or a public key.