Connectors Overview

Connectors enable AI teammates to fetch data, call tools, and interact with external systems. They serve as bridges between Edge Delta’s AI Team and your infrastructure, development tools, cloud platforms, and data sources. Configure connectors with credentials and settings, assign them to teammates (or they auto-assign to specialized teammates), then AI teammates use the connector tools to perform operations.

What Are Connectors?

A connector provides:

• Authentication: Secure connection to external services
• Tools: Specific capabilities (e.g., list resources, query data, create issues)
• Permissions: Read-only or read-write access controls
• Configuration: Service-specific settings (endpoints, regions, filters)

Event Connectors

Two-way, MCP-based connectors that enable AI teammates to interact with external platforms. Depending on the connector, they can receive events (GitHub webhooks, PagerDuty incidents) and send actions (create Jira tickets, query AWS APIs).

Streaming Connectors

Data ingestion connectors that continuously stream telemetry data into Edge Delta Pipelines. They collect logs, metrics, traces, and events, making them available for AI teammates to query through the Edge Delta MCP connector. Streaming connectors are the same as sources in an environment (pipeline)—when you configure a streaming connector, you’re adding a source to a pipeline.

Connector-Level Permissions

Configure default approval settings in the connector’s Tools tab:

• Allow: Execute without approval (read-only operations)
• Ask Permission: Require approval (write operations)

You can restrict specific tools when assigning connectors to teammates. Navigate to AI Team → Teammates → Edit → Connectors section to enable/disable tools per teammate or set specific permissions for that teammate.

Webhooks

Some connectors (GitHub, PagerDuty, Atlassian) provide webhook URLs. Configure this URL in the external service to push events to Edge Delta channels, triggering automated AI teammate responses.