Event Connections

​

Overview

Event connections are shared provider-level connections used by triggers. They are separate from MCP tool connectors: MCP connectors let agents call tools, while event connections let providers send events that can start or route agent work.

​

Event Connection Flow

​

Choose a Provider

The provider list is sourced from budevent descriptors. Each descriptor can define credential fields, provider type, sample events, grouping suggestions, and available event types.

​

Enter Descriptor Credentials

Bud Admin renders fields from the provider descriptor. Required fields must be present before creation. Secret fields are masked in the form.

​

Select Scope

• Project creates a project-scoped connection. The current project is always included and additional projects can be selected by admins.
• Global creates a shared connection visible to every project. Global creation and deletion are admin-only operations.

​

Use Webhook URLs Carefully

Some providers return a webhook URL after provisioning. Copy it into the provider’s webhook configuration when required, and treat the URL as sensitive routing information.

​

Maintain Connections

From the Triggers tab, operators can rename event connections, inspect provider details, copy webhook URLs, update project sharing, or delete obsolete connections.