Connectors

Alert channels

Send the outcome of a run to wherever your team actually looks.

An alert is only useful if it reaches someone. These connections are the outbound side of BARRY: a run fails, data goes stale, or a threshold is crossed, and the message goes to the place your team already watches rather than a dashboard nobody has open. Routing is per transport, so the pipelines that matter most can reach different people than the routine ones, and every message links straight back to the run it came from. Because alert channels are ordinary connections, they are configured once and reused — and the same Kafka or Event Hubs connection that receives data can carry alerts too.

Microsoft TeamsAlert

Posts an Adaptive Card into a Teams channel through an incoming webhook, so a failed or stale run shows up where the team already talks.

SlackAlert

Posts a message into a Slack channel through an incoming webhook URL — the quickest channel to set up when your team already lives in Slack.

Cisco WebexAlert

Sends a message into a Webex space using a bot token and the room identifier, for organisations standardised on Webex.

SMTP (Email)Alert

Sends alert email through any SMTP relay, often the simplest option when notifications need to reach people outside the chat tools.

Microsoft 365Alert

Sends mail through the Microsoft Graph API using an Entra application registration, so alerts come from a real mailbox in your tenant rather than an anonymous relay.

Microsoft Logic AppAlert

Posts JSON to a Logic App HTTP trigger, which lets you route alerts into whatever workflow, ticket system or approval chain you have already built.

Azure DevOpsAlert

Creates a work item — a bug or a task — in Azure DevOps, so a failed run turns into something that appears in the team's backlog.

Azure Event GridAlert

Publishes an event to a custom Event Grid topic, useful when alerts should fan out to several subscribers rather than a single channel.

Generic WebhookAlert

Sends an arbitrary HTTPS request, which covers any system that accepts a webhook but has no dedicated connector.

Looking for something else?

Every connection is Source, Sink, Trigger or Alert — derived from the connector itself, never set by hand. Browse the full catalogue, or ask us about a system you don’t see.

Ready to unlock your data?

See how BARRY brings your on-premises data to the cloud — safely, and on your terms.