Trigger.dev retweeted
We just added trusted publishing so that you can deploy from GitHub Actions without a Trigger API key tgr.dev/cz7WKpG
We just added trusted publishing so that you can deploy from GitHub Actions without a Trigger API key tgr.dev/cz7WKpG
You can now set custom access on Trigger API keys, save presets for your team, limit keys by IP and narrow keys to what they actually use. Available on all plans, including Free. tgr.dev/U9COVed
We now have support for OIDC workload identity. Here's what it is and the benefits of it.
tgr.dev/SVBoaqY
1
5
564
OIDC support is now available for all Trigger.dev Cloud users
tgr.dev/nYOCZKD
We’ve published our report on the November 1st security incident
trigger.dev/blog/security-in…
Trigger.dev retweeted
Early days but you can @triggerdotdev while you @convex now. We'll add more of Trigger to this soon.
Replying to @waynesutton @convex @Cloudflare @WhatsApp @PhotonHQ @triggerdotdev @X @_sarant @clipinfit @samebasecom @Google @github
Trigger.dev by @triggerdotdev
Enqueue Trigger.dev tasks from @Convex mutations, then track their status and output through reactive @Convex queries.
convex.dev/components/trigge…
Hey @triggerdotdev did you get hacked? got an email but don't see any anouncements
1
1
670
We've just posted here:
xitter.twitterapi.xyz/triggerdotdev/status/2…
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.
trigger.dev/blog/security-in…
676
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.
trigger.dev/blog/security-in…
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.
tgr.dev/uv7Lfki
We just added two new CLI commands to help agents build webhooks with Trigger while keeping webhook secrets out of their context

ALT Two terminal commands from Trigger.dev 4.8.3. First: a Stripe CLI command creates a webhook endpoint, pipes the output through jq to extract the secret, and pipes it into npx trigger.dev@latest webhooks set-secret stripe --env prod. Second: npx trigger.dev@latest webhooks generate-secret github --env prod --to-env GITHUB_WEBHOOK_SECRET.
1
8
1,214
This week we added webhooks support for the second time. @maverickdotdev wrote up the technical choices we made
tgr.dev/IJuegql
Congrats on the launch @mattaitken, @maverickdotdev, @samejr, @DKP__ & team @triggerdotdev!
🚨 Live on @ProductHunt 👇
hubs.ly/Q04CzTPv0
Trigger.dev retweeted
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👇
youtube.com/watch?v=6GjXLwj_…
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.
1
1
117
Start building: trigger.dev/product/webhooks
All 48 integrations: trigger.dev/product/webhooks…
1
107









