Source: vercel.com/changelog/vercel-connect-adds-webhook-triggers-for-more-providers
Vercel Connect receives webhook events from these providers and forwards them to an endpoint in a Vercel project of the developer's choice. The examples given include Telegram bot messages and emails received on a Resend domain. Connect also verifies incoming requests and handles provider heartbeats and verification challenges.
Triggers are enabled in the Vercel dashboard, either when creating a connector or in an existing connector's settings. Connect registers webhooks automatically for Resend and Telegram. For Twilio, Notion and X, developers use the webhook URL that Connect provides and follow its steps to finish setup in the provider's settings.
A trigger destination sets which project and endpoint receive the events, and triggers can be turned on or off later. The connector's Observability tab has a Live view that shows incoming trigger events and request details. The new providers join existing trigger support for Slack, Discord, Microsoft Teams, GitHub and Linear.
Why it matters if you build agents
Agents that respond to messages, emails or activity on Notion and X can now receive those events without writing their own webhook receiver and verification logic. Twilio, Notion and X still need manual webhook setup in each provider's settings. The Live logs in the Observability tab help confirm that events are reaching the agent's endpoint.
Get stories like this every weekday
One short email with the day's agent tooling news.